I know device SDB works, since I'm using it right now. I don't know what the prognosis is for the other drives. I know they have Ubuntu's bootloader, but other than that, there's really no way to know. The fact that the partition table is still intact is good news.

If I could just retrieve the files from my /home partition somehow--at the very least--I'd be pretty darn happy.

If I have to use the words 'partition' and 'table' one more time... :P

I just rebooted my system and when I try to boot from the Ubuntu drive, error 21 is displayed (drive does not exist). It was _JUST_ working. I'm wondering if there is something wrong with my board that could have caused some of the problems to the other two drives, as well. I've had it happen before recently where I had just been using Ubuntu and all of a sudden, it just wouldn't boot anymore. I scanned the drive with the script I mention later, but I can't imagine how simply scanning a drive could do anything, even if it may have been interrupted.

I have a Perl script that reads the partition table and then goes to the only Linux partition in the list. It lists out the data starting at this location and what I'm seeing is a large section of zeros followed by non-zero data, and then zeros again for a large section. Does this necessarily mean that all the data has been overwritten. I know I'd remember if I'd overwritten the entire drive with zeros and it seems like it would have taken a long time. I compared this to the Ubuntu drive and there appears to be much more data using the script. Without knowing much about the structure of the ext3 filesystem... is the data I _am_ able to pick up with the script simply pointers to where the data _really_ is?