Sony ZV-E10 in camera file repair process- DO NOT USE

sludge21017

Senior Member
Messages
4,624
Solutions
8
Reaction score
1,424
Put the card in the camera sometime last week, and the popup to repair before use came up. (Don't remember the exact wording, but you get the idea).

Figured it needed to rebuild the database or something.

Accepted.

1 week later - I'm looking around the memory card on the computer - the PRIVATE/M4ROOT/CLIP is empty. All the folders PRIVATE and lower are dated 12/26/2022 12:18pm... 1 week ago... which is about the time I remember having this problem.

Well how do I know they are missing? I have the photos from the day of the video.

And when I go to playback in camera- the video files are BLACK with play buttons.

I have backups of the video in question... will have to look and see if I lost anything else. Probably nothing else that was important.
 
Microcenter, 512GB, v30

It's the ZV-E10 repair process.

I had a new SanDisk card when I first got the camera - I was unable to transfer photos to my phone because the repair process had to run. But it never repaired anything - since I could never transfer photos to my phone.

I mean at that point I learned NOT to delete photos outside the camera - since it couldn't repair the database.

I am 100% sure I didn't delete the files on the card.

I copied my backups to the card. No prompt to 'repair' the card/database. Videos don't play. I mean it's not an entire loss or anything.

Will need to backup the photos first before attempting manual database repair option.
 
Last edited:
Damn, I nearly bought one of those 2 hours ago. After looking at it, plus an a6100 and a nikon z50, turned out they had none in stock.

I hope you didn't lose anything. If I understand correctly, this camera has done this twice, once on each of 2 different cards - bad news.
 
Damn, I nearly bought one of those 2 hours ago. After looking at it, plus an a6100 and a nikon z50, turned out they had none in stock.

I hope you didn't lose anything. If I understand correctly, this camera has done this twice, once on each of 2 different cards - bad news.
I mean I still love the camera.

This was on a power boot after using the card in my computer - Just not sure why this repair deleted the video folders this time and rebuilt them with nothing.

(The windows 10 machine is setup for removal of card whenever). I'm pretty sure I had no editing or writes at the time of removal.

720b7cd3e2ca48b09375c7c102232314.jpg.png

Yes, I had the video files backed up.

I wonder if DxO PL6 had something to do with it. It created a bunch of DOP files on the card. Okay - I thought I edited the files on my local drive in DXO PL6, it was a 30 minute photo timelapse ... maybe I edited on the card. But these files are from before the TL...which is odd to have anything applied to them.

6208bd0b9c21439a94150b6e91d7a250.jpg.png

The very 1st time it said it can't repair the database when trying to transfer files - so no file transfer for me to my phone. Can't use Imaging edge mobile app. No worries, nothing lost. I'm pretty sure I deleted files on the computer - other Sony cameras can repair those database without issue.
 
Last edited:
Other than a card or other hardware failure, I don't even get how this is a thing. It's just an exfat file system, with files and directories. Even if the camera is indexing the image files for convenience, like delete by date or whatever, it should be leaving the image files alone once it's written them. The fact that you add or delete on the computer shouldn't do anything to files you didn't explicitly change. This stuff is just weird.
 
Other than a card or other hardware failure, I don't even get how this is a thing. It's just an exfat file system, with files and directories. Even if the camera is indexing the image files for convenience, like delete by date or whatever, it should be leaving the image files alone once it's written them. The fact that you add or delete on the computer shouldn't do anything to files you didn't explicitly change. This stuff is just weird.
Note
  • Do not edit or otherwise process movie files/folders from the connected computer. Movie files may be damaged or become unplayable. Do not delete movies on the memory card from the computer. Sony is not held liable for consequences resulting from such operations via the computer.
  • If you delete images or perform other operations from the connected computer, the image database file may become inconsistent. In this case, repair the image database file.
  • The folder tree is different during MTP connection.
 
Other than a card or other hardware failure, I don't even get how this is a thing. It's just an exfat file system, with files and directories. Even if the camera is indexing the image files for convenience, like delete by date or whatever, it should be leaving the image files alone once it's written them. The fact that you add or delete on the computer shouldn't do anything to files you didn't explicitly change. This stuff is just weird.
Note
  • Do not edit or otherwise process movie files/folders from the connected computer. Movie files may be damaged or become unplayable. Do not delete movies on the memory card from the computer. Sony is not held liable for consequences resulting from such operations via the computer.
  • If you delete images or perform other operations from the connected computer, the image database file may become inconsistent. In this case, repair the image database file.
  • The folder tree is different during MTP connection.
Thanks for the explict cite. I may not understand it, but clearly it's a thing.

MTP is definitely weird. I'll always prefer USB Mass storage if it's available. On my system (usually Linux), MTPFS doesn't seems to preserve file modification dates. Blasphemy!

Someone mentioned using an automatic function for ejecting USB devices. General advice from the past: When using Windows, avoid *all* features including any of Smart, Dynamic, Automatic, etc in the name. They lead only to sorrow.

Mounting the camera/card as read-only seems to be the most prudent option. On Linux, if the device was auto-mounted, *software* eject and manually mount with "mount -o ro,noatime <device> <mountpoint>" would generally do it if using USB Mass Storage. I generally remove the card from the camera and use a card reader. "One less thing" as Forrest Gump said.
 
Last edited:
Yeah, other than that I don't know what happened. I know I didn't delete those files manually or date/timestamp all those folders as such.

Another thing - I am on f/w 1.00. 2.00 has been available for a while. Repair could be one of those operational fixes that don't get mentioned. I never bothered with the update as I don't care about eye AF with animals or touch shutter.

I will backup my card, manually repair the database and see what happens.

Upgrade to F/W 2.00.

If I did have problems, I'll try the repair on 2.00.

At any rate, don't really see anyone else having issues..maybe no one runs repair or does crazy things.
 
I said: "Mounting the camera/card as read-only seems to be the most prudent option."

Looked at the SD card in my RX100 today, it's got a little "lock" button that makes the card read-only. That ought to prevent a lot of possible mischief. (Just remember to set it back before you put the card back in the camera!)

ETA: Thinking of that would have saved me some aggravation: I once got confused and used Rawtherapee on a raw file on the SD card. It didn't actually change any images, but added a .pp3 sidecar file on the card. I backed up everything on the card (again), deleted the .pp3 file, put the card back in the camera, no problems seen.
 
Last edited:

Keyboard shortcuts

Back
Top