I’ve recently had a drive cause a UDMA CRC error, the counter is now at 1 from 0. So it has become CRIT as it should. It shows shows “UDMA CRC errors: 1 (during discovery: 0 CRIT)” I’ve dealt with the problem and wish to reset the status back to OK. I’ve read it compares the values against discovery hence the discovery bit in the return summary.
I’ve wait nearly 24 hours now and forced a Check_MK Discovery a few times but I can’t get it to go back to OK status.
Am I missing something here? the docs doesn’t seem how to force a rediscovery for the SMART data.
If anyone can shred some light that would be great.
Hi.
Yes, that is intentional (but ok, not really straight forward).
The smartctl counter doesn’t go back to 0 when there are no more new CRC errors. Instead, it stays at the last value.
By doing a forced re-inventory, you declare this value to be the new, accepted normal.
Yeah I know smartctl counter for those stats won’t reset but would be nice if there was a nice force re-inventory or something button for services that use the discovery metrics as the baseline, at the moment it wasn’t so obvious. Just my thoughts.
Hopefully someone else who is googling the issue will find this and it’ll help them
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
