On 11/17/19 16:06, Mick wrote:
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.
Have you had any experience with this? I spent days search for that
superblock once, even writing a pgm to search for the magic number,
after working with dump2fs, and never got anywhere. I'd sure like to
hear that somebody had success with it.
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.
Thanks for the tip about ddrescue.
