- Oct 9, 1999
- 4,999
- 106
- 106
There appears to be a problem with these 2 boards that i know of for sure with some WD hard drives. The problem appears to be something that WD changed in the drive itself that is actually causing it. Basically this is what happens. If one of these drives is connected to one of the IDE channels in any jumper configuration the board gets stuck in what I can only describe as a detection loop. All that is needed is to have the drive connected to one of the ide cables Even if there is no power on the drive it still happens. Jumper configuration makes no difference at all. I have seen it with my own K7N2-L board with a WD600BB drive manufactured OCT2001 and there is a long thread at nForcersHQ detailing the identical problem with Leadtech board. I spoke with WD tech support and while they didn't give an explanation for the problem they did say they were sending me a modified cable that they thought might correct the issue. One of the guys at nForcersHQ forums pointed me to an old thread in WD technical forums detailing an identical issue last year with these drives and the Abit KT7-RAID. The dirty fix they came up with at WD was to cut the 2 wires that go to pin 1 on the ata66/100/133 cable. This got me thinking that that was probably the cable modification in the cable they were sending me so I grabbed one of my old 80 conductor cables and clipped the 2 pin 1 wires. That corrected it the drive detects perfectly and quickly and appears to be functioning correctly so far. The drives that appear to have the issue that i saw noted were WD200, WD300, WD400, and at least some of the WD600BB drives. All the drives that did this that were mentioned were manufactured late summer and fall of 2001 as far as i can tell which isn't to say that newer nones don't i just haven't head of any yet. If anyone experiences this issue try the cable mod. At this time it doesn't appear to be the fault of the board but rather something that WD was doing differently with some of their drives.
Facebook
Twitter