From: David Greaves <david@dgreaves.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very strange RAID failure
Date: Wed, 19 Apr 2006 11:46:10 +0100 [thread overview]
Message-ID: <444614F2.4030607@dgreaves.com> (raw)
In-Reply-To: <20060419070522.GL10304@vitelus.com>
Aaron Lehmann wrote:
> I came back to my machine a few days ago and noticed strange behavior,
> and then found this in the logs:
>
>
> Apr 16 07:02:50 annexia kernel: ata1: command 0x35 timeout, stat 0x51 host_stat 0x60
> Apr 16 07:02:50 annexia kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> Apr 16 07:02:50 annexia kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
> Apr 16 07:02:50 annexia kernel: ata1: error=0x04 { DriveStatusError }
> Apr 16 07:02:50 annexia kernel: sd 0:0:0:0: SCSI error: return code = 0x8000002
> Apr 16 07:02:50 annexia kernel: sda: Current: sense key: Aborted Command
> Apr 16 07:02:50 annexia kernel: Additional sense: No additional sense information
> Apr 16 07:02:50 annexia kernel: end_request: I/O error, dev sda, sector 625137194
> Apr 16 07:02:50 annexia kernel: raid5: Disk failure on sda4, disabling device. Operation continuing on 3 devices
> Apr 16 07:02:50 annexia kernel: RAID5 conf printout:
> Apr 16 07:02:50 annexia kernel: --- rd:4 wd:3 fd:1
> Apr 16 07:02:50 annexia kernel: disk 0, o:0, dev:sda4
> Apr 16 07:02:50 annexia kernel: disk 1, o:1, dev:sdd4
> Apr 16 07:02:50 annexia kernel: disk 2, o:1, dev:sdb4
> Apr 16 07:02:50 annexia kernel: disk 3, o:1, dev:sdc4
go and search linux-ide for messages from me.
It looks similar to problems I've had that turned out to be 2.6.15
libata/fua bug.
David
--
prev parent reply other threads:[~2006-04-19 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 7:05 Very strange RAID failure Aaron Lehmann
2006-04-19 10:46 ` David Greaves [this message]
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=444614F2.4030607@dgreaves.com \
--to=david@dgreaves.com \
--cc=aaronl@vitelus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.