Ok, so far I've managed to fix this issue already. Not entirely certain how I did it because all of what I did didn' work initially, then something that shouldn't have worked did. Anyways, getting to the point. For a period of about 2-3 months I had a problem where my 2nd HD on my computer kept recycling every couple of hours. It's that same sound you hear when the bios completely resets your HD or when you first power on the computer and your HD's go through a quick self test. It's also the same sound if your HD's were encountering too many errors and they reset to try to reorient themselves so that they could find the data they were after again.
I had swapped cables, swapped drives, and tried everything I could think of and yet whatever drive was in there on the primary slave, it still acted up. Then suddenly one day it stopped doing it. No reason. It just stopped. Nothing I did for certain except running the IBM drive test utility several times because one of the drives was detected but couldn't be contacted for testing. I think this happened after I finally got the drive to be not only seen by the testing utility but actually able to be tested as well. I swapped several drives back and forth in an effort to see if it was just one drive or the cable or the controler or what it might be. I even swapped cables. Strange thing was, it just suddenly became visible to the testing utility and since then I haven't had one single reset.
Another strange thing about the issue I was having was that when it would do its little reset number there was no signs that the computer was acting up in any way. I could even be copying files to and from the drive and yet the computer wouldn't gag, pause, or show any signs that a reset had happened. That's what made it even weirder.
I welcome your comments on this as to what might have been happening.
I had swapped cables, swapped drives, and tried everything I could think of and yet whatever drive was in there on the primary slave, it still acted up. Then suddenly one day it stopped doing it. No reason. It just stopped. Nothing I did for certain except running the IBM drive test utility several times because one of the drives was detected but couldn't be contacted for testing. I think this happened after I finally got the drive to be not only seen by the testing utility but actually able to be tested as well. I swapped several drives back and forth in an effort to see if it was just one drive or the cable or the controler or what it might be. I even swapped cables. Strange thing was, it just suddenly became visible to the testing utility and since then I haven't had one single reset.
Another strange thing about the issue I was having was that when it would do its little reset number there was no signs that the computer was acting up in any way. I could even be copying files to and from the drive and yet the computer wouldn't gag, pause, or show any signs that a reset had happened. That's what made it even weirder.
I welcome your comments on this as to what might have been happening.
Facebook
Twitter