A drive previously working as slave all of a sudden decides not to?

  • Thread starter Thread starter Yousuf Khan
  • Start date Start date
Y

Yousuf Khan

Some wierd things were happening on a relative's PC recently. I had
setup this PC for them originally, and they said they were having
trouble booting anymore, none of the drives were seen. I had two drives
on the primary channel, a 60G master and an older 20G slave. They were
both setup using cable select rather than hard-coding through the
jumpers as master/slave. This pair of drives had been working in this
combination for well over a year without a problem. Then all of a sudden
a couple of days back all hell breaks loose randomly. I was hard pressed
to find out what went wrong, even went so far as to replace the
motherboard (thought the IDE channel had died on the motherboard).
Eventually after trying it one drive at a time, I figured out it was a
problem only when the 20G drive was set as slave through cable select
this problem occurred. Funny thing is that I can hard-code it as slave
and it works fine. Oh, BTW, this same 20G drive works fine as cable
selected master, just not cable-selected slave.

Anybody have ideas what caused this?

Yousuf Khan
 
Yousuf Khan said:
Some wierd things were happening on a relative's PC recently. I had
setup this PC for them originally, and they said they were having
trouble booting anymore, none of the drives were seen. I had two
drives on the primary channel, a 60G master and an older 20G slave.
They were both setup using cable select rather than hard-coding
through the jumpers as master/slave. This pair of drives had been
working in this combination for well over a year without a problem.
Then all of a sudden a couple of days back all hell breaks loose
randomly. I was hard pressed to find out what went wrong, even went
so far as to replace the motherboard (thought the IDE channel had
died on the motherboard). Eventually after trying it one drive at a
time, I figured out it was a problem only when the 20G drive was set
as slave through cable select this problem occurred. Funny thing is
that I can hard-code it as slave and it works fine. Oh, BTW, this
same 20G drive works fine as cable selected master, just not
cable-selected slave.
Click to expand...
Anybody have ideas what caused this?
Click to expand...

The ribbon cable could have gone bad.

The 20G drive could have a faulty jumper or a bad joint in the jumper area.
 
Previously Yousuf Khan said:
Some wierd things were happening on a relative's PC recently. I had
setup this PC for them originally, and they said they were having
trouble booting anymore, none of the drives were seen. I had two drives
on the primary channel, a 60G master and an older 20G slave. They were
both setup using cable select rather than hard-coding through the
jumpers as master/slave. This pair of drives had been working in this
combination for well over a year without a problem. Then all of a sudden
a couple of days back all hell breaks loose randomly. I was hard pressed
to find out what went wrong, even went so far as to replace the
motherboard (thought the IDE channel had died on the motherboard).
Eventually after trying it one drive at a time, I figured out it was a
problem only when the 20G drive was set as slave through cable select
this problem occurred. Funny thing is that I can hard-code it as slave
and it works fine. Oh, BTW, this same 20G drive works fine as cable
selected master, just not cable-selected slave.
Click to expand...
Anybody have ideas what caused this?
Click to expand...
Yousuf Khan
Click to expand...

Maybe a bad contact in the cable... Although that seems rather
unlikely to me.

Arno
 
Rod said:
The ribbon cable could have gone bad.
Click to expand...

I had thought of that, and changed the cable too, as the first order of
business. That didn't work, so then I thought about the motherboard IDE
interface going bad.
The 20G drive could have a faulty jumper or a bad joint in the jumper area.
Click to expand...

Yeah, I suppose.


Yousuf Khan
 
Back
Top