From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: linux-raid@vger.kernel.org
Subject: raid5 degraded twice, what happened here?
Date: Sun, 29 Mar 2009 22:38:20 +0200 [thread overview]
Message-ID: <200903292238.23416.Dexter.Filmore@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]
During the last two weeks my raid5 array degraded while shutting down.
Here's what happened at shutdown last time according to logs:
Mar 29 05:16:27 xerxes shutdown[5690]: shutting down for system halt
Mar 29 05:16:58 xerxes kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 29 05:16:58 xerxes kernel: ata3: soft resetting port
Mar 29 05:17:03 xerxes kernel: ata3: port is slow to respond, please be
patient (Status 0xd0)
Mar 29 05:17:07 xerxes kernel: ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Mar 29 05:17:37 xerxes kernel: ata3.00: qc timeout (cmd 0xec)
Mar 29 05:17:37 xerxes kernel: ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x4)
Mar 29 05:17:37 xerxes kernel: ata3: failed to recover some devices, retrying
in 5 secs
Mar 29 05:17:42 xerxes kernel: ata3: hard resetting port
Mar 29 05:17:48 xerxes kernel: ata3: port is slow to respond, please be
patient (Status 0xff)
Mar 29 05:17:52 xerxes kernel: ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Mar 29 05:17:52 xerxes kernel: ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x3)
Mar 29 05:17:52 xerxes kernel: ata3.00: limiting speed to UDMA/100:PIO3
Mar 29 05:17:52 xerxes kernel: ata3: failed to recover some devices, retrying
in 5 secs
Mar 29 05:17:57 xerxes kernel: ata3: hard resetting port
Mar 29 05:18:02 xerxes kernel: ata3: port is slow to respond, please be
patient (Status 0xff)
Mar 29 05:18:06 xerxes kernel: ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Mar 29 05:18:06 xerxes kernel: ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x3)
Mar 29 05:18:06 xerxes kernel: ata3.00: disabled
Mar 29 05:18:07 xerxes kernel: ata3: EH complete
Mar 29 05:18:07 xerxes kernel: sd 2:0:0:0: [sdb] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Mar 29 05:18:07 xerxes kernel: end_request: I/O error, dev sdb, sector
976751807
Mar 29 05:18:07 xerxes kernel: md: super_written gets error=-5, uptodate=0
Mar 29 05:18:07 xerxes kernel: RAID5 conf printout:
What is this? Controller screwup? Disk oops? Software thing?
Debian Etch r7, mdadm 2.5.6.
Dex
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
http://www.vorratsdatenspeicherung.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2009-03-29 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200903292238.23416.Dexter.Filmore@gmx.de \
--to=dexter.filmore@gmx.de \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).