My unraid install has been working fine for months, but recently the cache drive began throwing an error. 

 

The logs on my cache drive show:

Dec 28 15:23:25 Gringotts kernel: ata2.00: exception Emask 0x0 SAct 0x1ff00ff SErr 0x0 action 0x0
Dec 28 15:23:25 Gringotts kernel: ata2.00: irq_stat 0x40000008
Dec 28 15:23:25 Gringotts kernel: ata2.00: failed command: READ FPDMA QUEUED
Dec 28 15:23:25 Gringotts kernel: ata2.00: cmd 60/20:08:20:4a:04/00:00:00:00:00/40 tag 1 ncq dma 16384 in
Dec 28 15:23:25 Gringotts kernel: ata2.00: status: { DRDY ERR }
Dec 28 15:23:25 Gringotts kernel: ata2.00: error: { UNC }

 

I have already tried to change the sata cable and port on my motherboard in hopes that the cable might just be a dud. I also ran a smart test on the ssd and no errors were found on the drive. In searching the error online I can't find reference to the 'action 0x0' code, but a lot of 'action 0x6' so I'm not sure where to go from here. 

 

For some background, the drive is about 3 months old (ADATA SU635 480GB), and is connected via sata directly to my Asus P8Z68-V LX motherboard in the 6GB/s port. There is also a Samsung 850 evo connected as an unassigned drive to the other 6GB/s port. The samsung drive has been working fine to hold my appdata and hasnt given any errors. There are 3 other HDDs connected to internal sata ports as well as 4 drives connected to a DELL LSI SAS 9207-8i. All other drives seem to be performing fine with no smart errors reported or any errors in the logs. Attached are the diagnostic logs.

 

Please please please help me figure this out as I have been stuck without cache access for over a week now trying to figure this out. Thank you.

gringotts-diagnostics-20201227-1521.zip

Run an extended SMART test on it

Already ran an extended test and it completed without errors. The only errors that list in smart are the READ FPDMA QUEUED errors that look like theyre coming from whatever that Emask error is causing.

gringotts-smart-20201228-1807.zip