You keep top-posting and inverting the logical Q/A flow of this thread ... On Sunday, 17 November 2019 12:53:51 GMT n952162 wrote: > Ah, now I see. Yes, in that respect, that is, if you don't have a > chance to get /forcefsck written.
Running fsck manually with various options and then trying to recover various superblock locations could get you farther than simply running fsck in an accepting fashion. If fsck.ext4 shows up "bad magic number", you can run dumpe2fs on the partition and grep for "superblock" to find the location of both primary and backup superblocks of the corrupted fs. Then you can 'e2fsck -b XXXXXXXX / dev/sdaX' for each 'XXXXXXXX' superblock location and and try mount it thereafter to see if you can access your files. With a bit of luck at least one of the supeblocks will work recovering most of the data previously saved on this fs. Needless to say, you would not try this on the original partition, but a backup image you can create with ddrescue and friends. In any case, running fsck.ext4 -n (or -E nodiscard) should not cause any fs losses, unless the disk/hardware is faulty. Hence working on a backup image is the safest option. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
