smartd failing to start FreeNAS-9.10.1 running on Dell R730xd

[chownp]

SAS3 needs sas3flash, not sas2flash.

Thanks, but unfortunately no better.

Code:

# sas3flash -listall
Avago Technologies SAS3 Flash Utility
Version 10.00.00.01 (2015.06.18)
Copyright 2008-2015 Avago Technologies. All rights reserved.

   No Avago SAS adapters found! Limited Command Set Available!
   ERROR: Command Not allowed without an adapter!
   ERROR: Couldn't Create Command -listall
   Exiting Program.

 

[Ericloewe]

Try sas3ircu.

 

[chownp]

OK, I *think* I have fixed this. Reading the mrsas(4) man page I found a useful section on mfi vs mrsas driver priority, on the strength of this I have edited /boot/device.hints and added:

Code:

hw.mfi.mrsas_enable="1"

Rebooted machine. Now camcontrol gives me a different looking list of devices

Code:

# camcontrol devlist -v
scbus0 on mrsas0 bus 0:
<>  at scbus0 target -1 lun ffffffff ()
scbus1 on mrsas0 bus 1:
<HGST HUS726060AL5214 KK06>  at scbus1 target 0 lun 0 (pass0,da0)
<HGST HUS726060AL5214 KK06>  at scbus1 target 1 lun 0 (pass1,da1)
<HGST HUS726060AL5214 KK06>  at scbus1 target 2 lun 0 (pass2,da2)
<HGST HUS726060AL5214 KK06>  at scbus1 target 3 lun 0 (pass3,da3)
<HGST HUS726060AL5214 KK06>  at scbus1 target 4 lun 0 (pass4,da4)
<HGST HUS726060AL5214 KK06>  at scbus1 target 5 lun 0 (pass5,da5)
<HGST HUS726060AL5214 KK06>  at scbus1 target 6 lun 0 (pass6,da6)
<HGST HUS726060AL5214 KK06>  at scbus1 target 7 lun 0 (pass7,da7)
<HGST HUS726060AL5214 KK06>  at scbus1 target 8 lun 0 (pass8,da8)
<HGST HUS726060AL5214 KK06>  at scbus1 target 9 lun 0 (pass9,da9)
<HGST HUS726060AL5214 KK06>  at scbus1 target 10 lun 0 (pass10,da10)
<HGST HUS726060AL5214 KK06>  at scbus1 target 11 lun 0 (pass11,da11)
<SanDisk LT0200MO D40Z>  at scbus1 target 12 lun 0 (pass12,da12)
<SanDisk LT0200MO D40Z>  at scbus1 target 13 lun 0 (pass13,da13)

We have da<n> devices!

If I now slide the SMART switch on the Services page of the UI it stays "On" and I have a list of devices in smartd.conf which looks more promising:

Code:

# cat /usr/local/etc/smartd.conf
################################################
# smartd.conf generated by /etc/ix.rc.d/ix-smartd
################################################
/dev/da0 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da1 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da4 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da5 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da6 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da7 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da8 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da9 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da10 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da11 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da2 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py -s S/(01|02|03|04|05|06|07|08|09|10|11|12)/../(1|2|3|4|5|6|7)/(14|16|18)
/dev/da3 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py -s S/(01|02|03|04|05|06|07|08|09|10|11|12)/../(1|2|3|4|5|6|7)/(14|16|18)
/dev/da12 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da13 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py

I will schedule some tests and report how it goes.

 

[Ericloewe]

Ooh, that looks promising. If you filed a bug ticket, be sure to mention what you did. It not, I urge you to do so, because mfi is a pain in the ass in the best of times.

Seeing direct-attach SCSI devices is a nice step forward.

 

[Mirfster]

Nice! For sure it looks like you are on the right path.

 

[chownp]

I used the UI to schedule a short test on drives 2 and 3 and left it too it.

Have just logged back in and used smartctl to check the test status and get

Code:

smartctl -l selftest /dev/da2
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num  Test  Status  segment  LifeTime  LBA_first_err [SK ASC ASQ]
  Description  number  (hours)
# 1  Background short  Completed  80  227  - [-  -  -]
# 2  Background short  Completed  80  6  - [-  -  -]
# 3  Reserved(7)  Completed  64  6  - [-  -  -]

Long (extended) Self Test duration: 45749 seconds [762.5 minutes]

[root@grey] ~# smartctl -l selftest /dev/da3
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num  Test  Status  segment  LifeTime  LBA_first_err [SK ASC ASQ]
  Description  number  (hours)
# 1  Background short  Completed  80  227  - [-  -  -]
# 2  Background short  Completed  80  6  - [-  -  -]
# 3  Reserved(7)  Completed  64  6  - [-  -  -]

Long (extended) Self Test duration: 46422 seconds [773.7 minutes]

[root@grey] ~# smartctl -l selftest /dev/da4
smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num  Test  Status  segment  LifeTime  LBA_first_err [SK ASC ASQ]
  Description  number  (hours)
# 1  Background short  Completed  80  6  - [-  -  -]
# 2  Reserved(7)  Completed  64  6  - [-  -  -]

Long (extended) Self Test duration: 46086 seconds [768.1 minutes]

So looks like all that is working.

I'm going to file a "tips" ticket in the Hardware topic of this forum.

Is this still considered an installation bug i.e. should the FreeNAS installer spot the hardware and make the necessary driver priority changes? If so I'll file in bugtracker.

 

[Stux]

I'm wondering if this option just shouldn't be on by default.

Fairly sure FreeNAS always wants pure HBA mode.

Assuming the hint makes no difference when the hardware is not present.

 

[Ericloewe]

I'm wondering if this option just shouldn't be on by default.

Fairly sure FreeNAS always wants pure HBA mode.

Assuming the hint makes no difference when the hardware is not present.

At most, it might break mfi-exclusive stuff, which is hardly a tragedy.

 

[Ericloewe]

Is this still considered an installation bug i.e. should the FreeNAS installer spot the hardware and make the necessary driver priority changes? If so I'll file in bugtracker.

Definitely file it. As for category, I'm not sure, but you'll probably want to bring jpaetzel's attention to this.

 

[chownp]

I'm wondering if this option just shouldn't be on by default.

Fairly sure FreeNAS always wants pure HBA mode.

Assuming the hint makes no difference when the hardware is not present.

Yes, the whole point about using FreeNAS is that you want HBA mode. I've raised a bug along the lines that if FreeNAS should automatically install correctly on hardware in the FreeBSD HCL then the installer is making a wrong choice in this instance by not applying the hint.

https://bugs.freenas.org/issues/18136

 

[joeschmuck]

Good bug report, glad you didn't spare any information.