|
|
 |
|
|
Pages: 1
Hard Disk light problem?
(Click here to view the original thread with full colors/images)
Posted by: The-AoD
Ok, lets make this simple, I have a problem but it's not very "important". I'd like to fix the problem anyways.
Problem:
During boot, before windows or any operating system, my HDD light seems to be stuck on. I have the HDD's on the onboard ATA/66 controller. I haven't noticed this since lately, but I never really did pay much attention to it. It's just stuck on until the ATA controller detects the disks. Sometimes, after hard locks (only happens with Diablo 2) the ATA controller doesn't detect the disks.
System:
I have a Soyo 6ba+ IV with the Onboard HPT366 ATA controller. It has two Standard IDE ports as well, so the ATA controller is used like an add-on controller. I have the two Hard Disks (Maxtor Diamond Max 45gb and Quantum Bigfoot 8.4gb) on the Secondary line. If I run them on the primary, windows will not detect the CD-Rom, stupid Generic ATAPI. I have the CD-Rom as the Secondary Slave on the Standard IDE controllers. This is one combination that works with the CD-Rom, and I never felt like switching it around.
Could the arrangement cause the problem? What could be the reason for the Controller not picking up the drives after a hard lock?
Things I've done:
I've installed the Latest BIOS upgrade for the HPT366 BIOS. I've checked both Hard Disks for errors with thier utilities for the specified drive. I personally doubted that it could be the way I have the drives arranged on the Controller. I've tried updating the drivers for the ATA controller for windows, thinking that the light would go off and not come back on when windows was restarted, to no avail.
Other Information:
I've tried switching cables for the driver, but that did not solve anything. I've tried the string that I found from a Technical support website for the ATA controller, that didn't help any either.
Thanks for your time,
AoD
Posted by: Ion Silverbolt
Well both your ATA controller and your hard drives are overclocked. Even if it wasn't a problem before, hardware becomes less heat tolorent as it ages and is used. Them not being detected after a hard lock screams of a hardware problem. That leads me to believe there's either a heat or voltage problem going on. Or it could be something like one of the hard drives getting ready to barf. (For good)
When you're overclocking, you're placing extra demand on all components in the system. Do you have motherboard monitor? It could be a voltage sag causing the problem. Especially if the power supply is starting to get old.
You could try unplugging one of the drives if possible just to see if the problem stops.
Posted by: The-AoD
I've got the Soyo Mobo Monitor, and all the voltages are within perfect regulations. As for the not being detected, it hasn't done that in a rather long time, probably more than two weeks. The last thing I've done considering that problem would be setting the Standard IDE controllers to a disabled PIO mode to UDMA 33. I don't know if that fixed it, but the Standard IDE controller is acting as an ATA/33 only controller now, since the ATAPI drive supports ATA/33, I figured, why not?
As for the light problem, I don't know what the heck is going on with that, I've checked both drives with the latest Powermax utilities and they both check out. Factory Re-Authorizations are met and all systems seem to be go. I don't know the answer to this to the life of me, but I have the HDD's set as the Primary channel now, and still, that light is on. I'm starting to think it's just the motherboard and I haven't noticed it yet. I've taken the front cover off of the case to modify a place for a fan for the Maxtor. I've only noticed this since then. I've tried removing the fan from the power supply, but that didn't solve the light issue. I've locked up D2 7 times now, since I know how to lock D2 up(just hire an act 5 mercenary lol) and there hasn't been one detection error.
I also just got done trying something else that gave me quite a thrill ride. The Promise Technologies Maxtor ATA/100 controller, I dug it up and tried it with the drives. And the HDD light never came on until the detection took place, then it went back off, like it should normally. After that speculation took place, I attempted the Standard IDE channels and, the light problem persisted. I don't know what is up with this light, could it be the Motherboards BIOS? It's nothing big, it's just something that I've noticed lately. Other than that, there hasn't been a single problem with the thing.
Posted by: Ion Silverbolt
It sounds to me like the IDE cdontroller on your motherboard is going bad. That is provided you're using it at normal Bus settings.
I used to have a K6 300 with the FSB overclocked to 75Mhz and used to have the EXACT same drive problem you're having. Worked fine when I clocked back down. It happened so rarely that I didn't mind it though.
Posted by: The-AoD
Ohh, the light problem still occurs at stock clock, as a matter of fact, I goto stock clock alot. Specially when I don't feel like hearing my fan orchestra lol.
|
|
|
|
|