* HDD errors in dmesg, but don't know why...
@ 2008-02-18 19:27 Steve Fairbairn
2008-02-18 19:38 ` Justin Piszcz
2008-02-18 20:18 ` Jeff Garzik
0 siblings, 2 replies; 3+ messages in thread
From: Steve Fairbairn @ 2008-02-18 19:27 UTC (permalink / raw)
To: linux-raid
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)
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: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)
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 0x3ff 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
I've no idea what to make of these errors. As far as I can work out,
the HD's themselves are fine They are all less than 2 months old.
The box is CentOS 5.1. Linux space.homenet.com 2.6.18-53.1.13.el5 #1
SMP Tue Feb 12 13:02:30 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Any suggestions on what I can do to stop this issue?
Steve.
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.7/1284 - Release Date:
17/02/2008 14:39
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: HDD errors in dmesg, but don't know why...
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
1 sibling, 0 replies; 3+ messages in thread
From: Justin Piszcz @ 2008-02-18 19:38 UTC (permalink / raw)
To: Steve Fairbairn; +Cc: linux-raid
Looks like your replacement disk is no good, the SATA port is bad or other
issue. I am not sure what SDB FIS means but as long as you keep getting
that error, don't expect the drive to work correctly, I had a drive that
did a similar thing (DOA Raptor) and after I got the replacement it worked
fine. However, like I said, I am not sure what that error means SDB FIS.
On Mon, 18 Feb 2008, 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)
> 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: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)
> 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 0x3ff 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
>
> I've no idea what to make of these errors. As far as I can work out,
> the HD's themselves are fine They are all less than 2 months old.
>
> The box is CentOS 5.1. Linux space.homenet.com 2.6.18-53.1.13.el5 #1
> SMP Tue Feb 12 13:02:30 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
>
> Any suggestions on what I can do to stop this issue?
>
> Steve.
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.20.7/1284 - Release Date:
> 17/02/2008 14:39
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: HDD errors in dmesg, but don't know why...
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
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2008-02-18 20:18 UTC (permalink / raw)
To: Steve Fairbairn; +Cc: linux-raid
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-02-18 20:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).