Description of problem: In F-11 the configuration file /etc/smartd.conf had simply a DEVICESCAN entry with some options, including "-d sat", and, consequently, all the SATA disks, two in this system, were monitored by "smartd". In F-12, the very same directive does not seem to work, since no HDD are found. Version-Release number of selected component (if applicable): smartmontools-5.39-1.fc12.x86_64 How reproducible: Always, as far as I tried. Steps to Reproduce: 1. Have a configuration file, /etc/smartd.conf, with: DEVICESCAN -d sat -S on -a -H -s L/../../7/14 -m root 2. Start "smartd", with "service smartd restart" (or "start") 3. Check /var/log/messages for smartd entries. Actual results: ... Jan 10 13:52:54 lazy smartd[1865]: smartd 5.39 2009-12-09 r2995 [x86_64-redhat-linux-gnu] (local build)#012Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net#012 Jan 10 13:52:54 lazy smartd[1865]: Opened configuration file /etc/smartd.conf Jan 10 13:52:54 lazy smartd[1865]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices Jan 10 13:52:54 lazy smartd[1865]: In the system's table of devices NO devices found to scan Jan 10 13:52:54 lazy smartd[1865]: Monitoring 0 ATA and 0 SCSI devices Jan 10 13:52:54 lazy smartd[1867]: smartd has fork()ed into background mode. New PID=1867. Jan 10 13:56:49 lazy smartd[1867]: smartd received signal 15: Terminated Jan 10 13:56:49 lazy smartd[1867]: smartd is exiting (exit status 0) ... So, it seems, no ATA or SCSI devices are found. Expected results: The same as in F-11, something like: ... Dec 6 14:13:06 lazy smartd[2159]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Dec 6 14:13:06 lazy smartd[2159]: Home page is http://smartmontools.sourceforge.net/#012 Dec 6 14:13:06 lazy smartd[2159]: Opened configuration file /etc/smartd.conf Dec 6 14:13:06 lazy smartd[2159]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices Dec 6 14:13:06 lazy smartd[2159]: Device: /dev/sda, opened Dec 6 14:13:06 lazy smartd[2159]: Device: /dev/sda, found in smartd database. Dec 6 14:13:06 lazy smartd[2159]: Device: /dev/sda, enabled SMART Attribute Autosave. Dec 6 14:13:06 lazy smartd[2159]: Device: /dev/sda, is SMART capable. Adding to "monitor" list. Dec 6 14:13:06 lazy smartd[2159]: Device: /dev/sdb, opened Dec 6 14:13:07 lazy smartd[2159]: Device: /dev/sdb, found in smartd database. Dec 6 14:13:07 lazy smartd[2159]: Device: /dev/sdb, enabled SMART Attribute Autosave. Dec 6 14:13:07 lazy smartd[2159]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list. Dec 6 14:13:07 lazy smartd[2159]: Device: /dev/sdc, opened Dec 6 14:13:07 lazy smartd[2159]: Device: /dev/sdc, not ATA, no IDENTIFY DEVICE Structure Dec 6 14:13:07 lazy smartd[2159]: Monitoring 2 ATA and 0 SCSI devices Dec 6 14:13:07 lazy smartd[2198]: smartd has fork()ed into background mode. New PID=2198. ... Note that /dev/sdc is a SBP-2 device, hence no smart, but still found and scanned. Additional info: Since "smartd" claims it does not find devices to scan, it could be there are none, so this might be a kernel issue or related components. Unfortunately, I've no idea on how to check this, but I'll be glad to do it, if someone would tell me how. Of course, changing the DEVICESCAN directive with: /dev/sda -d sat -S on -a -H -s L/../../7/14 -m root /dev/sdb -d sat -S on -a -H -s L/../../7/14 -m root Does work as expected, with following log: ... Jan 10 13:58:12 lazy smartd[2343]: smartd 5.39 2009-12-09 r2995 [x86_64-redhat-linux-gnu] (local build)#012Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net#012 Jan 10 13:58:12 lazy smartd[2343]: Opened configuration file /etc/smartd.conf Jan 10 13:58:12 lazy smartd[2343]: Configuration file /etc/smartd.conf parsed. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sda [SAT], opened Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sda [SAT], found in smartd database. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sda [SAT], enabled SMART Attribute Autosave. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sdb [SAT], opened Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sdb [SAT], found in smartd database. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sdb [SAT], enabled SMART Attribute Autosave. Jan 10 13:58:12 lazy smartd[2343]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list. Jan 10 13:58:12 lazy smartd[2343]: Monitoring 2 ATA and 0 SCSI devices Jan 10 13:58:12 lazy smartd[2366]: smartd has fork()ed into background mode. New PID=2366. ... Hope this helps, bye, pg
hi, thanks for the report why do you have '-d sat' on DEVICESCAN line? Does it work for you without this?
Hi, (In reply to comment #1) > why do you have '-d sat' on DEVICESCAN line? Does it work for you without this? if I remember correctly, originally, without "-d sat", it was not working. After a quick investigation, I found out that it was needed, so I've it there. I'll try without it and report here. Thanks, bye, pg
Hi, it seems you're right, the "-d sat" directive does not appear to be needed anymore and it is even causing the problem. Removing it seems to fix the issue. I guess you can close this bug, even if I would suggest to check the documentation, since I cannot remember (but I could be wrong, of course) that this details are specified there. Thanks a lot for the support, bye, pg
After reading a man pages it seems a)it should work b)man pages are out of date, so I've asked upstream for answer.
the answer is A), it should work. It's already reported upsteam http://sourceforge.net/apps/trac/smartmontools/ticket/13 I'll wait for their solution and update smartmontools afterwards
fixed in smartmontools-5.39-2.fc12
smartmontools-5.39-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/smartmontools-5.39-2.fc12
smartmontools-5.39-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update smartmontools'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0870
smartmontools-5.39.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update smartmontools'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0870
smartmontools-5.39.1-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.