David Greaves wrote: >I've upgraded to 2.6.16 and applied your verbosity patches. > >I've persuaded my array to re-assemble and during the resync I got these >messages > >dmesg: >ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI >SK/ASC/ASCQ 0xb/00/00 >ata1: status=0x51 { DriveReady SeekComplete Error } >ata1: error=0x04 { DriveStatusError } >...(18mins later) >ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51 >ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI >SK/ASC/ASCQ 0x3/11/04 >ata1: status=0x51 { DriveReady SeekComplete Error } > >smartd is not running >This did not cause the raid subsystem to boot the disk (thank goodness!) > > Just providing a little more followon information... I have had a further 52 of these messages over the last day. No obvious cause. Mar 22 13:14:55 haze kernel: ata2: no sense translation for op=0x28 cmd=0x25 status: 0x51 Mar 22 13:14:55 haze kernel: ata2: status=0x51 { DriveReady SeekComplete Error } Most recently this happened: Mar 22 13:47:09 haze kernel: ata2: no sense translation for op=0x28 cmd=0x25 status: 0x51 Mar 22 13:47:09 haze kernel: ata2: status=0x51 { DriveReady SeekComplete Error } Mar 22 13:47:09 haze kernel: sd 1:0:0:0: SCSI error: return code = 0x8000002 Mar 22 13:47:09 haze kernel: sdb: Current: sense key: Medium Error Mar 22 13:47:09 haze kernel: Additional sense: Unrecovered read error - auto reallocate failed Mar 22 13:47:09 haze kernel: end_request: I/O error, dev sdb, sector 396518289 with dmesg piping up with: raid1: sdb2: rescheduling sector 5801424 raid1: sdd2: redirecting sector 5801424 to another mirror no drives were kicked from the array. David -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Tejun Heo <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Jeff Garzik <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Justin Piszcz <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: Mark Lord <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- Re: LibPATA code issues / 2.6.15.4
- From: David Greaves <[email protected]>
- LibPATA code issues / 2.6.15.4
- Prev by Date: [patch 17/24] s390: tape retry flooding by deferred CC in interrupt.
- Next by Date: [patch 20/24] s390: 3590 tape driver
- Previous by thread: Re: LibPATA code issues / 2.6.15.4
- Next by thread: Re: LibPATA code issues / 2.6.15.4
- Index(es):