Bad magic number in super-block while trying to open /dev/hda6

Daddyfix · 11-20-2006, 10:21 AM

I can't seem to fix a partition on my HD.
When I try to mount it I get this error

Code:

[root@server ~]# mount /home
mount: wrong fs type, bad option, bad superblock on /dev/hda6,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[root@server ~]# dmesg | tail
 [<c04068bf>] do_IRQ+0x9e/0xbc
 =======================
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
VFS: Can't find ext3 filesystem on dev hda6.
VFS: Can't find ext3 filesystem on dev hda6.
VFS: Can't find an ext2 filesystem on dev hda6.
VFS: Can't find an ext2 filesystem on dev hda6.
VFS: Can't find ext3 filesystem on dev hda6.
VFS: Can't find ext3 filesystem on dev hda6.

I tried to fix it with

Code:

[root@server ~]# mke2fs -n /dev/hda6
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3312960 inodes, 6622788 blocks
331139 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
203 block groups
32768 blocks per group, 32768 fragments per group
16320 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

[root@server ~]# e2fsck -f -b 32768 /dev/hda6
e2fsck 1.39 (29-May-2006)
e2fsck: Bad magic number in super-block while trying to open /dev/hda6

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>

Anything else I can try? I accidentally changed the partition extent start point but everything was fine until I rebooted.

Daddyfix · 11-20-2006, 10:05 PM

Ok.. I had a hell of a time bringing this partition back up.. It seems like there were 117 errors. For how long? Who knows.

Anyways, I hope this helps someone..
This is what I used to fix those errors and rewrite the partition, WITHOUT loosing data!

http www<dot>cgsecurity<dot>org<slash>wiki<slash>TestDisk

TestDisk is a powerful free data recovery software! It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally deleting your Partition Table). Partition table recovery using TestDisk is really easy.