Disk Controller Failure on a Compaq Laptop

[IJump]

I have someone using a Compaq Armada 1700. Someimte, on the first boot of the day, she gets a 1782-Disk Controller Failure error and all the subsequent errors that go along with not having any hard drives detected. When I looked at it last, the Non-System Disk message was still on the screen. I turned the computer off, then back on, and everything worked. She tells me that this error appears to happen only when she is first booting after having the computer off and unplugged for a significant amount of time (such as overnight, etc.). FYI, the hard drive and screen/lid combo have been replaced in the past.

I have a couple of questions:

Could something like a bad CMos Battery cause this? I didn't think that would affect an ide controller, but with it happening after the computer is off and unplugged...... who knows. I can pretty much rule out a bad laptop battery because it happens when it is plugged in. The power supply is not likely or it would happen more often the the first boot of the day.

What else, other than a flakey controller, might cause intermittent errors like this, with a fairly predictable pattern?


Any help would be appreciated.

 

[Hessakia]

sounds like a failing hard drive.

 

[networkman]

I'd agree with that asessment.. however, a couple other things to look at.. is there a setting in the BIOS to allow for a Spin-Up time of a few seconds before checking the HDD? Some BIOS's have such a feature, while others do not. A flaky CMOS battery IS another possibility especially given that it only happens when the notebook is off for "long" periods of time.. after it's powered up, the Auto-detect probably then kicks in on the next boot and things proceed as normal.

So, in priority, I would boot the notebook - COPY OFF IMPORTANT DATA, then check BIOS setting for spin-up time, if it isn't available, replace the CMOS battery and test again after unit is fully charged. If problem still occurs, then a new hard drive would be a good idea. Or you can always send it into Service, though they'll follow the same procedures.

 

[jschuk]

It is also possible that the drive needs to be reseated. I have seen a lot of things get cured by reseating the device.

 

[Jwyatt]

maybe you should enroll on the Team Anandtech team before we answer or help in any way JK

Does it ever give this error when booting from floppy? Try it first thing and see if it does. If not then I would look at the HDD. If it does give errors when booting from floppy, i would think MB. Maybe pci controller?