Restoring the MBR: How the heck do you RUN MbrFix.exe?? Won't run in DOS and it won't run in XP!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Originally posted by: pcgeek11
I didn't say that the controller was making the SATA Cables bad. All of the data in and out of the drive goes through the SATA Controller if the controller is crap... any data going through gets crapped up, then it could cause these symptoms. The cables are probably good, and so are the drives.
pcgeek11
Yeah, I'm sure the drives are good. But why would the PC work fine each time I replaced the SATA cable? That's why I was asking what could make the cables go bad. No, I haven't checked them on another PC, but I will be interested in trying.

 

Scitex

Senior member
Oct 9, 1999
350
6
81
Maybe a problem with the connector on the motherboard? Are you using the same port each time?
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Originally posted by: Nothinman
Is it common for that chkdsk c: /r command to return that type of error? Have any of you run it error free to completion?

No and yes, respectively.

Yeah, my first post on this page:

Ah, it just completed with NO ERRORS! Well, no problems I should say, it completed and said "chkdsk found and fixed one or more errors on the volume". Went back into Windows again with no problem.

So it finally did run ok after the last SATA cable.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Originally posted by: Scitex
Maybe a problem with the connector on the motherboard? Are you using the same port each time?

No, I even tried the "SATA2" port and got the same thing. It worked fine after the last SATA cable I used and continued to pass all tests, no issues, seemed perfect. So, it shipped.

The only other explanation I may have, it's some type of EMR, RF, EMI, etc., interference. I did have the SATA folded and tucked away behind the HD bay tray area. I think it was touching a USB data cable that went to the front panel of the case, or at least very close. I've never seen a USB cable interfere with a HD. It was touching the metal tray, but I've never seen an issue with that before either. If some kind of "inductive reactive" phenomenon took place with the metal case with the power cables against it at certain areas, and if the moon phase, temperature, humidity, planetary alignment, etc., was just right, :roll: I guess perhaps that might cause some issue if the SATA cable was making contact with the case.
 

computer

Platinum Member
Nov 5, 2000
2,735
2
0
Originally posted by: computer
No, I even tried the "SATA2" port and got the same thing. It worked fine after the last SATA cable I used and continued to pass all tests, no issues, seemed perfect. So, it shipped.

The only other explanation I may have, it's some type of EMR, RF, EMI, etc., interference. I did have the SATA folded and tucked away behind the HD bay tray area. I think it was touching a USB data cable that went to the front panel of the case, or at least very close. I've never seen a USB cable interfere with a HD. It was touching the metal tray, but I've never seen an issue with that before either. If some kind of "inductive reactive" phenomenon took place with the metal case with the power cables against it at certain areas, and if the moon phase, temperature, humidity, planetary alignment, etc., was just right, :roll: I guess perhaps that might cause some issue if the SATA cable was making contact with the case.

Oh, I need to add that after I tried the last cable, I DID NOT put the cable back where it was! I left that mofo SOB alone!! I just folded it up and "sleeved" it just behind the HD and out the way of the fan. I wasn't about to screw around with it since it was working fine.