On 11/23/2016 01:04 AM, YK wrote:
On 11/23/2016 12:01 AM, Phil Turmel wrote:
Please provide the output of these two commands:
dd if=/dev/sdb1 bs=4k count=4k |hexdump -C |head -n1000
dd if=/dev/sdc bs=4k count=4k |hexdump -C |head -n1000
Here is the output for sdb1
...
00000420 00 80 00 00 00 80 00 00 00 20 00 00 d8 ef ba 53 |.........
.....S|
00000430 e6 ef ba 53 01 00 ff ff 53 ef 01 00 01 00 00 00
|...S....S.......|
00000440 ef ee ba 53 00 00 00 00 00 00 00 00 01 00 00 00
|...S............|
On 11/23/2016 11:47 PM, YK wrote:
On 11/23/2016 10:25 PM, Wols Lists wrote:
Basically, you need to run hexdump, and look for evidence of a damaged
superblock, and/or a filesystem superblock.
If you find them, the other experts will be able, hopefully, to tell you
how to get the array back
I do see "53 ef" in the fifth line of the output for my sdb1 hexdump !
After a lot of reading, I'm getting to the conclusion that the hexdump
for sdb1
shows my ext4 superblock in the correct location with the expected
offset (line 430, 0x38).
Am I right?
I tried to mount the partition without offset, by executing:
mount /dev/sdb1 -o ro -t ext4 /mnt/recovery
But I still get this message:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1
Is there something I can do to successfully mount my old partition?
Thank you all again,
Yaniv
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
