• 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.

HDD Recognition.

I

imported_Fluffy

Member
A Seagate set up as a slave drive isn't recognized by the computer. The jumpers and connections are set up properly, but windows and DOS still won't recognize the HDD as plugged in.

Any suggestions?
 
i would first take out the master and see if you can get the Seagate to see as master, try changing IDE channels as well, if neither detect it, and you even tried putting it on the same molex connector, and IDE cable as the previous master, i think you might be looking for an RMA

but then there is always the possability of an incompatability. Or maybe the BIOS isnt new enuf to recognize it. how big is the drive? what kind of board are you plugging it into?
 
Paperlantern pretty much described the bulk and I would definitely follow up on that, and also for the rest of us which are very forgetful, there are negligible things that I'll make a checklist for just in case


Firstly, I would go into BIOS and do a little check there, I know the newer motherboards have AUTODETECT but sometimes you never know.

Also, I would make sure the IDE cables are connected correctly, (Master is outer and Slave is inner) and then I'd just check to see that the jumper is set to Cable Select.

Then I would go to Paperlantern's suggestions.

Lastly, I would download Seatools do a full diagnostic test, and see if the hard drive is really the problem.
 
In reply to Paperlantern, the drive is a 40GB Seagate, and that's about all I know of it. I'm not sure of the board make/model/etc. either (most likely Intel).

The computer was built from a slew of parts collected from other computers as project in IT class. Perhaps the drive was jarred or something else physically related. Hard to say.

It actually belongs to a friend of mine, I'll tell him to run the serials through Google. (Where would we be without Google?)

I'll relate these troubleshoots to him. Thanks for the advice.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top