After a recent power failure which caused my linux box (Ubuntu 8.10) to rapidly poweroff twice from a normal running state, I have a drive that will not mount.
UPDATE: The drive will sometimes mount, but show up as completely empty (not even Lost+Found) and show 14.9 GB free (it is a 500GB drive) When I try to do anything it gives me a permission error and the drive unmounts. (or, perhaps, was not really mounted in the first place?)
Here's the error message when I try to mount:
~$ sudo mount -a mount: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
So maybe specify the fs type?
~$ sudo mount -t ext3 /dev/sdd1 /media/disk-7 mount: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
No, same. So something is messed up?
~$ sudo fsck /dev/sdd1 fsck 1.41.3 (12-Oct-2008) e2fsck 1.41.3 (12-Oct-2008) /dev/sdd1: recovering journal fsck.ext3: No such file or directory while trying to re-open /dev/sdd1 Warning... fsck.ext3 for device /dev/sdd1 exited with signal 11.
Googling for signal 11 wasn't encouraging, but I found a few other ways to try to repair the disk:
~$ sudo e2fsck /dev/sdd1 e2fsck 1.41.3 (12-Oct-2008) /dev/sdd1: recovering journal e2fsck: No such file or directory while trying to open /dev/sdd1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 [device]
Still hoping this failure has something to do with the power outage, I assume the superblock is corrupt or something, and try another: (I first determine that my block size is 32k using makefs -n)
~$ sudo e2fsck -b 32768 /dev/sdd1 e2fsck 1.41.3 (12-Oct-2008) ext3 recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. /dev/sdd1: recovering journal e2fsck: Journal must be at least 1024 blocks while recovering ext3 journal of /dev/sdd1
Per Avery Payne below I tried the following:
sudo mount -t ext2 -o ro /dev/sdd1 /media/disk-7
But got this error message:
mount: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so ~$ dmesg | tail [261157.639721] EXT2-fs: sdd1: couldn't mount because of unsupported optional features (4).
And that's about where I'm stuck. I tried every backup superblock listed and get the same result. If it helps any, the "recovering journal" step takes a long time before it moves on to tell me it isn't working.
Honestly, I don't care much about getting back the state of the drive minutes before the crash, just about recovering the 400+ GB of other data that is on it. If anyone knows anything else I can try, ext3 data recovery utilities or techniques, etc, I would greatly appreciate it!