From: Jeff Garzik <jeff@garzik.org>
To: Steve Fairbairn <steve@fairbairn-family.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: HDD errors in dmesg, but don't know why...
Date: Mon, 18 Feb 2008 15:18:47 -0500 [thread overview]
Message-ID: <47B9E827.4060800@garzik.org> (raw)
In-Reply-To: <13c501c87264$411461d0$0603a8c0@meanmachine>
Steve Fairbairn wrote:
> Hi All,
>
> I've got a degraded RAID5 which I'm trying to add in the replacement
> disk. Trouble is, every time the recovery starts, it flies along at
> 70MB/s or so. Then after doing about 1%, it starts dropping rapidly,
> until eventually a device is marked failed.
>
> When I look in dmesg, I get the following...
>
> SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
> sdd: Write Protect is off
> sdd: Mode Sense: 00 3a 00 00
> SCSI device sdd: drive cache: write back
> ata5.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x0
> ata5.00: (irq_stat 0x00060002, device error via SDB FIS)
> ata5.00: cmd 60/00:10:3f:0e:f9/01:00:00:00:00/40 tag 2 cdb 0x0 data
> 131072 in
> res 41/40:00:50:0e:f9/9c:00:00:00:00/40 Emask 0x9 (media error)
> ata5.00: configured for UDMA/100
> ata5: EH complete
> SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
> sdd: Write Protect is off
> sdd: Mode Sense: 00 3a 00 00
> SCSI device sdd: drive cache: write back
> ata5.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x0
> ata5.00: (irq_stat 0x00060002, device error via SDB FIS)
> ata5.00: cmd 60/00:18:3f:02:f9/01:00:00:00:00/40 tag 3 cdb 0x0 data
> 131072 in
> res 41/40:00:c3:02:f9/9c:00:00:00:00/40 Emask 0x9 (media error)
"media error" means just that -- your hard drive is reporting bad media
to libata, which in turn dutifully reports that info to you :)
Jeff
prev parent reply other threads:[~2008-02-18 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 19:27 HDD errors in dmesg, but don't know why Steve Fairbairn
2008-02-18 19:38 ` Justin Piszcz
2008-02-18 20:18 ` Jeff Garzik [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=47B9E827.4060800@garzik.org \
--to=jeff@garzik.org \
--cc=linux-raid@vger.kernel.org \
--cc=steve@fairbairn-family.com \
/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.