Originally posted by Diablo3d
Are you using fakeraid? It sounds to me like this happened:
1) Fake-raid controller like Highpoint 1640a
2) Array is broken
3) You booted from a recovery disk that doesn't have the drivers for the raid controller modules loaded
Generally speaking, if you pull a drive from a hardware raid array and connect it to a standard controller (as would happen in the above example) you won't see any partition information. Sometimes you will see partition info on the first drive, but nothing on any of the others (because of striping).
what kind of raid controller do you have, or were you using 100% software? Also what distro are you using?
Sorry I should have provide a lot more information about my setup. I'm running Debian Testing. The drives are connected to 2 Promise PATA adaptors (non-RAID, just plain old PATA). One drive per ATA channel. Using 100% software raid.
From everything I can tell, the drives are still in good shape (i.e. not a hardware failure). It looks like, for whatever reason, the partition information is screwed up. They are no longer recognized as "fd" or whatever the linux raid partition type is.
dmesg says basically the same thing as fdisk:
hde: WDC WD2500JB-00GVA0, ATA DISK drive
ide2 at 0xdfa0-0xdfa7,0xdf8e on irq 217
hde: max request size: 1024KiB
hde: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
/dev/ide/host2/bus0/target0/lun0: unknown partition table
(repeats for hdg, hdi, hdk)
Also here is the contents of /etc/raidtab if that helps: