Anyone know what this might be?  It appears that it worked it out and is up and running. I did not have any symptoms in the gui, I was just looking in the logs for the spindown command being issues, and saw this:

 

 

 

 

 

Jan 22 20:53:34 NAS1 kernel: ata5.00: exception Emask 0x10 SAct 0x30000 SErr 0x400000 action 0x6 frozen

Jan 22 20:53:34 NAS1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Jan 22 20:53:34 NAS1 kernel: ata5: SError: { Handshk }

Jan 22 20:53:34 NAS1 kernel: ata5.00: failed command: WRITE FPDMA QUEUED

Jan 22 20:53:34 NAS1 kernel: ata5.00: cmd 61/08:80:00:4d:30/00:00:03:00:00/40 tag 16 ncq 4096 out

Jan 22 20:53:34 NAS1 kernel:        res 40/00:88:60:bc:34/00:00:03:00:00/40 Emask 0x10 (ATA bus error)

Jan 22 20:53:34 NAS1 kernel: ata5.00: status: { DRDY }

Jan 22 20:53:34 NAS1 kernel: ata5.00: failed command: WRITE FPDMA QUEUED

Jan 22 20:53:34 NAS1 kernel: ata5.00: cmd 61/08:88:60:bc:34/00:00:03:00:00/40 tag 17 ncq 4096 out

Jan 22 20:53:34 NAS1 kernel:        res 40/00:88:60:bc:34/00:00:03:00:00/40 Emask 0x10 (ATA bus error)

Jan 22 20:53:34 NAS1 kernel: ata5.00: status: { DRDY }

Jan 22 20:53:34 NAS1 kernel: ata5: hard resetting link

Jan 22 20:53:34 NAS1 kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Jan 22 20:53:34 NAS1 kernel: ata5.00: configured for UDMA/133

Jan 22 20:53:34 NAS1 kernel: ata5: EH complete

 

 

Try reseating your drives in the hotswap bays.  Usually those errors are cabling.

Try reseating your drives in the hotswap bays.  Usually those errors are cabling.

 

 

Ok, thanks... I'll give that a try before getting too worked up about it :-)