mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 05:35:59 +03:00
[GH-ISSUE #348] Failed to load attribute DB #831
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#831
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @IngmarStein on GitHub (Aug 25, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/348
Originally assigned to: @007revad on GitHub.
I see a lot of messages like the following in
/var/log/messages:Is this just an expected outcome after using this tool? It seems harmless - I don't see any broken functionality in Storage Manager, fwiw.
@007revad commented on GitHub (Aug 26, 2024):
I'd like to know if people get those spammy log entries before running syno_hdd_db.
For each NVMe drive I'm getting multiple of these at 18:43 each day:
And multiple of these at midnight each day:
They seem to be harmless, but add a spam to the log.
I wonder if it's because the drives are not in the smartmontools db files: