(no subject)

[torkell]

Chkdsk just decided the best way to fix a SmartMedia card with FAT errors was to eat the directory, and then go "Hey! Lost clusters!". I know have 500 of the things in a directory named "FOUND.000" instead of 64 megs of photos in a directory named "DCIM\100OLYMP".

... that's 64 MEGS of my photos you just ATE, you worthless program! Now I've got to piece together filenames and photos from a bunch of 4k and 144k files.

Comments

[pewterfish.livejournal.com]

Oh shit. I'm assuming no backups, in which case ... damn.

Any rapid programmatic solutions coming to mind? (Recovering the original FAT table occurs to me, but since the files have moved, that won't be much help).

[torkell]

Yep, no backups. Those photos were taken about... *looks at watch* 5 or 6 hours ago.

About the only thing in my favour is I reformatted all the cards a coupld of days ago (to set them all to something sensible for the cluster size), and so the files should be contiguous and ordered by time of shooting. Unfortuantly since chkdsk trashed the directory tree, fixing this is going to be tricky.

I also have a couple more cards where the folder containing the photos has vanished. Looking at the raw contents on one shows that everything's there, but part of the directory tree got eaten. Now to find a reference to FAT16...

[pleaseremove.livejournal.com]

lol, im sorry, its nasty to laugh...but someone has too

last time i ended up with a folder called FOUND.000 i left someone else to go sort it all out into its little folders again....ah the wonders of helping people when their machine screws up

[torkell]

Yes, but mine went and filled the .chk files with random junk. I have directory entries in the first 4k file (cluster size is 4k), and no file is bigger than ~180k. Average photo size is 700k. Funfunfun

[ralesk.livejournal.com]

What on Earth were you on when you decided to have chkdsk check your SM?