I have 7 wd20ears drives in my system.  When I set it up I did not know about the need to jumper pins 7 and 8.  Discovered the need to do this reading the forum.

 

So I decided to change each drive one at a time as per instructions in the wiki.  I started with the parity drive.  Once setting the jumper the system displayed lots of io errors when booting.  I went ahead and built parity anyway which seemed to go OK.  However i still get all these errors when booting.  Any ideas about what this all means.

 

Here's a sample of the errors and full syslog attached.  thanks for any suggestions on how to fix this.

 

Nov 4 08:02:37 Tower kernel: i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000008

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ FPDMA QUEUED

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 60/08:08:a8:88:e0/00:00:e8:00:00/40 tag 1 ncq 4096 in

Nov 4 08:02:37 Tower kernel: res 41/01:00:af:88:e0/40:00:e8:00:00/40 Emask 0x401 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000008

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ FPDMA QUEUED

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in

Nov 4 08:02:37 Tower kernel: res 41/01:00:af:88:e0/40:00:e8:00:00/40 Emask 0x401 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000008

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ FPDMA QUEUED

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in

Nov 4 08:02:37 Tower kernel: res 41/01:00:af:88:e0/40:00:e8:00:00/40 Emask 0x401 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: NCQ disabled due to excessive errors

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000008

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ FPDMA QUEUED

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in

Nov 4 08:02:37 Tower kernel: res 41/01:00:af:88:e0/40:00:e8:00:00/40 Emask 0x401 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Unhandled sense code

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor]

Nov 4 08:02:37 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 4 08:02:37 Tower kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 4 08:02:37 Tower kernel: e8 e0 88 af

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] ASC=0x13 ASCQ=0x0

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00

Nov 4 08:02:37 Tower kernel: end_request: I/O error, dev sdf, sector 3907029167

Nov 4 08:02:37 Tower kernel: Buffer I/O error on device sdf, logical block 488378645

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

Nov 4 08:02:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Nov 4 08:02:37 Tower kernel: ata12.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in

Nov 4 08:02:37 Tower kernel: res 51/01:00:af:88:e0/40:00:e8:00:00/e0 Emask 0x1 (device error)

Nov 4 08:02:37 Tower kernel: ata12.00: status: { DRDY ERR }

Nov 4 08:02:37 Tower kernel: ata12.00: configured for UDMA/133

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Unhandled sense code

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor]

Nov 4 08:02:37 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 4 08:02:37 Tower kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 4 08:02:37 Tower kernel: e8 e0 88 af

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] ASC=0x13 ASCQ=0x0

Nov 4 08:02:37 Tower kernel: sd 12:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00

Nov 4 08:02:37 Tower kernel: end_request: I/O error, dev sdf, sector 3907029167

Nov 4 08:02:37 Tower kernel: Buffer I/O error on device sdf, logical block 488378645

Nov 4 08:02:37 Tower kernel: ata12: EH complete

Nov 4 08:02:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 4 08:02:37 Tower kernel: ata12.00: irq_stat 0x40000001

syslog-2010-11-04.txt

I received the same type of error as you when I jumpered my parity drive. I ran the preclear with the jumper off then precleared with the jumper installed. It fixed all errors I had. It took almost 2 days to do this one drive, but at least it fix my issues.

I am reluctant to do a preclear as it will take so long and the drive is obviously good.  I am running a parity check after rebuilding parity and noticed when it hit the sectors with the io errors things stopped for a minute and then carried on.  No parity errors reported.

 

I am inclined to go ahead and jumper another drive after the parity check finishes (if no errors) and rebuild the data and then repeat for the other drives until all are done.  Then to do a preclear on the parity drive and rebuild it again.

 

I am worried that the io errors will appear on the data drives when I jumper them though.

 

Any thoughts?