Project

General

Profile

Bug #34360

Document workaround for when SMART service refuses to start on U5

Added by Bonnie Follweiler almost 3 years ago. Updated almost 3 years ago.

Status:
Done
Priority:
No priority
Assignee:
Dru Lavigne
Category:
Documentation
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Related projects 1 project

Description

I'm getting an error message in the UI "smartd_daemon is not running"
When I went to Services to start S.M.A.R.T. it wont start.


Related issues

Related to FreeNAS - Bug #48108: Fix typo in smartd.pyDone
Has duplicate FreeNAS - Bug #32571: smartd_daemon is not runningClosed

History

#2 Updated by Dru Lavigne almost 3 years ago

  • Category changed from OS to Middleware
  • Assignee changed from Caleb St. John to William Grzybowski
  • Target version changed from Backlog to 11.1-U6

#4 Updated by Dru Lavigne almost 3 years ago

  • Project changed from TrueNAS to FreeNAS
  • Category changed from Middleware to Middleware
  • Migration Needed deleted (No)
  • Hide from ChangeLog deleted (No)
  • Support Department Priority deleted (0)

#5 Updated by Dru Lavigne almost 3 years ago

  • Has duplicate Bug #32571: smartd_daemon is not running added

#6 Updated by Vladimir Vinogradenko almost 3 years ago

We have not been doing any changes in 11.1 since they are too breaking (from my POV).

#7 Updated by Dru Lavigne almost 3 years ago

William: if this is decided to not be backported, we'll need workaround instructions to add to the Relnotes.

#8 Updated by Nicolas Gilles almost 3 years ago

Hi,

I also run into this issue since upgrading to 11.1-U5 (from 11.1-Ux) ... The relevant log from the smartd logs looks like this:
In my case /dev/da0 and /dev/da1 are the USB boot devices (sandisk cruzer fit 16GB).

May 31 23:54:54 storm smartd[13590]: smartd 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
May 31 23:54:54 storm smartd[13590]: Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
May 31 23:54:54 storm smartd[13590]: Opened configuration file /usr/local/etc/smartd.conf
May 31 23:54:54 storm smartd[13590]: Configuration file /usr/local/etc/smartd.conf parsed.
May 31 23:54:54 storm smartd[13590]: Device: /dev/ada0, opened
May 31 23:54:54 storm smartd[13590]: Device: /dev/ada0, WDC WD40EFRX-68WT0N0, S/N:WD-WCC4EJUPNVTH, WWN:5-0014ee-20a858b5d, FW:80.00A80, 4.00 TB
May 31 23:54:54 storm smartd[13590]: Device: /dev/ada0, found in smartd database: Western Digital Red
May 31 23:54:55 storm smartd[13590]: Device: /dev/ada0, is SMART capable. Adding to "monitor" list.
May 31 23:54:55 storm smartd[13590]: Device: /dev/ada1, opened
May 31 23:54:55 storm smartd[13590]: Device: /dev/ada1, WDC WD40EFRX-68WT0N0, S/N:WD-WCC4EA7FE7JK, WWN:5-0014ee-20a85952a, FW:80.00A80, 4.00 TB
May 31 23:54:55 storm smartd[13590]: Device: /dev/ada1, found in smartd database: Western Digital Red
May 31 23:54:56 storm smartd[13590]: Device: /dev/ada1, is SMART capable. Adding to "monitor" list.
May 31 23:54:56 storm smartd[13590]: Device: /dev/ada2, opened
May 31 23:54:56 storm smartd[13590]: Device: /dev/ada2, WDC WD40EFRX-68WT0N0, S/N:WD-WCC4EHYCFVUT, WWN:5-0014ee-25fdad60f, FW:80.00A80, 4.00 TB
May 31 23:54:56 storm smartd[13590]: Device: /dev/ada2, found in smartd database: Western Digital Red
May 31 23:54:57 storm smartd[13590]: Device: /dev/ada2, is SMART capable. Adding to "monitor" list.
May 31 23:54:57 storm smartd[13590]: Device: /dev/ada3, opened
May 31 23:54:57 storm smartd[13590]: Device: /dev/ada3, WDC WD40EFRX-68WT0N0, S/N:WD-WCC4EHYCFKVY, WWN:5-0014ee-20a85952d, FW:80.00A80, 4.00 TB
May 31 23:54:57 storm smartd[13590]: Device: /dev/ada3, found in smartd database: Western Digital Red
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada3, is SMART capable. Adding to "monitor" list.
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, opened
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, Samsung SSD 850 EVO 120GB, S/N:S21UNXAGB47481E, WWN:5-002538-d407e9c7b, FW:EMT02B6Q, 120 GB
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, found in smartd database: Samsung based SSDs
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, can't monitor Current_Pending_Sector count - no Attribute 197
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, can't monitor Offline_Uncorrectable count - no Attribute 198
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada5, is SMART capable. Adding to "monitor" list.
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, opened
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, Samsung SSD 850 EVO 120GB, S/N:S21UNXAGB47412J, WWN:5-002538-d407e9c36, FW:EMT02B6Q, 120 GB
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, found in smartd database: Samsung based SSDs
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, can't monitor Current_Pending_Sector count - no Attribute 197
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, can't monitor Offline_Uncorrectable count - no Attribute 198
May 31 23:54:58 storm smartd[13590]: Device: /dev/ada4, is SMART capable. Adding to "monitor" list.
May 31 23:54:58 storm smartd[13590]: Device: /dev/da1, unable to autodetect device type
May 31 23:54:58 storm smartd[13590]: Unable to register device /dev/da1 (no Directive -d removable). Exiting.

#9 Updated by Janus Ng almost 3 years ago

For

May 31 23:54:58 storm smartd[13590]: Unable to register device /dev/da1 (no Directive -d removable). Exiting.

I have encountered that since 11.1, U something that I cannot remember. I have fixed it by marking the incompatible SMART device as disabled on the Storage->View Disk->[select device]->Edit button->Enable S.M.A.R.T->uncheck.

#10 Updated by Janus Ng almost 3 years ago

The SMART service started as it should be after making the above change.

#11 Updated by William Grzybowski almost 3 years ago

  • Category changed from Middleware to Documentation
  • Assignee changed from William Grzybowski to Dru Lavigne

Dru, there is no simple fix here, we have completely rewritten smart scripts for 11.2 to be able to sanely fix these kind of problems.

The workaround is what Janus described above.

#12 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Unscreened to Done
  • Target version changed from 11.1-U6 to N/A
  • Needs QA changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#13 Updated by Nicolas Gilles almost 3 years ago

I have tried the workaround mentioned above, but I still get the error. Could it be that the smartd.conf isn't being regenerated upon config change?

#14 Updated by Dru Lavigne almost 3 years ago

  • Category changed from Documentation to Middleware
  • Assignee changed from Dru Lavigne to Vladimir Vinogradenko
  • Seen in changed from TrueNAS 11.1-U5 to 11.1-U5

Vlad: do you know the answer to the last comment?

#15 Updated by Vladimir Vinogradenko almost 3 years ago

Nicolas, are you absolutely sure that you have disabled all disks causing problems? If so, please post output of cat /usr/local/etc/smartd.conf and cat /var/log/daemon.log | grep -i smart

#16 Updated by Nicolas Gilles almost 3 years ago

Yes, I just triple checked and indeed da0 and da1 were set to "false" in the smart column. The daemon.log output is the same as what I posted above. It was always da1 causing trouble.

The smartd.conf was "odd" though:

################################################
# smartd.conf generated by /etc/ix.rc.d/ix-smartd
################################################
/dev/ada0 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/ada1 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/ada2 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/ada3 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/ada5 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/ada4 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da1 -a -n never -W 0,37,40 -m nicolas.gilles@gmail.com -M exec /usr/local/www/freenasUI/tools/smart_alert.py

So I tried a couple of moves, and it magically got fixed. I think the issue was that I used the "bulk edit" feature to edit the disks the first time.

#17 Updated by Dru Lavigne almost 3 years ago

  • Subject changed from Error "smartd_daemon is not running." and S.M.A.R.T. Service wont start to Document workaround for when SMART service refuses to start on U5
  • Category changed from Middleware to Documentation
  • Assignee changed from Vladimir Vinogradenko to Dru Lavigne

#18 Updated by Jeff Ervin over 2 years ago

  • Related to Bug #48108: Fix typo in smartd.py added

Also available in: Atom PDF