Can anyone translate what this means?

 

Mar  4 03:12:17 sun kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

Mar  4 03:12:17 sun kernel: ata12.00: failed command: READ DMA EXT (Minor Issues)

Mar  4 03:12:17 sun kernel: ata12.00: cmd 25/00:00:ff:de:ae/00:04:a3:00:00/e0 tag 0 dma 524288 in (Drive related)

Mar  4 03:12:17 sun kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)

Mar  4 03:12:17 sun kernel: ata12.00: status: { DRDY } (Drive related)

Mar  4 03:12:17 sun kernel: ata12: hard resetting link (Minor Issues)

Mar  4 03:12:17 sun kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)

Mar  4 03:12:17 sun kernel: ata12.00: configured for UDMA/133 (Drive related)

Mar  4 03:12:17 sun kernel: ata12.00: device reported invalid CHS sector 0 (Drive related)

Mar  4 03:12:17 sun kernel: ata12: EH complete (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: irq_stat 0x40000001 (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: failed command: READ DMA EXT (Minor Issues)

Mar  4 03:13:06 sun kernel: ata12.00: cmd 25/00:00:ff:e6:ae/00:04:a3:00:00/e0 tag 0 dma 524288 in (Drive related)

Mar  4 03:13:06 sun kernel:          res 51/40:1f:de:e9:ae/00:01:a3:00:00/e0 Emask 0x9 (media error) (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: status: { DRDY ERR } (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: error: { UNC } (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: configured for UDMA/133 (Drive related)

Mar  4 03:13:06 sun kernel: ata12: EH complete (Drive related)

(points to message right below yours) Me too. Just popped up this morning.

see http://lime-technology.com/forum/index.php?topic=18780.0 for things to try so far.

Can anyone translate what this means?

 

Mar  4 03:12:17 sun kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

Mar  4 03:12:17 sun kernel: ata12.00: failed command: READ DMA EXT (Minor Issues)

Mar  4 03:12:17 sun kernel: ata12.00: cmd 25/00:00:ff:de:ae/00:04:a3:00:00/e0 tag 0 dma 524288 in (Drive related)

Mar  4 03:12:17 sun kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)

Mar  4 03:12:17 sun kernel: ata12.00: status: { DRDY } (Drive related)

Mar  4 03:12:17 sun kernel: ata12: hard resetting link (Minor Issues)

Mar  4 03:12:17 sun kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)

Mar  4 03:12:17 sun kernel: ata12.00: configured for UDMA/133 (Drive related)

Mar  4 03:12:17 sun kernel: ata12.00: device reported invalid CHS sector 0 (Drive related)

Mar  4 03:12:17 sun kernel: ata12: EH complete (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: irq_stat 0x40000001 (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: failed command: READ DMA EXT (Minor Issues)

Mar  4 03:13:06 sun kernel: ata12.00: cmd 25/00:00:ff:e6:ae/00:04:a3:00:00/e0 tag 0 dma 524288 in (Drive related)

Mar  4 03:13:06 sun kernel:          res 51/40:1f:de:e9:ae/00:01:a3:00:00/e0 Emask 0x9 (media error) (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: status: { DRDY ERR } (Drive related)

Mar  4 03:13:06 sun kernel: ata12.00: error: { UNC } (Errors)

Mar  4 03:13:06 sun kernel: ata12.00: configured for UDMA/133 (Drive related)

Mar  4 03:13:06 sun kernel: ata12: EH complete (Drive related)

The first is where a command to the disk timed out.  I see it setting up a 3Gbps link.  Are your SATA cables up to it? Rated for 3.9Gbps?  Or, are they able to pick up induced noise from other cables nearby?  Did you perhaps bundle them? or worse, bundle them with a power cable?  In any case, these are not really harmful, as the OS just reset the link and re-tried.  About all that you might have noticed was a tiny delay in accessing your data.

 

The second is much easier.  It is a "media error"  of an UNC (un-Correctable) type.

In terms you might better understand, an UN-readable sector on the disk.  A SMART report on the drive will show it as a sector pending re-allocation, or, possible a sector already re-allocated if you've written to the sector since it was discovered as un-readable.

 

 

I left the cables UNbundled in the case. All power cables are as far away as they can get. The server has been running for months in my closet not being touched by anyone. Odd these type errors just come up.

 

As for the the media error, sounds like a hard drive issue or a hard drive going bad? How would I know which drive, I don't see a serial number or anything. I did notice, only one of my drives has pending. All the others do not. Maybe that is the drive the unRAID log is trying to tell me about.

 

 

 

Post SMART reports.