psypher
November 1st, 2008, 06:03 PM
Hey all.
Got a bit of a problem. Had a Gutsy install with the OS on one drive and 3 X 80GB SATA drives setup with RAID5. The OS drive failed. I replaced it and installed Intrepid. Now my 3 X 80GB drives all have no partition table.
sudo fdisk -l
[sudo] password for sysadmin:
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000743c8
Device Boot Start End Blocks Id System
/dev/sda1 * 1 24042 193117333+ 83 Linux
/dev/sda2 24043 24321 2241067+ 5 Extended
/dev/sda5 24043 24321 2241036 82 Linux swap / Solaris
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd does seem to output something else, but not much?
I'm really really worried. There's no backup yet, that was the backup being moved onto a new server which is ready now.
I know the data must still be there. It's just a case of rebuilding the partition table and superblock. I really hope there is someone out there that has experience with this. Even if someone could just tell me why this would have happened. Surely the superblock and partition table was not stored on the other failed drive? It had nothing to do with this raid.
As far as i know the raid had not failed before the other disk, although I didn't check so I'll never know. But I think that each drive always contains a copy of the superblock. If I can just recover that I'm sure I can recreate the raid with mdadm and let it resync and all will be good.
Any help would be greatly appreciated.
Thanks
Got a bit of a problem. Had a Gutsy install with the OS on one drive and 3 X 80GB SATA drives setup with RAID5. The OS drive failed. I replaced it and installed Intrepid. Now my 3 X 80GB drives all have no partition table.
sudo fdisk -l
[sudo] password for sysadmin:
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000743c8
Device Boot Start End Blocks Id System
/dev/sda1 * 1 24042 193117333+ 83 Linux
/dev/sda2 24043 24321 2241067+ 5 Extended
/dev/sda5 24043 24321 2241036 82 Linux swap / Solaris
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd does seem to output something else, but not much?
I'm really really worried. There's no backup yet, that was the backup being moved onto a new server which is ready now.
I know the data must still be there. It's just a case of rebuilding the partition table and superblock. I really hope there is someone out there that has experience with this. Even if someone could just tell me why this would have happened. Surely the superblock and partition table was not stored on the other failed drive? It had nothing to do with this raid.
As far as i know the raid had not failed before the other disk, although I didn't check so I'll never know. But I think that each drive always contains a copy of the superblock. If I can just recover that I'm sure I can recreate the raid with mdadm and let it resync and all will be good.
Any help would be greatly appreciated.
Thanks