wolfpeach
06-02-2004, 12:11 PM
have installed knoppix on hdd & now having trouble accessing one of the disk partitions. The automount does not work for one partition, and when I try to mount manually I get the following error:
root@eoaserver:~# mount -t ext3 /dev/hda3 /mnt/hda3
mount: wrong fs type, bad option, bad superblock on /dev/hda3,
or too many mounted file systems
I tried running fsck, and got this:
root@eoaserver:~# fsck /dev/hda3
fsck 1.35-WIP (21-Aug-2003)
e2fsck 1.35-WIP (21-Aug-2003)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/hda3
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>
I tried e2fsck & got the following:
root@eoaserver:~# e2fsck -f -b 8193 /dev/hda3 e2fsck 1.35-WIP (21-Aug-2003)
e2fsck: Bad magic number in super-block while trying to open /dev/hda3
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>
The filesystem is ext3 (type 83). I tried deleting and remaking the partition with fdisk, but no improvement. Heres the info:
Disk /dev/hda: 20.4 GB, 20490559488 bytes
255 heads, 63 sectors/track, 2491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 305 2449881 83 Linux
/dev/hda2 306 396 730957+ 82 Linux swap
/dev/hda3 397 2491 16828087+ 83 Linux
Have also tried editing fstab to include filetype ext3 for hda3, but also no difference.... At end of tether here... :-[ Anyone got any suggestions...???
Wolfpeach X
root@eoaserver:~# mount -t ext3 /dev/hda3 /mnt/hda3
mount: wrong fs type, bad option, bad superblock on /dev/hda3,
or too many mounted file systems
I tried running fsck, and got this:
root@eoaserver:~# fsck /dev/hda3
fsck 1.35-WIP (21-Aug-2003)
e2fsck 1.35-WIP (21-Aug-2003)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/hda3
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>
I tried e2fsck & got the following:
root@eoaserver:~# e2fsck -f -b 8193 /dev/hda3 e2fsck 1.35-WIP (21-Aug-2003)
e2fsck: Bad magic number in super-block while trying to open /dev/hda3
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>
The filesystem is ext3 (type 83). I tried deleting and remaking the partition with fdisk, but no improvement. Heres the info:
Disk /dev/hda: 20.4 GB, 20490559488 bytes
255 heads, 63 sectors/track, 2491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 305 2449881 83 Linux
/dev/hda2 306 396 730957+ 82 Linux swap
/dev/hda3 397 2491 16828087+ 83 Linux
Have also tried editing fstab to include filetype ext3 for hda3, but also no difference.... At end of tether here... :-[ Anyone got any suggestions...???
Wolfpeach X