-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in HA log regarding parity history parsing - not enough fields #38
Comments
Thanks for the info. Good to know about the parity logs that messing around and the formatting changed over the years. I have only recently started using a parity disk again to help me work on the integrations parity sensor so my logs are limited. |
Hi updated the integration manually with the latest code and I still get errors. My errors :
|
Both parity check history errors disappear, but now I have another error:
As I look into debug log, here is detail:
And here is my parity check history:
|
Thanks for the logs. Helps a lot to try and fine tune it Looking at the logs, I can see several formats that need to be handled: Legacy format (4-5 fields): 2017 Jan 17 09:38:32|20311|147.7 MB/s|0 Newer format with error count (5 fields): 2017 Feb 14 09:34:21|20060|149.6 MB/s|0|0 Modern format with raw bytes/sec and additional metadata: 2022 Jun 21 05:26:46|32214|124194045|0|5|check P Q|3907018532 Latest format with full details: 2023 May 28 08:51:22|31875|125.5 MB/s|0|0|check P Q|3907018532|31875|1|Scheduled Correcting Parity-Check |
I made changes based on the logs you provided.
|
Nice work @domalab The only message I have in the logs are the warning about skipping the invalid date :
Thank you |
Thanks for that @domalab now I don't have any error regarding parity check history, so from my point of view it looks fixed 😊 |
Describe the bug
In HA log i can see this error:
Probably it's caused by older records which have lesser columns, in Unraid GUI I can see that:
Logs until 2022-06-05 have only these columns filled
Logs until 2023-05-21 have only these columns filled:
Rest of logs until today have columns filled:
Last part is probably caused by plugin which adds incremental run for parity check.
So by the error problem probably should be, that older logs don't have column Size.
This behavior start from update of integration to version 2024.12.28.
Expected behavior
Screenshots
Unraid (please complete the following information):
Home Assistant (please complete the following information):
Home Assistant installation type (please complete the following information):
Priority of Request
Additional context
The text was updated successfully, but these errors were encountered: