Quote:
|
Originally Posted by Undertoad
The event log has numerous bad block errors listed for drive D, even after the drive has been replaced. Therefore these errors are probably not actual errors, but a failing controller thinking they ARE errors.
|
The controller is actually nothing more than some drivers and receivers. However the chip that contains that 'controller' can be tested. First do something that constantly accesses the drive. This is what hardware diagnostics are for. Once you have established a pattern, and then selectively heat different sections with a hairdryer on high. Yes it must be that hot to a human and yet that cool to a computer. The offending part (i.e. semiconductor, cable connector, etc) identifies itself via increased errors with temperature.
As noted earlier, heat is a diagnostic tool.
Drive D is the original offending drive? Well, it may have bad drivers/receivers on its computer board. It might cause motherboard computer to not communicate with a C: drive computer. IDE bus is a network cable where each computer - drive computer from each disk and the motherboard computer all share time talking on that cable. Therefore problem could be slave drive computer, master drive computer, south bridge IC on motherboard, etc. This is what the hairdryer does. To make intermittents more frequent by applying heat. Find failures by running parts hotter - then do not fix those parts with more fans.
Hairdryer that causes any computer part to fail - that part is 100% defective. And that part will get worse with age.