From AnalogJ's Repo: [BUG] Can't dismiss non-critical scrutiny warning for UltraDMA CRC Error Count #553

[zwimer]

In the non-fork'd version, one issue was that you couldn't dismiss warnings for UltraDMA CRC Errors. These errors often occur due to loose cables. They are valid errors, however, after fixing the loose cable, for example, the HDD retains the error count, as it is a cumulative counter. As a result, even if the underlying issue is fixed, Scrutiny will continue to detect that the number of UltraDMA errors is greater than the allowable threshold and consequently make the drive as failing tests. It'd be nice to be able to manually adjust the threshold or only warn if this number changes, for example.

Has this fork addressed this issue? If not I can copy the issue to this repo and link the original.

Source:
AnalogJ#553 (comment)

[zwimer]

This issue might be being addressed by this PR in the base repo: https://github.com/AnalogJ/scrutiny/pull/835/changes#diff-7478caef4620caab3e911c77c1e21ee3097b71e16b7143ad99be0da6f0555677R63

See the new discussion here: AnalogJ#920

[Starosdev]

@zwimer This has been addressed in PR #233, now merged to master.

Scrutiny will now compare attribute 199's raw value against the previous submission -- if the count hasn't increased, the warning is automatically suppressed. Additionally, there's a new inline menu on the device detail page where you can manually "Ignore attribute" or "Force passed" for any attribute.

Could you please test with the latest build and let us know if it resolves the issue on your end? Thanks for reporting this.