Opened 2 days ago
Last modified 2 days ago
#1906 new defect
smard fails to start if non-removable drive is connected by usb without -d removable
| Reported by: | ehsm2278 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | smartd | Version: | 7.3 |
| Keywords: | usb | Cc: |
Description
I just discovered that my smartd has been failing to start just because I moved an internal SATA harddrive to an external USB-attached adapter, complaining:
Unable to register device /dev/disk/by-id/ata-ST16000NM000J-2TW103_Z92CWXJ (no Directive -d removable). Exiting.
It appears that smartd now *requires* "-d removable" for USB attached devices, even if I don't want them to be treated as removable??
This drive may technically be removable (but so are SATA, SCSI, and other devices!), but as far as I am concerned it is a permanently installed drive, and I WANT to receive warning emails and other notifications if this drive isn't accessible, contrary to the behavior of being forced to add "-d removable"!
Why was this made a mandatory config option regardless of the desires of the operator?
Change History (2)
comment:1 by , 2 days ago
comment:2 by , 2 days ago
| Keywords: | removable required removed |
|---|---|
| Milestone: | → undecided |
Unable to register device /dev/disk/by-id/ata-ST16000NM000J-2TW103_Z92CWXJ (no Directive -d removable). Exiting.
This is as expected because if a drive is reconnected via USB, it reappears as some /dev/disk/by-id/usb-... (or possibly uas) instead.
... I WANT to receive warning emails and other notification...
Put the correct path name into smartd.conf and make sure to add -d sat if the USB Id is not in the drivedb.
Why was this made a mandatory config option regardless of the desires of the operator?
Because this was a reasonable design decision done by another volunteer in the year 2003 :-)
Apologies, I just realized that the device node changed from ata- to usb-, so the config for the device path has to change too.