I have a LInux Firewall Server which is not boooting but I have some scripts on it which I want to backup. So I have used knnopix Live CD to boot & got these observations. Any Idea to do next. root@Knoppix:~# fdisk -l Disk /dev/hda: 5368 MB, 5368709120 bytes 255 heads, 63 sectors/track, 652 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 3 24066 83 Linux /dev/hda2 4 652 5213092+ 5 Extended /dev/hda5 4 134 1052226 82 Linux swap / Solaris /dev/hda6 135 224 722893+ 83 Linux /dev/hda7 225 288 514048+ 83 Linux /dev/hda8 289 626 2714953+ 83 Linux oot@Knoppix:~# mount -t ext3 /dev/hda1 /mnt/hda1 mount: wrong fs type, bad option, bad superblock on /dev/hda1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Knoppix:~# fsck /dev/hda1 fsck 1.40-WIP (14-Nov-2006) e2fsck 1.40-WIP (14-Nov-2006) Couldn't find ext2 superblock, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/hda1 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> Thanks, Ravinder Singh

First, try replacing ext3 with ext2 in your mount command line: mount -t ext2 /dev/hda1 /mnt/hda1 If that fails, follow the direction at the end of the fsck output . . . try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> HTH, Ernie Registered Linux User 247790

Thanks ernie, I have tried these options. mount -t ext3 /dev/hda1 /mnt/hda1 mount -t ext2 /dev/hda1 /mnt/hda1 e2fsck -b 8193 /dev/hda1 The error is same. Is there any command to see which type of filesystem it is & which block size it is using. Thanks & regards, Ravinder Singh