9 Legend

 • 

87.5K Posts

May 22nd, 2015 05:00

The system likely needed only a new hard drive in the first place.  Before authorizing a repair, if you have not tried a simple drive replacement, that would give you the definitive answer.

4 Posts

May 22nd, 2015 08:00

Dell's repair facility has the computer, so I can't really do much to check. They were going to replace the drive, but found this motherboard/hard drive connection issue. I have the hard drive (I removed it). I'm wondering if the connection issue could be the issue causing the 2000-142 error, and that maybe the hard drive is fine.

When you say that it likely needed  only a hard drive in the first place, are you suggesting that this newfound motherboard issue is unfounded, like maybe they are driving up the cost for the repair?

Not sure if I should have them replace the board only and try it out with the original drive, or pay for both the new drive and board replacement. Hard to say.

9 Legend

 • 

87.5K Posts

May 22nd, 2015 09:00

It's not clear that the "a connection on the mainboard is compromised" has anything to do with the hard drive.  In any case, the hard drive is likely faulty.  Whether anything else is, I doubt anyone can determine without seeing the system. 

4 Posts

May 22nd, 2015 16:00

I understand. Thanks for replying.

One last question: In theory (or practice), if the connection from the HD to the motherboard on a laptop has failed for some reason or another, can this cause the 2000-142 error message? Is that error code strictly indicative of a failed HD, having nothing to do with the connection between the HD and 'board?

Thanks again.

4 Posts

May 22nd, 2015 16:00

Gotcha'. Thanks so much for your response(s). I really appreciate it; makes me feel confident that the HD is bad. As for this motherboard HD connection issue, I'll just have to trust them on that, and have the 'board replaced too, I suppose. That's the way it goes. 

Thanks again for your help. Take care.

9 Legend

 • 

87.5K Posts

May 22nd, 2015 16:00

The error is reported by the logic board on the drive itself - so it's genuine.  All the interface does is carry the signal reported to the system by the drive's controller -- there's no way it could be generated by a faulty connector (in fact I'd guess the opposite - if a drive were failing and connected through a faulty connector, you would in fact be more likely not to see the error if the interface blocked it being reported).

No Events found!

Top