Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Apr 2007
Disk doesn't contain a valid partition table
To fix the problem I have tried running fsck /dev/hdd but the message back is
fsck /dev/sdd 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/sdd
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>
which is a bit strange since the drive is formatted to ext3.
Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 2550 20482843+ c W95 FAT32 (LBA) /dev/sda2 2551 2805 2048287+ 82 Linux swap / Solaris /dev/sda3 2806 9052 50179027+ 83 Linux /dev/sda4 9053 9729 5438002+ f W95 Ext'd (LBA) /dev/sda5 9053 9729 5437971 83 Linux Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 12493 100349991 83 Linux /dev/sdb2 12494 24321 95008410 f W95 Ext'd (LBA) /dev/sdb5 12494 19946 59866191 83 Linux /dev/sdb6 19947 20711 6144831 b W95 FAT32 /dev/sdb7 20712 24321 28997293+ b W95 FAT32 Disk /dev/sdc: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 9023 72477216 c W95 FAT32 (LBA) /dev/sdc2 9024 24321 122881185 f W95 Ext'd (LBA) /dev/sdc5 9024 24321 122881153+ 83 Linux Disk /dev/sdd: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdd doesn't contain a valid partition table
Last edited by MikeTbob; 09-23-2012 at 06:22 AM. Reason: added code tags
If you can get it to mount, you should back up
the data and reformat it. If it fails to mount, you have
nothing to lose by reformatting.
You probably need to partition and format. If you have problems after that
you have a creepy problem with the OS, the usb hardware or software,
or other hard to trace bug.
- Join Date
- Apr 2007
Sadly it will not mount since the system now thinks it is ext2 whereas it is (or was) ext3.
I have everything to loose by formatting ..... nearly 500GB of data. This is the third time (different drives) in three weeks so I really need to find out the reason why. (yes, that is 1.5TB of data in total)
Whilst the problem has so far been exclusively on external drives connected through USB I have just had a lot of difficulty in getting the base system to boot. It took just over an hour and fsck ran of its own accord reporting lots of Port Failed to Respond; Revalidation Failed (errorno=-2) and I/O error problems. I wonder if this is some strange coincidence or a related event.
The messages above include "Port Failed to Respond". Since no USB devices are attached I wonder which port. I wonder if this could be failure of the motherboard ...... hope not. But the problem has only been around for two or three weeks which sort of rules our the o/s and would leave it as hardware based. Cables are out since it affects several drives so if that were the case then it can only be the motherboard since there is effectively nothing else left.
- Join Date
- Dec 2010
I have the same problem with my lvm table, but there noboby on the net that can tell something helpfull...
Can sobody tell something with some clue about the problem...
Please start a new thread detailing the problems you are having and someone will help you ASAP. We lock these old threads.