Here's an interesting situation for you. I have a hardrive that seems to have a mind of its own. Before I mention anything further I'll bring you up to speed with what is in my system.
Motherboard :ASUS A7N8X
CPU :Athlon XP 2800+ (Barton Core, 333 FSB)
RAM :512Mb PC2700 RAM (1x512MB stick)
Audio :Sound Blaster Audigy Gamer
CD/DVD Drives :LG CD Burner & DVD Drive
NIC :On board nVidia 10/100
HDD :Maxtor 30Gb 7200 RPM & Fujitsu 30Gb 7200 RPM
(Not sure of caches sizes)
This is what's happened so far, I tried booting up one day and got an "NTLDR not found" error. After some fooling around I noticed it was because my Fujitsu(Slave) drive was being detected as master, and the Maxtor drive was not being detected at all. Oh an all this happened as the Fujitsu drive was specifically jumpered for SLAVE. Interesting so far eh!
Ok so now I go into to trouble shooting mode, I disconnected the Fujitsu drive and only connected the Maxtor drive. My system booted fine, I then reconnect the Fujitsu drive and I get the same problem. Then I tried connecting the drives to separate IDE Lines. I put the Maxtor on IDE 1 and the Fujitsu on IDE 2, during this process I also unplugged both my CD-w/RW & DVD drives. I never touched any of the jumper's I only verified that the Fujitsu was still jumpered as slave. When I booted in this configuration again the Fujitsu was detected as master, the system booted fine.
It was at this point that I tried pulling the jumper completely from the Fujitsu drive. I then plugged it in on the IDE 1 line along with the Maxtor drive. They were both detected correctly and the system loaded fine. Hmmmm I started saying at this point.
Anyways I shutdown again, reattached the jumper in the correct slave position and the same error again.
Now seeing as this has become much longer winded than I thought I'll just ask the question. I'm guessing with a fair amount of certainty that the Fujitsu drive is now on it last legs, correct? Or is there a possibility of something else going wrong. I managed to back-up all the pertinent data from the drive when I managed to get them both to boot, now I'm wondering if I have to buy another drive, or can I fix this one.
Thanks for everyone help and input.