Linux ATA/IDE development
 help / color / mirror / Atom feed
From: scar <scar-47zfDnpWZoPQT0dZR+AlfA@public.gmane.org>
To: linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: troubleshoot disk problems / libata error messages
Date: Mon, 17 Jun 2013 07:45:43 -0700	[thread overview]
Message-ID: <kpn7ej$rdc$1@ger.gmane.org> (raw)
In-Reply-To: <201306150442.37242.gheskett-ouEgS7marmk@public.gmane.org>

Gene Heskett @ 06/15/2013 01:42 AM:
> On Saturday 15 June 2013 04:08:13 scar did opine:
>> i've been having HDD issues lately, and the issues have persisted across
>> two different disks and two different SATA ports on the motherboard
>>
> That hot red plastic die used to color MOST sata cables is a time bomb.  
> That particular red die causes the copper in the cables to embrittle and 
> connectivity goes away, like its some sort of acid.  
> 
> Ditch the hot red colored cables.  They are a time bomb that WILL go off, 
> sooner rather than later.  

thank you Gene for this insightful input.  all five of my internal disks
use these red cables! ;~;  i will check local hardware store for
alternatives.  BTW i finally got the ata3 errors, the other SError was
Handshk[1].

1. http://pastie.org/private/txwmbwyuot2sebmlrigp9g


--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-06-17 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  4:17 troubleshoot disk problems / libata error messages scar
2013-06-15  8:42 ` Gene Heskett
     [not found]   ` <201306150442.37242.gheskett-ouEgS7marmk@public.gmane.org>
2013-06-17 14:45     ` scar [this message]
2013-06-17 15:23       ` Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='kpn7ej$rdc$1@ger.gmane.org' \
    --to=scar-47zfdnpwzopqt0dzr+alfa@public.gmane.org \
    --cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox