Custom Query (1452 matches)

Forwarded from: ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894134

Hi.

It seems that smartd "double monitors" devices, when explicitly naming them via a symbolic link and using DEVICESCAN in the config file.

Consider e.g. the following typical use case: One wants to monitor all devices, but has special settings (e.g. different temperature ranges for one e.g. a SSD which runs at higher temps than an HDD): /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F -d auto -d removable -n standby,4 -a -W 0,50,60 -m root -M exec /usr/share/smartmontools/smartd-runner DEVICESCAN -d auto -d removable -n standby,4 -a -W 0,45,50 -m root -M exec /usr/share/smartmontools/smartd-runner

It also makes sense to use the symbolic link /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F rather than e.g. /dev/sda, as the later is not necessarily a stable name.

However, with the above in smartd.conf, smartd output in syslog shows that apparently both devices /dev/disk/by-id/ata-Samsung_SSD_850_PRO_1TB_S252NXAG910017F and /dev/sda (which I assume is still auto-detected by the DEVICESCAN) are now monitored (presumably with different monitoring settings).

Cheers, Chris.

Forwarded from: ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893665

Hi.

It seems that smartd, even with a configuration like: DEVICESCAN -d auto -d removable … (i.e. similar or equal to the default config in Debian), doesn't detect devices which are added after (i.e. removable devices) the daemon was started.

Example: 1) Start smartd (respectively it runs from system boot)

It "sees" my internal SSD.

2) I add an external HDD via USB-SATA-bridge.

The USB-SATA-bridge I'm using requires no special smartmontools config, i.e. smartctl --all /dev/sdX works out of the box.

Now even if I wait for the default of 1800s (after which it would "check" again) it doesn't *not* take note of the new device and add it to the monitored ones.

Only if I SIGHUP the daemon, it will actually see and add it.

So the first problem here is that smartd never seems to scan for new devices on it's own.

Even if it would, that would IMO not really solve the problem, as a maximum of 30 min (assuming the default interval) is probably too long to take note of SMART issues. Mostly because it can easily happen that an external device isn't even connected for so long (e.g. I just connect it to get some data on it and then I remove it again).

I also think, that sending SIGHUP automatically (e.g. via some cron job or systemd timer) is not really the best solution, as it would also cause the config to be read in again (which may be just edited).

The best thing would probably be if udev or systemd could somehow magically inform smartd when a new device is added (ideally without the later reading in the configs again). Then, smartd could immediately make a first check, thus the device would get checked even if it was removed again before the 30 mins.

One word of caution though: IMO it would be bad, if any cron/systemd/udev solution would actually start smartd. If one does e.g. digital forensics and intentionally stops smartd.serice in order to prevent any SMART commands being run on devices... it shouldn't come back by itself ;-)

Thanks, Chris.

Running

smartd version 5.38

under

Debian Lenny 5.0.5 amd64

using a

HP SmartArray P212/256

smartctl works correctly:

sudo smartctl -d cciss,0 -a /dev/cciss/c0d0

smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Serial number: 9RXKJ6P9            
Device type: disk
Local Time is: Mon Aug 30 17:57:02 2010 CEST
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
SMART Health Status: OK

Current Drive Temperature:     <not available>
Read defect list: asked for grown list but didn't get it

Error Counter logging not supported
Device does not support Self Test logging

But smartd not.

In

/etc/smartd.conf:

/dev/cciss/c0d0 -d cciss,0 -H -m root@localhost

Running:

sudo invoke-rc.d smartmontools start

gives the following errors in syslog: A

ug 30 17:58:12 crosrv07 smartd[6798]: smartd version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Aug 30 17:58:12 crosrv07 smartd[6798]: Home page is http://smartmontools.sourceforge.net/#012
Aug 30 17:58:12 crosrv07 smartd[6798]: Opened configuration file /etc/smartd.conf
Aug 30 17:58:12 crosrv07 smartd[6798]: Configuration file /etc/smartd.conf parsed.
Aug 30 17:58:12 crosrv07 smartd[6798]: Device: /dev/cciss/c0d0 [cciss_disk_00], opened
Aug 30 17:58:12 crosrv07 smartd[6798]: Device /dev/cciss/c0d0 [cciss_disk_00]: using '-d sat' for ATA disk behind SAT layer.
Aug 30 17:58:12 crosrv07 smartd[6798]: Device: /dev/cciss/c0d0 [cciss_disk_00], opened
Aug 30 17:58:12 crosrv07 kernel: [17501.663995] program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
Aug 30 17:58:12 crosrv07 smartd[6798]: Device: /dev/cciss/c0d0 [cciss_disk_00], not found in smartd database.
Aug 30 17:58:12 crosrv07 smartd[6798]: Device: /dev/cciss/c0d0 [cciss_disk_00], ATA IDENTIFY DEVICE words 82-83 don't specify if SMART capable.
Aug 30 17:58:12 crosrv07 smartd[6798]: Device: /dev/cciss/c0d0 [cciss_disk_00], to proceed anyway, use '-T permissive' Directive.
Aug 30 17:58:12 crosrv07 smartd[6798]: Unable to register SCSI device /dev/cciss/c0d0 [cciss_disk_00] at line 144 of file /etc/smartd.conf
Aug 30 17:58:12 crosrv07 smartd[6798]: Unable to register device /dev/cciss/c0d0 [cciss_disk_00] (no Directive -d removable). Exiting.

If you need further info, asl without problems.