Custom Query (1265 matches)


Show under each result:

Results (52 - 54 of 1265)

Ticket Resolution Summary Owner Reporter
#121 worksforme smartd fails to report disk failure if a disk doesn't respond anymore Christian Franke kaluscha

I had a self test running on disk hdb:

smartd: Device: /dev/hdb, self-test in progress, 10% remaining

The disk encountered problems, see /var/log/messages:

kernel: hdb: dma_timer_expiry: dma status == 0x61
kernel: hdb: DMA timeout error
kernel: hdb: dma timeout error: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hda: DMA disabled
kernel: hdb: DMA disabled
kernel: ide0: reset: success

There were several kernel IDE resets until the drive didn't respond anymore:

kernel: hdb: drive not ready for command

smartd wrote messages:

smartd: Device: /dev/hdb, failed to read Temperature

However, smartd had been configured to send e-mails in case of trouble (/dev/hdb -a -I 194 -W 4,40,42 -R 5 -m myamil). In this case, it failed to do so.

In my opinion this is a major problem as smartd should inform the admins that a disk is complety offline, i.,e. doesn't respond to requests on the IDE bus anymore.

#1015 duplicate smartd double monitors devices when using symlinks to devices calestyo

Forwarded from:


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.

#1014 duplicate smartd doesn't notice newly added devices afters start calestyo

Forwarded from:


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.

Note: See TracQuery for help on using queries.