@matrix why would you use FAT32?
@nukie Default for thumb drives
💀
@matrix
You burn it with nuclear fire.
@matrix mkfs -t vfat
@matrix mkfs.vfat also works
@sjw I need the data
@matrix the data on the drive? Then mount it and pull the data off of it.
@matrix oh I completely misread!
@matrix Try fsck -w -r -l -a -v -t /dev/sdX1
-w means write to disk immediately.
-r means to do disk check interactively (ask you what to do to when encountering errors). On newer versions of dosfsck this is the default.
-l means to list the filenames processed.
-a means automatically fix errors. Do not use it, if You want to have more control over fixing possible errors.
-v means verbose mode. Generates slightly more output.
-t means mark unreadable clusters as bad.
-w means write to disk immediately.
-r means to do disk check interactively (ask you what to do to when encountering errors). On newer versions of dosfsck this is the default.
-l means to list the filenames processed.
-a means automatically fix errors. Do not use it, if You want to have more control over fixing possible errors.
-v means verbose mode. Generates slightly more output.
-t means mark unreadable clusters as bad.
@matrix I meant fsck.vfat
@sjw That's why tried. TestDisk seems to have helped partially. It found the partition and most files are accessible.
@matrix oh you can't even see partitions! That makes things a bit more complicated.
I'd recommend dumping an image with dd and working off the image.
I'd recommend dumping an image with dd and working off the image.
@sjw Yeah, I did that, since the drive was dying.
I think I managed to get all the files by running dosfsck on the partition recovered by TestDisk.
