ATA error - anything to be worried about?

[Fraoch]

Got this in my e-mail this morning from my FreeNAS:

Minas-Tirith.local kernel log messages:
> (ada3:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 70 fa cb 40 10 00 00 00 00 00
> (ada3:ahcich3:0:0:0): CAM status: ATA Status Error
> (ada3:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
> (ada3:ahcich3:0:0:0): RES: 41 10 70 fa cb 40 10 00 00 00 00
> (ada3:ahcich3:0:0:0): Retrying command

Never seen that before. And it wasn't repeated in the log.

Everything seems fine though. No errors, all files readable, nothing out of the ordinary except two things, probably unrelated:

- getting the "Disk" graphs up in the "Reporting" tab takes abnormally long. Only a few seconds, but still a noticeable delay
- ARC Hit Ratio abnormally low, 53.3%. Usually I'm in the high 90s. ARC size is very small, it's like the ARC hasn't "warmed up" yet but uptime is 9 days

Nothing to be concerned about? My drives are getting old, 19 462 power on hours on the oldest ones, but they still pass all S.M.A.R.T. tests (short tests daily, extended tests weekly).

FreeNAS-9.10.2 (a476f16)

 

[Ericloewe]

What does SMART say, exactly?

 

[Fraoch]

For some reason that error is not logged?

Code:

# smartctl -l error /dev/ada3
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
No Errors Logged

The smartmontools documentation indicates this though:

Error log data structures shall not include errors attributed to the receipt of faulty commands." The definitions of these terms are:
<snip>
IDNF (ID Not Found): user-accessible address could not be found. For READ LOG type commands, IDNF can also indicate that a device data log structure checksum was incorrect.

As for the self tests:

Code:

# smartctl -l selftest /dev/ada3
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description  Status  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline  Completed without error  00%  19463  -
# 2  Short offline  Completed without error  00%  19439  -
# 3  Short offline  Completed without error  00%  19415  -
# 4  Short offline  Completed without error  00%  19391  -
# 5  Short offline  Completed without error  00%  19367  -
# 6  Extended offline  Completed without error  00%  19348  -
# 7  Short offline  Completed without error  00%  19319  -
# 8  Short offline  Completed without error  00%  19295  -
# 9  Short offline  Completed without error  00%  19271  -
#10  Short offline  Completed without error  00%  19246  -
#11  Short offline  Completed without error  00%  19222  -
#12  Short offline  Completed without error  00%  19198  -
#13  Extended offline  Completed without error  00%  19179  -
#14  Short offline  Completed without error  00%  19151  -
#15  Short offline  Completed without error  00%  19127  -
#16  Short offline  Completed without error  00%  19103  -
#17  Short offline  Completed without error  00%  19079  -
#18  Short offline  Completed without error  00%  19055  -
#19  Short offline  Completed without error  00%  19031  -
#20  Extended offline  Completed without error  00%  19012  -
#21  Short offline  Completed without error  00%  18983  -

 

[BigDave]

Nothing to be concerned about? My drives are getting old, 19 462 power on hours on the oldest ones, but they still pass all S.M.A.R.T. tests (short tests daily, extended tests weekly).

Almost 5,000 hours ago I had a very similar occurrence with one of my drives.
I decided to begin replacement of my 3TB drives for 4TB models, since replacing
the drive with the error, the issue had disappeared. I am now half way through
as I have three more drives left with a bit over 19,000 hrs. on them.

 

[Fraoch]

Thanks!

I have an unused replacement drive ready for just such an event. If I see the error again I'll shut down and re-seat cables. If I see it again after that I'll replace the drive.