System Environment:
OS: Proxmox VE 9.1.2
Hardware: Mix of SATA (Intel/WD) and SAS drives.
I am trying to configure smartd to monitor exactly 16 physical drives using /etc/smartd.conf. However, smartd consistently reports 29 or 30 devices. When running smartd -q showtests, the output shows every physical device twice: once with a clean path and once with a trailing comma.
Example Output:
/dev/disk/by-id/ata-INTEL_SSDSC2KB480G8_BTYF83150H7H480BGN
/dev/disk/by-id/ata-INTEL_SSDSC2KB480G8_BTYF83150H7H480BGN,
What I have already tried:
Manual Configuration: Listed all 16 drives explicitly using /dev/disk/by-id/ paths.
DEVICESCAN: Removed all instances of DEVICESCAN from the config file.
Environment Flags: Set smartd_opts="-q nodev0" in /etc/default/smartmontools to prevent auto-scanning.
Cache Clearing: Stopped the service, ran killall -9 smartd, and cleared /var/lib/smartmontools/* before restarting.
Sanitizing the File: Used sed to strip carriage returns (\r) and commas, and even used printf to rebuild the file from scratch to avoid hidden characters/encoding issues from the terminal.
Simplicity Test: Even with only 2 drives listed in smartd.conf, the daemon still reports 4 devices (the 2 drives + 2 "comma" versions).
Even with a perfectly clean, manual configuration file, smartd appears to be misparsing the end of each line as a comma or failing to ignore a "ghost" device list from another source. It seems to be appending a comma to every valid device path and attempting to monitor it as a second, unique (but non-existent) device.
Has anyone seen smartd inject commas into device paths on Proxmox? Is there a secondary configuration or a systemd override that might be forcing a "Configuration Merge" or causing this parsing error?
OS: Proxmox VE 9.1.2
Hardware: Mix of SATA (Intel/WD) and SAS drives.
I am trying to configure smartd to monitor exactly 16 physical drives using /etc/smartd.conf. However, smartd consistently reports 29 or 30 devices. When running smartd -q showtests, the output shows every physical device twice: once with a clean path and once with a trailing comma.
Example Output:
/dev/disk/by-id/ata-INTEL_SSDSC2KB480G8_BTYF83150H7H480BGN
/dev/disk/by-id/ata-INTEL_SSDSC2KB480G8_BTYF83150H7H480BGN,
What I have already tried:
Manual Configuration: Listed all 16 drives explicitly using /dev/disk/by-id/ paths.
DEVICESCAN: Removed all instances of DEVICESCAN from the config file.
Environment Flags: Set smartd_opts="-q nodev0" in /etc/default/smartmontools to prevent auto-scanning.
Cache Clearing: Stopped the service, ran killall -9 smartd, and cleared /var/lib/smartmontools/* before restarting.
Sanitizing the File: Used sed to strip carriage returns (\r) and commas, and even used printf to rebuild the file from scratch to avoid hidden characters/encoding issues from the terminal.
Simplicity Test: Even with only 2 drives listed in smartd.conf, the daemon still reports 4 devices (the 2 drives + 2 "comma" versions).
Even with a perfectly clean, manual configuration file, smartd appears to be misparsing the end of each line as a comma or failing to ignore a "ghost" device list from another source. It seems to be appending a comma to every valid device path and attempting to monitor it as a second, unique (but non-existent) device.
Has anyone seen smartd inject commas into device paths on Proxmox? Is there a secondary configuration or a systemd override that might be forcing a "Configuration Merge" or causing this parsing error?