• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Any ideas why new system wont see my 2ndary Hard Drive?

C

Compddd

Golden Member
Running a Intel D875PBZ with latest Bios Revision with 1GB of 3200LL Corsair TwinX and P4 3.0C with a 120 GB 8MB Maxtor and a 30GB Maxtor for the 2ndary, My system runs fine with just the 120 hooked up, but when I hook up the 30 to the slave connection on the ide cable, the system wont see any of my drives, the DVD Rom, the 120, or the 30. I have the 30's jumper set to Slave and it worked fine on my old 1066 Rambus mobo, and just to make sure I hooked the 30 up to my Other computer and it worked fine. Any ideas?
 
I forgot to mention that I formatted and installed WinXp on the 30 using my old motherboard, I know that you cant boot up a HD with XP with XP having all the old motherboard info in it, could that be my problem?
 
Start with the simple tests first. Make certain the jumper settings are correct or if you're opting for "cable-select" make certain that your jumpers reflect this. Reseat the power connector and the ide cable. make certain that the hdd is powering up during the initial boot (pull the box apart so that you can hear or touch the drive to make certain the platters are spinning), if in doubt, try switching the power connectors from one hdd to the other. Interrupt the bootup and go to CMOS and see if it's being recongized there; if not, see if you can manually input the hdd info (you'll need some data off the hdd so be prepared). If all of that fails, try connecting it as the master hdd and see if the system will recognize it then. If all of these options fail, 90% chance that you have a bad hdd. One last test would be to try it in a friend's system.

I had a system that would randomly ignore my hdd; turned out to be a faulty mb that was resetting cmos info and not recognizing the hdd. I would have to manually input the hdd info, then it would be fine. Replaced the mb with same unit and it worked fine.

good luck
 
Bacillus was right, it was the cable, the cable is one of those rounded ata 133 glow in the dark cables, I tried a diff cable and both drives booted up flawlessly, guess its time to take the glow in the dark cable back and get a refund 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top