In my last attempt, I tried different filesystem offsets. I tried that with all superblocks in the testdisk.log for i in $(grep e2fsck testdisk.log | uniq | cut -d " " -f 4) do Running e2fsck with those values gives: e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 Recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed It mentions many entry like: recover_EXT2: s_block_group_nr=1/7452, s_mnt_count=6/20, I've also ran a testdisk deep search if anyone can decypher the log. However as I understand, these are where the superblocks were when the filesystem was created, which does not necessarily mean they are still intact. but trying "e2fsck -b " for each block fails: $ sudo e2fsck -b 71663616 /dev/sdb1Į2fsck: Invalid argument while trying to open /dev/sdb1 Mount: wrong fs type, bad option, bad superblock on /dev/sdb1,įsck reports an invalid superblock: $ sudo fsck.ext4 /dev/sdb1įsck.ext4: Superblock invalid, trying backup blocks.įsck.ext4: Bad magic number in super-block while trying to open /dev/sdb1Īnd e2fsck reports a similar error: $ sudo e2fsck /dev/sdb1Į2fsck: Superblock invalid, trying backup blocks.Į2fsck: Bad magic number in super-block while trying to open /dev/sdb1ĭumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1 Mount: you must specify the filesystem type but the partition fails to mount: $ sudo mount /dev/sdb1 a The drive has a single partition and uses a GPT partition table (with the label ears).įdisk -l /dev/sdb shows: Device Boot Start End Blocks Id System
However, as a result, it appears its EXT4 file system is corrupt. Recently, my external hard drive enclosure failed (the hard drive itself powers up in another enclosure).
0 kommentar(er)
