I have Promise and VIA SATA controllers on my motherboard with 1 and 2 drives connected, respectively, as well as a SI3114 raid card with 4 eSATA connections, 2 of which are used in an external housing. The system is installed on a normal PATA drive. As of yesterday, all of these drives were working fine.

I had been having a problem with the system crashing when copying some files from one drive to another and watching a video file on the drive being copied to at the same time (didn't do it seperately, but I didn't have much time to try independently). Log showed a series of these before crashing:

Was told to run memtest, so I did, and it found 68 errors in just over 2 hours. Today, however, I realized that I had bumped the base clock speed up from 200 MHz to 205 MHz probably a few weeks ago for no reason at all (11x multiplier, so 55 MHz gain. Again, no reason). Set it back to auto, and no errors in memtest after 3 hours (going to let it run overnight once I finish this post). When I exited memtest and restarted the system, it had problems booting normally. It took 3-4 times as long to start services and get to the login screen. Fluxbox booted fine, but booting Gnome would also boot much more slowly (never finished b/c it took too long for me to wait.) No problems that I could see but same problem for several reboots. I went through serviceconf (this is FC4), and disabled services that weren't being used. I'm not sure if this did it, but it eventually started booting normally again. However, another problem came up.

It starts when it begins to unload the kernel. Something about Red Hat Nash 4.something, and then it says ata9 disabled. Once it boots, the drive I had been copying to and watching video on during crashes wouldn't load (I had even thought that drive might have been going bad to begin with earlier. I'd run fsck on it and had some errors come up, so I backed it up, reformatted, and reloaded the data). All the other drives load, including another from the same raid pci controller. Here is what dmesg|grep ata brings up.

Changing which controller it plugs into makes no change to dmesg. If the SI controller is removed, it starts off with ata5 disabled instead of ata9, but the card was still plugged in when I tried the drive on a different controller, so I don't know if the dmesg would show ata5 or ata9 disabled. It won't really bother me if the drive has died, and I have to get it RMA'd, but I'd like to have a chance to clear it off first (non-destructive cleaning off) and reclaim a (relatively) small number of files that I hadn't burned a backup of yet if possible. Any ideas?

I forgot to point out that I turned all the services that I had disabled or stopped from booting automatically back on just in case with, obviously, no effect.