Problem/Justification
This error is often attributed to faulty SATA cables or ports, while the assignment of the logged device name (e.g. /dev/sda) is not guaranteed to be consistent. If someone tries swapping cables or drives around to isolate the problem component this makes logging and tracking the cause over time difficult and confusing.
Impact
It would make troubleshooting of sporadic errors easier, can’t think of any inconveniences an updated message would introduce.
User Story
As an user troubleshooting hardware problems, I would like persistent port and drive identification included in the “ATA error count increased” alert message. (e.g. /dev/disk/by-id/ and /dev/disk/by-path/.)
I’m not clear on exactly what you are asking for. Can you provide an example?
Also, have you looked at Multi-Report? It tracks UDMA_CRC_Errors and a lot more, specifically to aid in troubleshooting. This may be what you are asking for.
Hi joeschmuck,
I’m referring to this alert message:
Message reads “Device: /dev/sda [SAT], ATA error count increased from 5 to 6.”
So the drive assigned /sda at that moment has a problem. Several things can change the order in which the SATA drives are given these identifiers so unless you take extra care to check which disk and port are involved in a timely manner that information gets lost.
Something like “Device: /dev/sda [SAT] - ID: ata-WDC_WD123ABCD-1234567_ABCDEFGH - Path: /dev/disk/by-path/pci-0000:01:00.1-ata-6, ATA error count increased from 5 to 6.”
would be more actionable.
I’ll look into Multi Report, thanks.
Thanks for the clarification.
Multi-Report will help you out, I “track” by serial number, not solely the device ID. I do agree that it would be nice if TrueNAS listed the drive serial number as well, I can’t imagine it would be difficult at all.
1 Like
I am out of votes unfortunately, but I agree that the message leaves out vital information that makes corrective action more difficult if you happen to not catch it at the right time.
Don’t forget to vote for your own suggestion.
