Logged in to shutdown my server a month ago, just before departing on vacation, and was greeted with errors on the parity drive.  Didn't have time to look into it then, just getting home and trying to get things up and running.  When I booted the server tonight, Unraid sees the drive as a new parity drive and wants to sync parity.  Before doing anything I'm hoping to get some help/guidance.  I'm running Unraid 4.7.  The syslog from when I shut down the system is attached (2-25 version), the errors actually show up on 2/13, along with the syslog from tonight and the SMART report from tonight (which shows nothing unusual that I can see).

 

No changes have been made to the system in months.  The text of the error is:

 

Feb 13 03:41:01 Tower kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 13 03:41:01 Tower kernel: ata9.00: irq_stat 0x40000001
Feb 13 03:41:01 Tower kernel: ata9.00: failed command: READ DMA
Feb 13 03:41:01 Tower kernel: ata9.00: cmd c8/00:10:8f:1c:00/00:00:00:00:00/e0 tag 0 dma 8192 in
Feb 13 03:41:01 Tower kernel:          res 51/04:10:8f:1c:00/00:00:00:00:00/e0 Emask 0x1 (device error)
Feb 13 03:41:01 Tower kernel: ata9.00: status: { DRDY ERR }
Feb 13 03:41:01 Tower kernel: ata9.00: error: { ABRT }
Feb 13 03:41:02 Tower kernel: ata9.00: configured for UDMA/133
Feb 13 03:41:02 Tower kernel: ata9: EH complete

 

Any assistance/ideas would be greatly appreciated - please let me know if there's any additional information I can provide.  Thanks in advance.

logs.zip

I'm not an expert at these things so I'll let someone else chime in on the details, but I'd believe it would be beneficial to run a smart test on the drive in question and post those results as well.

Thanks for the response Influencer.  The zip file I posted includes a smart report from the drive that was run tonight.  From what I can see, it doesn't include anything unusual (no reallocated sectors, etc.). 

 

My fault, I looked down too far and read the "current testing" instead of the "test results" section.

The SMART report looks ok. Run a long SMART test.

Thanks dgaschk.  The results of the long test are attached.  The key change is that the Current Pending Sector count increased to 1. 

 

Any thoughts?  Thanks again.

smart.txt

The pending sector needs to be resolved. Rebuild the drive: Start the array with the drive unassigned. Then assign the drive and restart the array. The drive will rebuild.

Just to confirm, right now Unraid is seeing the drive as a new parity drive, with the option to start the array and run a parity sync - is that the correct step to take?

Yes That will resolve the pending sector.

Ran the parity sync without error, then another extended SMART test, which now shows no reallocated or pending sectors.  Not sure what went on, but everything seems to be good (for now anyways).  Thanks again for the help.