Forum Debian Users Gang

# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xeff0eff0

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        7833    62918541    7  HPFS/NTFS
/dev/sda3            7834        7955      979965   82  Linux swap / Solaris
/dev/sda4            7956       60801   424485495    5  Extended
/dev/sda5            7956       10492    20378421   83  Linux
/dev/sda6           10493       18038    60613213+  83  Linux
/dev/sda7           18039       36597   149075136   83  Linux
/dev/sda8           36598       54411   143090923+  83  Linux
/dev/sda9           54412       57913    28129783+  83  Linux
/dev/sda10          57914       58768     6867756   83  Linux
/dev/sda11          58769       60801    16330041   83  Linux

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xaa78aa78

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       24321   195358401   83  Linux

Log of fsck -C -R -A -a
Mon Nov 23 16:52:56 2009

fsck from util-linux-ng 2.16.1
fsck.ext3: No such file or directory while trying to open /dev/sda8^M
/dev/sda8:
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>

fsck.ext3: No such file or directory while trying to open /dev/sda7^M
/dev/sda7:
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>

fsck.ext3: No such file or directory while trying to open /dev/sda9^M
/dev/sda9:
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>

Failed to open the device '/dev/sda5': No such file or directory


Failed to open the device '/dev/sda10': No such file or directory


Failed to open the device '/dev/sda6': No such file or directory



reiserfs_open: the reiserfs superblock cannot be found on /dev/sdb1.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

fsck died with exit status 8

Mon Nov 23 16:52:57 2009
----------------