I have had a bad experience with a broken hd.
So far i have been able to recover almost ( but not all ) data on the hd.
I report everything i did with the hope that it could be useful, my problem is with e2fsck and journal.
I haven't bought another hd to store the dd_rescue output because dd_rescue would take some months to recover the 150 gb home partition ( in 2 hours 20 MB... ), most of the data were backed up and hd is still in warranty.
In fact everything started with a grub 17 error.
I booted from another hd, then when i tried to mount the home partition ( ext3 ) i received the bad superblock error.
I found a way to discover where backup superblocks where ( be careful, and test it first to a floppy or a file before )
mkfs.ext2 -n /dev/hdb6
In the output there were superblock blocks.
Then it's possible to mount the filesystem, with the command ( as root )
mount -t ext2 -o ro,errors=continue,sb=163840 /dev/hdb6 /mnt/something
If it still gives error, you can try with something like
for i in $( cat Super.txt ) ; do mount -t ext2 -o ro,errors=continue,sb=$i /dev/hdb6 /mnt/something && break ; done
Where Super contains all the superblocks.
To copy files, i've used
cp -rpvf sourcedir destinationdir 2>>~/logfile.txt
With this i recovered almost every data, except quite new mails not yet backed up and other few things.
You can check reading logfile.txt what's still wrong.
So i have tried to check the filesystem with e2fsck, but i have been unable to do so
With
e2fsck -b superblock -c -C 0 /dev/hdb6
i obtain the following error concerning journal. I would like to skip journal check but i don't find a way to do so, and here is my problem.
e2fsck: Attempt to read block from filesystem resulted in short read controlland o il journal ext3 per /home
e2fsck 1.37 (21-Mar-2005)
/home: Attempt to read block from filesystem resulted in short read while readin g block 538
/home: Attempt to read block from filesystem resulted in short read lettura del superblocco del journal
Help is welcome.
Thank you in advance.
