needs help, root inode gone after usb bus reset on sata disks
Jelle de Jong
jelledejong at powercraft.nl
Thu May 29 14:44:08 UTC 2008
Theodore Tso wrote:
> On Thu, May 29, 2008 at 11:37:25AM +0200, Jelle de Jong wrote:
>> My humble excuse, i had to place the disk in a server and this server had
>> an older version of the dumpe2fs tool that did not supported the superblock
>> option. I upgraded the server and rerun all the test for you.
>>
>> dumpe2fs -o superblock=32768 /dev/sda1 >
>> dumpe2fs-superblock-32768-info-sda1.txt 2>&1
>> dumpe2fs -o superblock=98304 /dev/sda1 >
>> dumpe2fs-superblock-98304-info-sda1.txt 2>&1
>
> Unfortunately, it looks like the backup superblocks were also
> corrupted, and in the same way. Did you *ever* run e2fsck in
> read/write mode (i.e., without the -n option) on this filesystem after
> when you think it had gotten corrupted?
yes i made one mistake the first time i run fsck /dev/sdX i answered yes
to the fist question (autoreponse), then i saw the second question and
saw that it was the same issue as with the previous disk and cancel the
fsck and reported my issue to the list.
>
> So what I will suggest at this point is that you do the following:
>
> debugfs -w /dev/sda1
> debugfs: features dir_index filetype sparse_super
> debugfs: quit
>
> The run "e2fsck -nf /dev/sda1" and make the output looks relatively
> clean. You should *not* see any messages about needing to relocate
> inode tables.
>
> If so, you can then run "e2fsck -f /dev/sda1 to fully recover the
> filesysten.
>
>> I always seem to get the impossible out of Linux tools, but most times this
>> is during quality tests... however this was on "normal usage". I hope it
>> has noting to do with the latest release changes or with corrupt binaries
>> on my client system.
>
> Well, absolutely no one else reporting this problem or anything like
> it...
Ok, this did not when so great...
e2fsck -nf /dev/sda1 > e2fsck-nf-info-sda1.txt 2>&1
e2fsck -fy /dev/sda1 > e2fsck-fy-info-sda1.txt 2>&1
http://www.powercraft.nl/temp/e2fsck-nf-info-sda1.txt.gz
http://www.powercraft.nl/temp/e2fsck-fy-info-sda1.txt.gz (log is of an
second resumed run)
root at ashley:/media/sda1# ls -hal
total 8.0K
drwxr-xr-x 3 root root 4.0K 2008-05-29 15:28 .
drwxr-xr-x 5 root root 200 2008-05-29 16:10 ..
drwx------ 2 root root 4.0K 2008-05-29 15:28 lost+found
root at ashley:/media/sda1# cd lost+found/
root at ashley:/media/sda1/lost+found# ls -hal
total 8.0K
drwx------ 2 root root 4.0K 2008-05-29 15:28 .
drwxr-xr-x 3 root root 4.0K 2008-05-29 15:28 ..
root at ashley:/media/sda1/lost+found# df -hal
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 688G 8.0K 653G 1% /media/sda1
nothing there anymore :-S :-S
I am going to restore the backup image back to sda1 it is 750GB so this
takes a while (14 hours)
Any ideas what went wrong?
More information about the Ext3-users
mailing list