DUX COMPUTER DIGEST

 

Site Search

Site Info

Home » Forums » Forum Archives » Disk Drives » Topic # 207

Drive went bad
abNORMal Sep-17-01 11:51 AM
Strange thing happened this weekend.
A friend of mine called and told me her machine wouldn't boot, and she had a message that the hard drive wasn't being found.

I tried a new cable and some other troubleshooting, but couldn't get it to recognize that a hard drive existed. I then took the drive, jumpered it as a slave and hooked it into another machine. (I used the cable connector in the middle of the hard drive ribbon cable which was hooked to the CD player). When it tried to boot, it couldn't recognize its master drive! (let alone the slave drive.) I tried cable select with the same result.

I'm puzzled as to why the presence of a slave drive (good or bad) would prevent the machine from finding the master drive.


1. RE: Drive went bad
lbyard Sep-17-01 05:01 PM
In response to message 0
The Master drive may have a jumper setting for Master with Slave present; e.g., Western Digital drives. The problem with the Slave drive could prevent any drive on the same cable from being detected/booting. Some drives, especially old ones, simply will not work with drives from other manufacturers or as Slave to drives from other manufacturers--they may work as a Master. Try connecting the drive to be tested to the secondary IDE interface, if there is one. Larry

2. RE: Drive went bad
abNORMal Sep-17-01 07:19 PM
In response to message 1
Thanx Larry.

| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |