![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
erehwon6811
Limp Gawd
- Joined
- Aug 5, 2004
- Messages
- 493
Yesterday, I noticed that I could no longer access my documents. I checked and I was no longer detecting the hard drive. I took it out and used the interface in a external drive to transfer my files to another computer. My dad noticed that it did not want to start up when laid horizontal, so we had to lay it on its side to get it to start. I did get my data and Western Digital is sending us a new drive. I thought the problem was solved. Bad drive.
While out at Staples today, we picked up a 200 gig Maxtor for $40. He let me put this one in and he's taking the one WD is sending us. I plug it in and start the computer up. It is not detected. I checked Disk management and the bios and neither detect it. I do not know what is wrong. It appears that the first one was a bad drive (made in June 05 and only used in the two months since being installed at Christmas), but I don't understand the new one not working. I even tried a different cable and nothing.
Here's my specs:
GIGABYTE GA-K8NSC-939 Socket 939
Antec PERFORMANCE TX TX1050B Black Steel Server Computer Case 500W ATX12V v2.0 Power Supply
AMD Athlon 64 3500+ Venice 1GHz FSB Socket 939
CORSAIR ValueSelect 1GB (2 x 512MB) 184-Pin DDR SDRAM DDR 400
The one thing I'm thinking I did that could have had any effect is that that day I used the motherboard's software to upgrade the bios. I also upgraded some of the chipset stuff. I remember seeing this Nvidia GART driver along with the rest of the stuff. Maybe I shouldn't have installed that. I can't imagine that killing the first drive and preventing me from detecting the other drive. I also notice this Nvidia Raid thing at bootup, but I don't have a raid setup. I don't remember how long that has been there, but I think it was there before Saturday.
Well, I just fixed my own problem. I uninstalled that GART driver as well as the Nvidia IDE driver. It's detecting it now and I'm formating it. That still doesn't help me with the other drive. Could those drivers have been causing the same problem? When put in that external drive, the drive wouldn't spin up unless it was on its side. So, either the drive was bad and stopped working correctly that day or those drivers really messed it up. I don't know. This whole situation has been weird.
While out at Staples today, we picked up a 200 gig Maxtor for $40. He let me put this one in and he's taking the one WD is sending us. I plug it in and start the computer up. It is not detected. I checked Disk management and the bios and neither detect it. I do not know what is wrong. It appears that the first one was a bad drive (made in June 05 and only used in the two months since being installed at Christmas), but I don't understand the new one not working. I even tried a different cable and nothing.
Here's my specs:
GIGABYTE GA-K8NSC-939 Socket 939
Antec PERFORMANCE TX TX1050B Black Steel Server Computer Case 500W ATX12V v2.0 Power Supply
AMD Athlon 64 3500+ Venice 1GHz FSB Socket 939
CORSAIR ValueSelect 1GB (2 x 512MB) 184-Pin DDR SDRAM DDR 400
The one thing I'm thinking I did that could have had any effect is that that day I used the motherboard's software to upgrade the bios. I also upgraded some of the chipset stuff. I remember seeing this Nvidia GART driver along with the rest of the stuff. Maybe I shouldn't have installed that. I can't imagine that killing the first drive and preventing me from detecting the other drive. I also notice this Nvidia Raid thing at bootup, but I don't have a raid setup. I don't remember how long that has been there, but I think it was there before Saturday.
Well, I just fixed my own problem. I uninstalled that GART driver as well as the Nvidia IDE driver. It's detecting it now and I'm formating it. That still doesn't help me with the other drive. Could those drivers have been causing the same problem? When put in that external drive, the drive wouldn't spin up unless it was on its side. So, either the drive was bad and stopped working correctly that day or those drivers really messed it up. I don't know. This whole situation has been weird.