:'(  I just copied about 22GB of media to disk 5 of my array and the main page is showing 3 errors.  The problems seem to be in the following part of the syslog:

 

Nov 15 01:13:02 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:02 unRAID kernel: ata2.00: irq_stat 0x00020002, device error via D2H FIS

Nov 15 01:13:02 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:02 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:02 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:02 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:02 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:03 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:03 unRAID kernel: ata2: EH complete

Nov 15 01:13:07 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:07 unRAID kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS

Nov 15 01:13:07 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:07 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:07 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:07 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:07 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:07 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:07 unRAID kernel: ata2: EH complete

Nov 15 01:13:10 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:10 unRAID kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS

Nov 15 01:13:10 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:10 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:10 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:10 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:10 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:10 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:10 unRAID kernel: ata2: EH complete

Nov 15 01:13:13 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:13 unRAID kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS

Nov 15 01:13:13 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:13 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:13 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:13 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:13 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:13 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:13 unRAID kernel: ata2: EH complete

Nov 15 01:13:16 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:16 unRAID kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS

Nov 15 01:13:16 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:16 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:16 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:16 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:16 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:16 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:16 unRAID kernel: ata2: EH complete

Nov 15 01:13:19 unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 15 01:13:19 unRAID kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS

Nov 15 01:13:19 unRAID kernel: ata2.00: failed command: READ DMA

Nov 15 01:13:19 unRAID kernel: ata2.00: cmd c8/00:58:a7:7a:00/00:00:00:00:00/e0 tag 0 dma 45056 in

Nov 15 01:13:19 unRAID kernel: res 51/40:00:ea:7a:00/00:00:00:00:00/00 Emask 0x9 (media error)

Nov 15 01:13:19 unRAID kernel: ata2.00: status: { DRDY ERR }

Nov 15 01:13:19 unRAID kernel: ata2.00: error: { UNC }

Nov 15 01:13:19 unRAID kernel: ata2.00: configured for UDMA/100

Nov 15 01:13:19 unRAID kernel: sd 2:0:0:0: [sdc] Unhandled sense code

Nov 15 01:13:19 unRAID kernel: sd 2:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08

Nov 15 01:13:19 unRAID kernel: sd 2:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor]

Nov 15 01:13:19 unRAID kernel: Descriptor sense data with sense descriptors (in hex):

Nov 15 01:13:19 unRAID kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 15 01:13:19 unRAID kernel: 00 00 7a ea

Nov 15 01:13:19 unRAID kernel: sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x4

Nov 15 01:13:19 unRAID kernel: sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 00 7a a7 00 00 58 00

Nov 15 01:13:19 unRAID kernel: end_request: I/O error, dev sdc, sector 31466

Nov 15 01:13:19 unRAID kernel: ata2: EH complete

Nov 15 01:13:19 unRAID kernel: md: disk5 read error

Nov 15 01:13:19 unRAID kernel: handle_stripe read error: 31400/5, count: 1

Nov 15 01:13:19 unRAID kernel: md: disk5 read error

Nov 15 01:13:19 unRAID kernel: handle_stripe read error: 31408/5, count: 1

Nov 15 01:13:19 unRAID kernel: md: disk5 read error

Nov 15 01:13:19 unRAID kernel: handle_stripe read error: 31416/5, count: 1

 

I've attached the full syslog, a S.M.A.R.T. report on disk 5 and a filtered syslog on disk 5 (thanks to Joe's excellent unMENU)

 

Can someone translate for me?  Is this just a possible loose cable (I hope)? What should I do next?

 

THANKS!

Filtered_syslog_D5-2010-11-15.txt

syslog-2010-11-15.txt

2010_11_15_Disk_5.txt

According to the "smart" report those 3 "read" errors all were in 1 un-readable sector on disk5. 

When a "read" error occurs you'll usually see it as a "media error" in the syslog.  The unRAID software uses parity and the pther data disks to re-construct the un-readable sector to the program reading it gets the correct data.  It also then writes that same re-constructed contents back to the disk with the un-readable sector.  This allow the SMART firmware on the disk to re-allocate the sector since it now knows what the contents should be. (Initially, when unable to read it, it is marked as pending re-allocation waiting for a subsequent write to it)

 

All this has already occurred. 

 

Most modern disks have several thousand spare sectors to use for re-allocation.  You've used 1 of them.

 

Keep an eye on the disk over the next months/years.  If you see a steady increase in the number of re-allocated sectors you'll want to RMA the disk.  It might stabilize and not increase at all.  I've got one disk in my array that has had the same 100 re-allocated sectors from the first time I ran a smart report on it.  The number has never increased so I have no reason to replace it.

 

Joe L.

Thanks Joe!