ext3 filesystem: superblock not found
I somehow broke the data partition of my server when preparing for
backup. e2fsck can't find superblock, but finds 'bad magic number...'
I tried the e2fsck with different -b option:
e2fsck -b 8192 /dev/rd/c0d0p3
e2fsck -b 8193 /dev/rd/c0d0p3
e2fsck -b 16384 /dev/rd/c0d0p3
e2fsck -b 16385 /dev/rd/c0d0p3
e2fsck -b 32768 /dev/rd/c0d0p3
e2fsck -b 32769 /dev/rd/c0d0p3
e2fsck -b 65536 /dev/rd/c0d0p3
e2fsck -b 65537 /dev/rd/c0d0p3
e2fsck -b 32768 /dev/rd/c0d0p3
e2fsck -b 65536 /dev/rd/c0d0p3
e2fsck -b 131072 /dev/rd/c0d0p3
e2fsck -b 262144 /dev/rd/c0d0p3
e2fsck -b 524288 /dev/rd/c0d0p3
but always got the same the negative result.
Debian sarge:
srv:~# uname -a
Linux srv 2.6.8-2-386 #1 Thu May 19 17:40:50 JST 2005 i686 GNU/Linux
(box has been up and running since May 21!)
The partition is on a Mylex hardware raid. The status of the raid from
/proc/rd/c0/current_status seems ok.
At the moment I am dd'ing the partition off somewhere save and would
like to try to recover somehow.
Is there still hope?
I would be very grateful for any hints and suggestions.
Thanks,
Jo
Output of different commands and log-files:
---output of e2fsck:
srv:/var/log# e2fsck /dev/rd/c0d0p3
e2fsck 1.37 (21-Mar-2005)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/rd/c0d0p3
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>
---/var/log/syslog------------------
Dec 2 19:39:10 srv kernel: EXT3-fs error (device rd/c0d0p3):
ext3_readdir: bad entry in directory #2: inode out of bounds - offset=0,
inode=2, rec_len=12, name_len=1
Dec 2 19:39:10 srv kernel: Aborting journal on device rd/c0d0p3.
Dec 2 19:39:10 srv kernel: ext3_abort called.
Dec 2 19:39:10 srv kernel: EXT3-fs abort (device rd/c0d0p3):
ext3_journal_start: Detected aborted journal
Dec 2 19:39:10 srv kernel: Remounting filesystem read-only
Dec 2 19:39:10 srv kernel: EXT3-fs error (device rd/c0d0p3):
ext3_readdir: bad entry in directory #2: inode out of bounds - offset=0,
inode=2, rec_len=12, name_len=1
---/var/log/dmesg-----------------------------------
DAC960#0: Physical Device 0:8 Found
DAC960#0: Physical Device 0:0 Found
DAC960#0: Physical Device 0:1 Found
DAC960#0: Physical Device 0:2 Found
DAC960#0: Physical Device 0:3 Found
DAC960#0: Physical Device 0:0 Online
DAC960#0: Physical Device 0:2 Standby
DAC960#0: Physical Device 0:3 Online
DAC960#0: Physical Device 0:1 Online
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) Found
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) Online
kjournald starting. Commit interval 5 seconds
EXT3 FS on rd/c0d0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Can't find ext3 filesystem on dev rd/c0d0p3.
Reply to: