From: Carlos Hendson <skyclan@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [HELP] Intermittent software RAID failures
Date: Thu, 18 Mar 2010 22:45:03 +0100 [thread overview]
Message-ID: <4BA29EDF.3010001@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hello,
I've got a Dell Inspiron 1720 laptop with dual 2.5" hard drives setup
using software RAID1. I've had this computer for about a year and half
and all's been working well.
I've experienced intermittent software RAID errors like those found in
the "softraid-fail.txt" attachment.
Initially I suspected a kernel bug because it started around the same
time I'd upgraded the kernel (around the 2.6.30 upgrade) but subsequent
kernel upgrades haven't improved the situation.
I've run smartctl --all and bablocks on both disks, but nothing is
reported as faulty.
I don't understand what is causing RAID to report these faults and would
like some ideas as to how I can further diagnose the problem.
Thanks in advance,
Carlos
[-- Attachment #2: softraid-fail.txt --]
[-- Type: text/plain, Size: 6799 bytes --]
Feb 28 15:14:16 pheonix kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
Feb 28 15:14:16 pheonix kernel: ata3.00: irq_stat 0x00400000, PHY RDY changed
Feb 28 15:14:16 pheonix kernel: ata3: SError: { PHYRdyChg }
Feb 28 15:14:16 pheonix kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 28 15:14:16 pheonix kernel: res 40/00:0c:97:74:25/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Feb 28 15:14:16 pheonix kernel: ata3.00: status: { DRDY }
Feb 28 15:14:16 pheonix kernel: ata3: hard resetting link
Feb 28 15:14:19 pheonix kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 28 15:14:19 pheonix kernel: ata3.00: configured for UDMA/133
Feb 28 15:14:19 pheonix kernel: ata3: EH complete
Feb 28 15:14:19 pheonix kernel: end_request: I/O error, dev sdb, sector 178062452
Feb 28 15:14:19 pheonix kernel: raid1: Disk failure on sdb1, disabling device.
Feb 28 15:14:19 pheonix kernel: raid1: Operation continuing on 1 devices.
Feb 28 15:14:19 pheonix kernel: md: recovery of RAID array md0
Feb 28 15:14:19 pheonix kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Feb 28 15:14:19 pheonix kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Feb 28 15:14:19 pheonix kernel: md: using 128k window, over a total of 178024192 blocks.
Feb 28 15:14:19 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Feb 28 15:14:19 pheonix kernel: md: md0: recovery done.
Feb 28 15:14:19 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:19 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:19 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:19 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:19 pheonix kernel: md: recovery of RAID array md0
Feb 28 15:14:19 pheonix kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Feb 28 15:14:19 pheonix kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Feb 28 15:14:19 pheonix kernel: md: using 128k window, over a total of 178024192 blocks.
Feb 28 15:14:19 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Feb 28 15:14:19 pheonix kernel: md: md0: recovery done.
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:20 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Feb 28 15:14:20 pheonix kernel: disk 1, wo:1, o:0, dev:sdb1
Feb 28 15:14:20 pheonix kernel: RAID1 conf printout:
Feb 28 15:14:20 pheonix kernel: --- wd:1 rd:2
Feb 28 15:14:20 pheonix kernel: disk 0, wo:0, o:1, dev:sda8
Mar 12 19:38:06 pheonix kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
Mar 12 19:38:06 pheonix kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed
Mar 12 19:38:06 pheonix kernel: ata1: SError: { PHYRdyChg }
Mar 12 19:38:06 pheonix kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 12 19:38:06 pheonix kernel: res 40/00:24:b6:fa:df/00:00:17:00:00/40 Emask 0x10 (ATA bus error)
Mar 12 19:38:06 pheonix kernel: ata1.00: status: { DRDY }
Mar 12 19:38:06 pheonix kernel: ata1: hard resetting link
Mar 12 19:38:09 pheonix kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 12 19:38:09 pheonix kernel: ata1.00: configured for UDMA/133
Mar 12 19:38:09 pheonix kernel: ata1: EH complete
Mar 12 19:38:09 pheonix kernel: end_request: I/O error, dev sda, sector 305244964
Mar 12 19:38:09 pheonix kernel: raid1: Disk failure on sda8, disabling device.
Mar 12 19:38:09 pheonix kernel: raid1: Operation continuing on 1 devices.
Mar 12 19:38:09 pheonix kernel: md: recovery of RAID array md0
Mar 12 19:38:09 pheonix kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Mar 12 19:38:09 pheonix kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Mar 12 19:38:09 pheonix kernel: md: using 128k window, over a total of 178024192 blocks.
Mar 12 19:38:09 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Mar 12 19:38:09 pheonix kernel: md: md0: recovery done.
Mar 12 19:38:09 pheonix kernel: RAID1 conf printout:
Mar 12 19:38:09 pheonix kernel: --- wd:1 rd:2
Mar 12 19:38:09 pheonix kernel: disk 0, wo:1, o:0, dev:sda8
Mar 12 19:38:09 pheonix kernel: disk 1, wo:0, o:1, dev:sdb1
Mar 12 19:38:09 pheonix kernel: md: recovery of RAID array md0
Mar 12 19:38:09 pheonix kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Mar 12 19:38:09 pheonix kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Mar 12 19:38:09 pheonix kernel: md: using 128k window, over a total of 178024192 blocks.
Mar 12 19:38:09 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Mar 12 19:38:09 pheonix kernel: md: md0: recovery done.
Mar 12 19:38:09 pheonix kernel: RAID1 conf printout:
Mar 12 19:38:09 pheonix kernel: --- wd:1 rd:2
Mar 12 19:38:09 pheonix kernel: disk 0, wo:1, o:0, dev:sda8
Mar 12 19:38:09 pheonix kernel: disk 1, wo:0, o:1, dev:sdb1
Mar 12 19:38:09 pheonix kernel: md: recovery of RAID array md0
Mar 12 19:38:09 pheonix kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Mar 12 19:38:09 pheonix kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Mar 12 19:38:09 pheonix kernel: md: using 128k window, over a total of 178024192 blocks.
Mar 12 19:38:09 pheonix kernel: md: resuming recovery of md0 from checkpoint.
Mar 12 19:38:09 pheonix kernel: md: md0: recovery done.
Mar 12 19:38:10 pheonix kernel: RAID1 conf printout:
Mar 12 19:38:10 pheonix kernel: --- wd:1 rd:2
Mar 12 19:38:10 pheonix kernel: disk 0, wo:1, o:0, dev:sda8
Mar 12 19:38:10 pheonix kernel: disk 1, wo:0, o:1, dev:sdb1
Mar 12 19:38:10 pheonix kernel: md: recovery of RAID array md0
Mar 18 21:57:33 pheonix kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
Mar 18 21:57:33 pheonix kernel: ata3.00: irq_stat 0x00400000, PHY RDY changed
Mar 18 21:57:33 pheonix kernel: ata3: SError: { PHYRdyChg }
Mar 18 21:57:33 pheonix kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 18 21:57:33 pheonix kernel: res 40/00:24:bf:1c:1f/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Mar 18 21:57:33 pheonix kernel: ata3.00: status: { DRDY }
Mar 18 21:57:33 pheonix kernel: ata3: hard resetting link
Mar 18 21:57:37 pheonix kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 18 21:57:37 pheonix kernel: ata3.00: configured for UDMA/133
Mar 18 21:57:37 pheonix kernel: ata3: EH complete
Mar 18 21:57:37 pheonix kernel: end_request: I/O error, dev sdb, sector 178116972
next reply other threads:[~2010-03-18 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 21:45 Carlos Hendson [this message]
2010-03-18 21:58 ` [gentoo-user] [HELP] Intermittent software RAID failures Mark Knecht
2010-03-18 22:45 ` Keith Dart
2010-03-19 8:11 ` Carlos
2010-03-19 14:37 ` Volker Armin Hemmann
2010-03-19 14:33 ` Paul Hartman
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=4BA29EDF.3010001@gmx.net \
--to=skyclan@gmx.net \
--cc=gentoo-user@lists.gentoo.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