Hey guys... after 4 years of service, I started seeing this in my log. Is my drive going bad? Anyone have ideas? Thanks! Snippet below, full log attached.

 

Jan 27 23:06:28 flock kernel: Descriptor sense data with sense descriptors (in hex):

Jan 27 23:06:28 flock kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Jan 27 23:06:28 flock kernel:        00 68 42 10

Jan 27 23:06:28 flock kernel: sd 5:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 (Drive related)

Jan 27 23:06:28 flock kernel: sd 5:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 68 41 a8 00 00 80 00 (Drive related)

Jan 27 23:06:28 flock kernel: end_request: I/O error, dev sdd, sector 6832656 (Errors)

Jan 27 23:06:28 flock kernel: ata4: EH complete (Drive related)

Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors)

Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832592/3, count: 1 (Errors)

Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors)

Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832600/3, count: 1 (Errors)

Jan 27 23:06:28 flock kernel: md: disk3 read error (Errors)

Jan 27 23:06:28 flock kernel: handle_stripe read error: 6832608/3, count: 1 (Errors)

Jan 27 23:07:22 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 27 23:07:22 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related)

Jan 27 23:07:22 flock kernel: ata4.00: failed command: READ DMA (Minor Issues)

Jan 27 23:07:22 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related)

Jan 27 23:07:22 flock kernel:          res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 27 23:07:22 flock kernel: ata4.00: status: { DRDY ERR } (Drive related)

Jan 27 23:07:22 flock kernel: ata4.00: error: { UNC } (Errors)

Jan 27 23:07:22 flock kernel: ata4.00: configured for UDMA/133 (Drive related)

Jan 27 23:07:22 flock kernel: ata4: EH complete (Drive related)

Jan 27 23:07:25 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 27 23:07:25 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related)

Jan 27 23:07:25 flock kernel: ata4.00: failed command: READ DMA (Minor Issues)

Jan 27 23:07:25 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related)

Jan 27 23:07:25 flock kernel:          res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors)

Jan 27 23:07:25 flock kernel: ata4.00: status: { DRDY ERR } (Drive related)

Jan 27 23:07:25 flock kernel: ata4.00: error: { UNC } (Errors)

Jan 27 23:07:25 flock kernel: ata4.00: configured for UDMA/133 (Drive related)

Jan 27 23:07:25 flock kernel: ata4: EH complete (Drive related)

Jan 27 23:07:27 flock kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Jan 27 23:07:27 flock kernel: ata4.00: irq_stat 0x40000001 (Drive related)

Jan 27 23:07:27 flock kernel: ata4.00: failed command: READ DMA (Minor Issues)

Jan 27 23:07:27 flock kernel: ata4.00: cmd c8/00:80:b8:3f:68/00:00:00:00:00/e0 tag 0 dma 65536 in (Drive related)

Jan 27 23:07:27 flock kernel:          res 51/40:1f:10:40:68/00:00:00:00:00/e0 Emask 0x9 (media error) (Errors)

syslog.txt

Drive dying or Power Supply would be my guess.  Could also be motherboard/memory, sata cables.

 

The gurus on here will want you to post a full syslog (attachment).

 

I would take out the "sdd" drive and run some tests on it; preclear 1-2x and view the smart reports.

 

Thanks for the feedback. My guess is not the memory or motherboard since the errors are only occurring on one drive. I can swap out the SATA cable and switch the power connector to a free one. Power supply is pretty new too.