From: Erik Bourget <erik@midmaine.com>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CMD680, kernel 2.4.21, and heartache
Date: Fri, 03 Oct 2003 08:23:56 -0400 [thread overview]
Message-ID: <87lls2tspv.fsf@loki.odinnet> (raw)
In-Reply-To: <200310031159.h93BxfYm000758@81-2-122-30.bradfords.org.uk> (John Bradford's message of "Fri, 3 Oct 2003 12:59:41 +0100")
John Bradford <john@grabjohn.com> writes:
>> Some factors that are definitely NOT a problem: - Faulty run of drives.
>> This has also happened to Hitachi 80GB drives in the same configurations.
>>
>> - Heat. They're in a chilly room. The cases haven't overheated. We've had
>> guys checking this every few hours after the first one went bonkers.
>>
>> Possible problems -
>> - Simple software problem that somebody can fix and save the day. :)
>> - All Dell Poweredge 650 servers are broken. :/
>
>> Oct 1 07:47:47 mailstore2-1 kernel: hda: dma_intr: status=0x51 { DriveReady
>> SeekComplete Error } Oct 1 07:47:47 mailstore2-1 kernel: hda: dma_intr:
>> error=0x40 { UncorrectableError }, LBAsect=37694874, high=2, low=4140442,
>> sector=35220864
>
> That is definitely an error from the drive. If you're absolutely sure
> it's not a faulty batch of drives or a cooling issue, maybe you have
> power supply problems? Does SMART give you any useful information?
>
> John.
Not power supply problems; two of the machines that have this problem are
located in different facilities even. What's SMART?
Thanks,
- Erik
next prev parent reply other threads:[~2003-10-03 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 11:23 CMD680, kernel 2.4.21, and heartache Erik Bourget
2003-10-03 11:59 ` John Bradford
2003-10-03 12:23 ` Erik Bourget [this message]
2003-10-03 12:40 ` John Bradford
2003-10-03 12:48 ` Erik Bourget
2003-10-03 13:11 ` John Bradford
2003-10-03 18:10 ` Tomasz Rola
2003-10-03 18:22 ` Erik Bourget
2003-10-03 18:47 ` John Bradford
2003-10-04 1:57 ` jimbleferret
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=87lls2tspv.fsf@loki.odinnet \
--to=erik@midmaine.com \
--cc=john@grabjohn.com \
--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