The output was just a part of a dmesg. Fdisk -l gives me the following output:
$ fdisk -l /dev/sdb
Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x28f12a69
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 608 4883728+ 83 Linux
/dev/sdb2 609 38913 307684912+ f W95 Ext'd (LBA)
/dev/sdb5 609 730 979933+ 82 Linux swap / Solaris
/dev/sdb6 731 38913 306704916 83 Linux
The partition that gives me trouble is sdb6. Manually mounting this partition gives me the following...
$ sudo mount /dev/sdb6 /mnt/tmp
mount: wrong fs type, bad option, bad superblock on /dev/sdb6,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Originally Posted by pixellany
Welcome to LQ!!
First, what command produced all of that output?
Please post the output of "fdisk -l" (ell, not one---run this as root)
Also, what happens if you try to mount one or more of the partitions manually using "mount"? e.g.: Suppose you have a mount point named "/mnt/ext_1". Try running
mount /dev/sdb1 /mnt/ext_1
With respect to restoring the partition structure, there are at least two aspects:
1. the partition table which is simply a map of the partition locations. This can readily be copied from an identical disk.
2. the "formatting"--i.e. the filesystem structure of each partition. I've never heard of copying this from another drive, but I doubt that it can be done without altering data. It CAN however be repaired with tools like fsck.-----But first, lets find out where the problem is.
If you think the drive is physically failing, and you have really valuable data, then the first thing to consider is cloning the whole drive.