[GH-ISSUE #348] Failed to load attribute DB #831

Closed
opened 2026-03-12 17:21:03 +03:00 by kerem · 1 comment
Owner

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:

DS923 synostgd-disk[9493]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1

Is this just an expected outcome after using this tool? It seems harmless - I don't see any broken functionality in Storage Manager, fwiw.

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`: ``` DS923 synostgd-disk[9493]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1 ``` Is this just an expected outcome after using this tool? It seems harmless - I don't see any broken functionality in Storage Manager, fwiw.
kerem 2026-03-12 17:21:03 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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:

DISKSTATION synowebapi_SYNO.Storage.CGI.Smart_1_get_health_info[21402]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1

And multiple of these at midnight each day:

DISKSTATION syno_disk_data_collector[19829]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1

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:

/var/lib/smartmontools/drivedb.db
/var/lib/smartmontools/synodrivedb.db
<!-- gh-comment-id:2309572608 --> @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: ``` DISKSTATION synowebapi_SYNO.Storage.CGI.Smart_1_get_health_info[21402]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1 ``` And multiple of these at midnight each day: ``` DISKSTATION syno_disk_data_collector[19829]: smartctl/smartctl_nvme_smart_info_get.c:232 Failed to load attribute DB of disk /dev/nvme0n1 ``` 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: ``` /var/lib/smartmontools/drivedb.db /var/lib/smartmontools/synodrivedb.db ````
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#831
No description provided.