Custom Query (1291 matches)
Results (49 - 51 of 1291)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#79 | wontfix | smartd opensolaris service defination | ||
Description |
Attached is an {open}solaris service definition. The configure script should alter some of the path names but otherwise should work flexibly. An make install target could do something like: cp smartd.xml /var/svc/manifest/site/ chown root:sys /var/svc/manifest/site/smartd.xml svccfg -v import /var/svc/manifest/site/smartd.xml Documentation could say run 'svcadm enable smartd' to get it running I'm still getting this error. I'm running out of time to debug it. Tips welcome. svc:/system/smartd:default (SMART monitoring) State: maintenance since June 9, 2010 01:54:26 PM EST Reason: Start method failed repeatedly, last exited with status 10. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smartd See: man -M /usr/share/man -s 4 smartd.conf See: /var/svc/log/system-smartd:default.log Impact: This service is not running. /var/svc/log/system-smartd:default.log [ Jun 9 13:52:06 Rereading configuration. ] [ Jun 9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ] [ Jun 9 13:54:26 Method "start" exited with status 10. ] [ Jun 9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ] [ Jun 9 13:54:26 Method "start" exited with status 10. ] [ Jun 9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ] [ Jun 9 13:54:26 Method "start" exited with status 10. ] |
|||
#1538 | invalid | smartd gets confused about which drive is reporting temperature changes? | ||
Description |
OS: OpenSUSE Leap 15.3 (x86-64) smartmontools version 7.0-6.1 I've received a number of smartd email notifications over the past few weeks. Every time, the system journal suggests that smartd detected a temperature change on /dev/sda but that an error was logged against /dev/nvme. My system has two SSDs: /dev/sda: Samsung 850 EVO /dev/nvme0: SK Hynix P31 The following warning/error was logged by the smartd daemon today: Device: /dev/nvme0, number of Error Log entries increased from 11 to 12 Device info: SHGP31-1000GM-2, S/N:XXXXXX, FW:41060C20 The system journal from that timestamp shows the following: smartd[1511]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 [Raw 26] to 73 [Raw 27] smartd[1511]: Device: /dev/nvme0, number of Error Log entries increased from 11 to 12 smartd[1511]: Sending warning via <mail> to xxxxxxxx@xxxxxxxx ... smartd[1511]: Warning via <mail> to xxxxxx@xxxxxxxx: successful For some reason, it looks like smartd logged the error against /dev/nvme0? |
|||
#1248 | worksforme | smartd fails to start when no disks are present | ||
Description |
As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862908 "smartd" fails to start on the system without disks (e.g. KVM). It would be better to start the daemon anyway and wait for pluggable disks to appear. This could help to prevent init system failures on attempted start of "smartd". |