From: Neil Brown <neilb@suse.de>
To: Mike <mikee@mikee.ath.cx>
Cc: linux-raid@vger.kernel.org
Subject: Re: FailSpare event?
Date: Fri, 12 Jan 2007 09:59:15 +1100 [thread overview]
Message-ID: <17830.49475.108136.376489@notabene.brown> (raw)
In-Reply-To: message from Mike on Thursday January 11
On Thursday January 11, mikee@mikee.ath.cx wrote:
>
> So I'm ok for the moment? Yes, I need to find the error and fix everything
> back to the (S) state.
Yes, OK for the moment.
>
> The messages in $HOST:/var/log/messages for the time of the email are:
>
> Jan 11 16:04:25 elo kernel: sd 2:0:4:0: SCSI error: return code = 0x8000002
> Jan 11 16:04:25 elo kernel: sde: Current: sense key: Hardware Error
> Jan 11 16:04:25 elo kernel: Additional sense: Internal target failure
> Jan 11 16:04:25 elo kernel: Info fld=0x10b93c4d
> Jan 11 16:04:25 elo kernel: end_request: I/O error, dev sde, sector 280575053
> Jan 11 16:04:25 elo kernel: raid5: Disk failure on sde2, disabling device. Operation continuing on 5 devices
Given the sector number it looks likely that it was a superblock
update.
No idea how bad an 'internal target failure' is. Maybe powercycling
the drive would 'fix' it, maybe not.
>
> On AIX boxes I can blink the drives to identify a bad/failing device. Is there
> a way to blink the drives in linux?
Unfortunately not.
NeilBrown
next prev parent reply other threads:[~2007-01-11 22:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 22:11 FailSpare event? Mike
2007-01-11 22:23 ` Neil Brown
2007-01-11 22:36 ` Mike
2007-01-11 22:59 ` Neil Brown [this message]
2007-01-11 23:06 ` Mike
2007-01-12 0:05 ` Mike Hardy
2007-01-12 0:40 ` Corey Hickey
2007-01-12 0:48 ` Martin Schröder
2007-01-12 14:34 ` Ernst Herzberg
2007-01-13 18:10 ` Nix
2007-01-13 23:34 ` Nix
2007-01-13 23:38 ` Nix
[not found] ` <45ABA3E4.3050800@tmr.com>
2007-01-15 19:59 ` Nix
2007-01-14 15:01 ` Nix
2007-01-14 21:20 ` Neil Brown
2007-01-15 20:08 ` Nix
2007-01-13 22:29 ` Mike
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=17830.49475.108136.376489@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mikee@mikee.ath.cx \
/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;
as well as URLs for NNTP newsgroup(s).