Hi guys,

 

Trying to troubleshoot something here and im a bit over my head trying to interpret the linux logs. I assume this is a bad drive, cable, or port, but I would greatly appreciate your input before I start juggling stuff around inside the case.

 

The below errors are looping in my syslog. The array operates, and there are no red balls, just one drive flashes grey / green (not sure what this means)

 

 

Apr 10 17:29:04 UNRAID kernel: ata2.01: failed command: READ DMA EXT

Apr 10 17:29:04 UNRAID kernel: ata2.01: cmd 25/00:00:28:97:8b/00:04:b1:00:00/f0 tag 0 dma 524288 in

Apr 10 17:29:04 UNRAID kernel:          res 51/84:10:18:98:8b/84:03:b1:00:00/f0 Emask 0x30 (host bus error)

Apr 10 17:29:04 UNRAID kernel: ata2.01: status: { DRDY ERR }

Apr 10 17:29:04 UNRAID kernel: ata2.01: error: { ICRC ABRT }

Apr 10 17:29:04 UNRAID kernel: ata2: soft resetting link

Apr 10 17:29:04 UNRAID kernel: ata2.00: configured for UDMA/133

Apr 10 17:29:04 UNRAID kernel: ata2.01: configured for UDMA/33

Apr 10 17:29:04 UNRAID kernel: ata2: EH complete

Apr 10 17:29:05 UNRAID kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

Apr 10 17:29:05 UNRAID kernel: ata2.01: BMDMA stat 0x66

Apr 10 17:29:05 UNRAID kernel: ata2.01: failed command: READ DMA EXT

Apr 10 17:29:05 UNRAID kernel: ata2.01: cmd 25/00:00:28:cf:8b/00:04:b1:00:00/f0 tag 0 dma 524288 in

Apr 10 17:29:05 UNRAID kernel:          res 51/84:10:18:d3:8b/84:00:b1:00:00/f0 Emask 0x30 (host bus error)

Apr 10 17:29:05 UNRAID kernel: ata2.01: status: { DRDY ERR }

Apr 10 17:29:05 UNRAID kernel: ata2.01: error: { ICRC ABRT }

Apr 10 17:29:05 UNRAID kernel: ata2: soft resetting link

Apr 10 17:29:05 UNRAID kernel: ata2.00: configured for UDMA/133

Apr 10 17:29:05 UNRAID kernel: ata2.01: configured for UDMA/33

Apr 10 17:29:05 UNRAID kernel: ata2: EH complete

 

And so on, and so forth. How can i easily identify which drive is playing up? "ata2.01", I assume means controller 2 port 1?

 

Thanks in advance for any inputs.

 

Paul

You'd be better off posting the full syslog, gives a better idea of the overall problem.

Hi guys,

 

Trying to troubleshoot something here and im a bit over my head trying to interpret the linux logs. I assume this is a bad drive, cable, or port, but I would greatly appreciate your input before I start juggling stuff around inside the case.

 

The below errors are looping in my syslog. The array operates, and there are no red balls, just one drive flashes grey / green (not sure what this means)

 

 

Apr 10 17:29:04 UNRAID kernel: ata2.01: failed command: READ DMA EXT

Apr 10 17:29:04 UNRAID kernel: ata2.01: cmd 25/00:00:28:97:8b/00:04:b1:00:00/f0 tag 0 dma 524288 in

Apr 10 17:29:04 UNRAID kernel:          res 51/84:10:18:98:8b/84:03:b1:00:00/f0 Emask 0x30 (host bus error)

Apr 10 17:29:04 UNRAID kernel: ata2.01: status: { DRDY ERR }

Apr 10 17:29:04 UNRAID kernel: ata2.01: error: { ICRC ABRT }

Apr 10 17:29:04 UNRAID kernel: ata2: soft resetting link

Apr 10 17:29:04 UNRAID kernel: ata2.00: configured for UDMA/133

Apr 10 17:29:04 UNRAID kernel: ata2.01: configured for UDMA/33

Apr 10 17:29:04 UNRAID kernel: ata2: EH complete

Apr 10 17:29:05 UNRAID kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

Apr 10 17:29:05 UNRAID kernel: ata2.01: BMDMA stat 0x66

Apr 10 17:29:05 UNRAID kernel: ata2.01: failed command: READ DMA EXT

Apr 10 17:29:05 UNRAID kernel: ata2.01: cmd 25/00:00:28:cf:8b/00:04:b1:00:00/f0 tag 0 dma 524288 in

Apr 10 17:29:05 UNRAID kernel:          res 51/84:10:18:d3:8b/84:00:b1:00:00/f0 Emask 0x30 (host bus error)

Apr 10 17:29:05 UNRAID kernel: ata2.01: status: { DRDY ERR }

Apr 10 17:29:05 UNRAID kernel: ata2.01: error: { ICRC ABRT }

Apr 10 17:29:05 UNRAID kernel: ata2: soft resetting link

Apr 10 17:29:05 UNRAID kernel: ata2.00: configured for UDMA/133

Apr 10 17:29:05 UNRAID kernel: ata2.01: configured for UDMA/33

Apr 10 17:29:05 UNRAID kernel: ata2: EH complete

 

And so on, and so forth. How can i easily identify which drive is playing up? "ata2.01", I assume means controller 2 port 1?

 

Thanks in advance for any inputs.

 

Paul

CRC errors are usually either a bad SATA cable, OR a cable picking up noise from an adjacent cable.  If you've neatly bundled up all the cables, you've caused it yourself.  Cut the tie-wraps and get some distance between the cables.