• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Spinrite reported Cabling Error

QueBert

QueBert

Lifer
I got 50 Cabling errors while scanning my 320 gig SATA WD drive, of course Google turns up nothing and I emailed the dude who makes it but he hasn't gotten back to me.

My initial thought was it was reporting the cable was bad, but I don't think it's possible to detect a bad SATA cable with software is it? Any ways, I rebooted, switched the SATA cable from both my drives figuring if it was the cable it should logically give me the same error on my other drive, of course it didn't though. I switched the cables back to the original, ran Spinrite again and no errors at all. I know something is up with my PC, my XP would lock up and require a reboot, and sometimes I'd have to reboot 4-5 times to actually get windows to load. Since the problem I have unhooked the 320 gig drive (one I suspect is causing the issues) and haven't had a lock up.

I ran the WD DIAG program and it claims my drives are both fine, there is something going on with the 320 gig though, if I RMA it even after their program says it's error free will they even take it back?
 
I'm assuming Spinrite isn't making an assumption about the cable itself. It's probably not sensing certain signaling.

Since you --in actuality-- reseated the SATA cable on both the other drive and the original, I wouldn't be surprised you didn't get errors the second time.

Why not reseat the cable again on the problematic drive and see if it boots OK.

Doesn't WD have those "SecureConnect" SATA cables you could use? They provide a much more enveloping connection to the drive. Note: If you use one, you'll also have to use the legacy 4-pin power connection, as the SecureConnect cable needs both the SATA power and the legacy power to work.
 
my Raptor has some funky SATA cable that's hellova wide, don't think it could possible come loose like older cables, the other drive has one with the metal clip on it - is the first one what you're talking about? It's possible one of the cables was loose and that was giving me the problem in the first place.
 
It's this cable:

http://www.amazon.com/dp/B00012PSB8/ref...3&creativeASIN=B00012PSB8&linkCode=asn

I posted the Amazon link above because it's the cheapest I saw for it.

Says it works with both Raptors and Caviar "SE" SATA drives.

And yes, it's certainly possible the cable was loose causing the issues.

Remember this note:

Important compatibility note: When using the WD SecureConnect cable, you must use the legacy power adapter because the SecureConnect cable utilizes the SATA power port to provide additional stability.
 
I have a million SATA cables if that's the problem, but I'll assume it was just loose because like I said when I rehooked the drives as they first were where I got the error, Spinrite didn't report nothing *shrug*
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top