From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Manuel Reimer" <Manuel.Spam@nurfuerspam.de>,
"Jeff Garzik" <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Massive IDE problems. Who leaves data here?
Date: Tue, 22 Jan 2008 12:46:32 -0800 [thread overview]
Message-ID: <2c0942db0801221246u678d2a20xef9cf93ee28eaf51@mail.gmail.com> (raw)
In-Reply-To: <fn5jsn$ful$1@ger.gmane.org>
(Please always do a reply-to-all for this email list.)
On Jan 22, 2008 12:40 PM, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
> Jeff Garzik wrote:
> > If your IDE interface is complaining about BadCRC errors, then it's
> > complaining about hardware problems (bad cable, etc.)
>
> The cable already has been replaced three times. I even got sure to
> *not* bend the cable. This all doesn't help.
>
> May a bad cable really cause corrupted data?
>
> I also have such messages for my cdrom drive (the bad sector messages at
> the end of the log for drive hdc). I replaced the 40 pin cable with a
> new 80 pin one and still have the errors...
Bad or almost bad power supplies can cause lots of unhappy problems
such as these. If you have another power supply laying around, it can
be worth swapping them out. Double-checking that your CPU fan is still
spinning, and that memtest86+ doesn't show any errors doesn't hurt
either.
next prev parent reply other threads:[~2008-01-22 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 20:24 Manuel Reimer
2008-01-22 20:25 ` Jeff Garzik
2008-01-22 20:40 ` Manuel Reimer
2008-01-22 20:46 ` Ray Lee [this message]
2008-01-22 21:04 ` Manuel Reimer
2008-01-22 21:12 ` Ray Lee
2008-01-24 16:25 ` Manuel Reimer
2008-01-24 16:26 ` Manuel Reimer
2008-01-22 23:50 ` Jan Engelhardt
2008-01-24 16:27 ` Manuel Reimer
2008-01-22 22:25 ` Alan Cox
2008-01-24 16:29 ` Manuel Reimer
2008-01-23 1:03 ` Bill Davidsen
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=2c0942db0801221246u678d2a20xef9cf93ee28eaf51@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=Manuel.Spam@nurfuerspam.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®