smartd is not running

[Bernd80]

Hello,

I'm new to FreeNAS and have one issue I'm not able to solve. I installed FreeNAS-9.10.1 with 16GB RAM and 3x2TB disks in RAIDZ on an ESXi server.
Everything works well but after each boot I've one warning message (yellow light on top right) telling me
"smartd is not running."

In storage listing all drives I see for each drive SMART is active. I hope someone is able to point me in the right direction.

Regrads,
Bernd

 

[joeschmuck]

That is because you likely either don't have the ESXi setup to pass-through the hard drives or you are using VM hard drives. It is important to have smartd working. Please note that ESXi support is not really supported here but you will get support from many of the users here. If you want further support, please describe the physical parts on your machine and how they are connected. Be as descriptive as possible, don't assume we understand a thing, it generally works out better that way. And we will not assume you know what you are doing (sounds a bit harsh) so you may be asked to do something which we may consider obvious but we have no idea of your experience level. This will help us help you better.

And if you could describe how your setup the VM, that would be helpful, and include the .vmx file.

 

[Bernd80]

Hi Thanks for your reply. Yes you're right the hard drives are virtual vmdk on different physical hard drives.
They are not connected as RDM (Raw Device Mapping), as also ESX does not support to map SATA drives without tweaks.

So do I understand you right, that I can disable the S.M.A.R.T service to silence this message as it makes in my (ESXi specific) configuration no difference whether S.M.A.R.T is enabled or not? Or is there anythin else you would recommend in my situation?

Attached my VMX file for the case it plays a role.

 

[SweetAndLow]

Hi Thanks for your reply. Yes you're right the hard drives are virtual vmdk on different physical hard drives.
They are not connected as RDM (Raw Device Mapping), as also ESX does not support to map SATA drives without tweaks.

So do I understand you right, that I can disable the S.M.A.R.T service to silence this message as it makes in my (ESXi specific) configuration no difference whether S.M.A.R.T is enabled or not? Or is there anythin else you would recommend in my situation?

Attached my VMX file for the case it plays a role.

You will lose all your data if this is a real setup. Using vmdks with zfs doesn't make any sense if you expect zfs to keep your data safe.

Sent from my Nexus 5X using Tapatalk

 

[Bernd80]

I did some tests in advance before deciding to give FreeNAS a try, when a disk fails I was able to insert a new one and the RADIZ started succusfully to resilver. So I did not loose anythin in my test cases. Furthermore I've a backup solution in place. So your statement that I WILL lose all data makes no sense to me.

What is the difference compared to a Windows server with NTFS based shares on vmdk's? This is very common and the situation I come from.

 

[Ericloewe]

Look, we've been through this:
https://forums.freenas.org/index.ph...nas-in-production-as-a-virtual-machine.12484/
And this is the tip of the iceberg. Feel free to dig deeper.

 

[joeschmuck]

You are really taking a risk here but I understand what you have done. All we can do is warn you that you might be getting into some trouble here. If you do have issues, even unrelated to the hard drives, ensure that you disclose this in the forum posting because sometimes it will matter.

Good Luck.

 

[Bernd80]

Thank you for the given infromation.

I personally believe it has to be considered what kind of usage we are talking about. In my case this is at home for my family to access one file share from Mac, Windows and sometimes Ubuntu. So I'm sure virtualization gives me more advantages in case of hardware independency than disadvantages mentioned in the linked thread.

For all who wants to know what I did finally: I disabled S.M.A.R.T. service and the warning is gone as S.M.A.R.T. does not work with virtualized drives which is not a problem to me.

 

[SweetAndLow]

The only time it's acceptable to use vmdks is when you spin up a little server to test a scenario and then tear it down 1h later. When using them you don't get raw access to the disks. Zfs needs to write thing in a very specific way so it knows if something changes out from under it. This is what gives you the corruption protection. Your have created another layer of abstraction that is hurting performance. You don't get notifications if disk failure until it's too late. There are lots of reasons to not use virtual disks and zero reasons to use them. Doesn't matter if it's for home use or not. Sometimes home use is even more important because those pictures of your kids at age 3 can never be replaced of you let them get corrupt on your poorly designed Nas.

Sent from my Nexus 5X using Tapatalk

 

[Bernd80]

Well it's always easy to buy some extra hardware for each specific use case, but I'm not willing to spend additional bucks for hardware nor for the additional power consumption.

You say "Zfs needs to write thing in a very specific way", well it can do so, but in my case in a vmdk container. My perfromance tests so far were sufficient for my gigabit network. And again, losing data or not losing data is in my opinion a question of backup and not depending to virtualization.

 

[Ericloewe]

So I'm sure virtualization gives me more advantages in case of hardware independency

That's a fantasy advantage, because you're not running a massive cluster where you can juggle VMs between servers with ease. And because FreeNAS is as independent from the hardware as it can be.

 

[SweetAndLow]

Do what you want but fit the record anyone reading this in the future, don't do this.

Sent from my Nexus 5X using Tapatalk

 

[Bernd80]

What is fantasy to the fact that in case of hardware change it's as simple as copying a file from one disk to another to restart a virtaul machines? Maybe it's for FreeNAS also easy, but not for most other operating systems.

 

[SweetAndLow]

What is fantasy to the fact that in case of hardware change it's as simple as copying a file from one disk to another to restart a virtaul machines? Maybe it's for FreeNAS also easy, but not for most other operating systems.

It's even less work for freenas. What other vms are you running on this esxi server? Would it make more sense to install freenas and run the vms under freenas or use jails?

Sent from my Nexus 5X using Tapatalk

 

[joeschmuck]

@Bernd80

You can see that we have some very spirited and enthusiastic personnel here on the forums and they have the best of intentions. I also agree with their comments and all they are doing is trying to warn you that there is a pitfall in using vmdk files for FreeNAS so we would never recommend doing this for anything other than for a test bed and we would do our best to steer people away from doing this.

I guess there is nothing I could say to you since you say you will have a backup of your data elsewhere, which is smart no matter how your NAS was configured. Also I'm not sure why you are running ESXi in the first place and not running FreeNAS on a bare metal machine. I know I have my reasons but then again, my hard drives are dedicated and pass-through for FreeNAS.

If things do fail on you (I'm not hoping they do), I would sincerely appreciate a nice long posting as to what went wrong and something promoting to not do what you did. A nice warning basically if it's appropriate.

Cheers

 

[Bernd80]

Will do if this happens. Thanks

 

[AndersL]

Hello FreeNAS forum,
I have a problem not being able to start smartd.
FreeNAS 11.0 running on a Dell PowerEdge 1850, 8 GB ECC memory, Xeon 64bit processor. I have one SCSI disk as boot, 36 GB. Then two external 3 TB usb-disk in ZFS mirror config.
smartctl -a /dev/da1 gives error:

Code:

40:SU:freenas:~anders> smartctl -a /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/da1: Unknown USB bridge [0x0bc2:0x3322 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

But command:
smartctl -a -d scsi /dev/da1
works fine:

Code:

42:SU:freenas:~anders> smartctl -a -d scsi /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:  Seagate
Product:  Expansion Desk
Revision:  9401
Compliance:  SPC-4
User Capacity:  3,000,592,981,504 bytes [3.00 TB]
Logical block size:  512 bytes
Physical block size:  4096 bytes
Logical Unit id:  0x5000000000000001
Device type:  disk
Local Time is:  Wed Aug  2 14:26:31 2017 CEST
SMART support is:  Available - device has SMART capability.
SMART support is:  Disabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:  0 C
Drive Trip Temperature:  0 C

Error Counter logging not supported

Device does not support Self Test logging

I tried to insert -d scsi in the /usr/local/etc/smartd.conf, but then I get error

Code:

Aug  1 16:47:12 freenas smartd[10166]: Unable to register SCSI device /dev/da1 at line 4 of file /usr/local/etc/smartd.conf
Aug  1 16:47:12 freenas smartd[10166]: Unable to register device /dev/da1 (no Directive -d removable). Exiting.

when I try to start smartd manually.

Original contents of /usr/local/etc/smartd.conf:

Code:

################################################
# smartd.conf generated by /etc/ix.rc.d/ix-smartd
################################################
/dev/da1 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da2 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py

I realise that changes of this file will be erased at the next boot, but it should be good to test it when the system is up and running.
In the man page for smartd.conf the -d TYPE is listed, but it seems not to be accepted when smartd reads it.

Output from smartd -V:

smartd 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

smartd comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 6.5 dated 2016-05-07 at 11:17:46 UTC
smartmontools SVN rev 4318 dated 2016-05-07 at 11:18:20
smartmontools build host: amd64-portbld-freebsd11.0
smartmontools build with: C++98, GCC 4.2.1 Compatible FreeBSD Clang 4.0.0 (tags/RELEASE_400/final 297347)
smartmontools configure arguments: '--disable-dependency-tracking' '--enable-sample' '--with-nvme-devicescan=yes' '--with-initscriptdir=/usr/local/etc/rc.d' '--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd11.0' 'build_alias=amd64-portbld-freebsd11.0' 'CXX=c++' 'CXXFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing ' 'LDFLAGS= -fstack-protector' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing'


Best wishes
Anders Liljeborg

 

[Spearfoot]

Hello FreeNAS forum,
I have a problem not being able to start smartd.
FreeNAS 11.0 running on a Dell PowerEdge 1850, 8 GB ECC memory, Xeon 64bit processor. I have one SCSI disk as boot, 36 GB. Then two external 3 TB usb-disk in ZFS mirror config.
smartctl -a /dev/da1 gives error:

Code:

40:SU:freenas:~anders> smartctl -a /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/da1: Unknown USB bridge [0x0bc2:0x3322 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

But command:
smartctl -a -d scsi /dev/da1
works fine:

Code:

42:SU:freenas:~anders> smartctl -a -d scsi /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:  Seagate
Product:  Expansion Desk
Revision:  9401
Compliance:  SPC-4
User Capacity:  3,000,592,981,504 bytes [3.00 TB]
Logical block size:  512 bytes
Physical block size:  4096 bytes
Logical Unit id:  0x5000000000000001
Device type:  disk
Local Time is:  Wed Aug  2 14:26:31 2017 CEST
SMART support is:  Available - device has SMART capability.
SMART support is:  Disabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:  0 C
Drive Trip Temperature:  0 C

Error Counter logging not supported

Device does not support Self Test logging

I tried to insert -d scsi in the /usr/local/etc/smartd.conf, but then I get error

Code:

Aug  1 16:47:12 freenas smartd[10166]: Unable to register SCSI device /dev/da1 at line 4 of file /usr/local/etc/smartd.conf
Aug  1 16:47:12 freenas smartd[10166]: Unable to register device /dev/da1 (no Directive -d removable). Exiting.

when I try to start smartd manually.

Original contents of /usr/local/etc/smartd.conf:

Code:

################################################
# smartd.conf generated by /etc/ix.rc.d/ix-smartd
################################################
/dev/da1 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da2 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py

I realise that changes of this file will be erased at the next boot, but it should be good to test it when the system is up and running.
In the man page for smartd.conf the -d TYPE is listed, but it seems not to be accepted when smartd reads it.

Output from smartd -V:

smartd 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

smartd comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 6.5 dated 2016-05-07 at 11:17:46 UTC
smartmontools SVN rev 4318 dated 2016-05-07 at 11:18:20
smartmontools build host: amd64-portbld-freebsd11.0
smartmontools build with: C++98, GCC 4.2.1 Compatible FreeBSD Clang 4.0.0 (tags/RELEASE_400/final 297347)
smartmontools configure arguments: '--disable-dependency-tracking' '--enable-sample' '--with-nvme-devicescan=yes' '--with-initscriptdir=/usr/local/etc/rc.d' '--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd11.0' 'build_alias=amd64-portbld-freebsd11.0' 'CXX=c++' 'CXXFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing ' 'LDFLAGS= -fstack-protector' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing'


Best wishes
Anders Liljeborg

Using USB-connected drives is not advised: FreeNAS (ZFS) works best with direct access to the hard drives, via either the motherboard's SATA ports or a HBA (host bus adapter).

The listing returned by smartctl shows this result:

Code:

SMART support is:  Disabled

...which I believe explains why the smartd service cannot access the disks and therefore cannot start correctly.

See the Hardware Recommendations Guide for a good overview of FreeNAS' hardware requirements.

Good luck!

 

[AndersL]

But the really irritating thing is that I have the same hardware configuration running FreeNAS 8.3.0 with a working smartd! Same Dell PowerEdge1850 (we got several of these very cheap) and two 2 TB usb-disks plus a boot disk exactly the same as for the FreeNAS 11 system.
On the 8.3.0 system the /usr/local/etc/smartd.conf looks like:

Code:

################################################
# smartd.conf generated by /etc/rc.d/ix-smartd
################################################
/dev/da0 -n never -W 0,0,0
/dev/da1 -n never -W 0,0,0
/dev/da2 -n never -W 0,0,0

So here all three disks are included.
The command smartctl -a /dev/da1 gives:

Code:

smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p5 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:  WDC WD20EZRX-00DC0B0
Serial Number:  WD-WMC1T0802510
LU WWN Device Id: 5 0014ee 0ae1b360f
Firmware Version: 80.00A80
User Capacity:  2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:  512 bytes logical, 4096 bytes physical
Device is:  Not in smartctl database [for details use: -P showall]
ATA Version is:  8
ATA Standard is:  ACS-2 (revision not indicated)
Local Time is:  Wed Aug  2 16:30:48 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
  was completed without error.
  Auto Offline Data Collection: Enabled.
Self-test execution status:  (  0) The previous self-test routine completed
  without error or no self-test has ever
  been run.
Total time to complete Offline
data collection:  (25980) seconds.
Offline data collection
capabilities:  (0x7b) SMART execute Offline immediate.
  Auto Offline data collection on/off support.
  Suspend Offline collection upon new
  command.
  Offline surface scan supported.
  Self-test supported.
  Conveyance Self-test supported.
  Selective Self-test supported.
SMART capabilities:  (0x0003) Saves SMART data before entering
  power-saving mode.
  Supports SMART auto save timer.
Error logging capability:  (0x01) Error logging supported.
  General Purpose Logging supported.
Short self-test routine
recommended polling time:  (  2) minutes.
Extended self-test routine
recommended polling time:  ( 263) minutes.
Conveyance self-test routine
recommended polling time:  (  5) minutes.
SCT capabilities:  (0x70b5) SCT Status supported.
  SCT Feature Control supported.
  SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG  VALUE WORST THRESH TYPE  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate  0x002f  200  200  051  Pre-fail  Always  -  0
  3 Spin_Up_Time  0x0027  180  177  021  Pre-fail  Always  -  5991
  4 Start_Stop_Count  0x0032  068  068  000  Old_age  Always  -  32319
  5 Reallocated_Sector_Ct  0x0033  200  200  140  Pre-fail  Always  -  0
  7 Seek_Error_Rate  0x002e  200  200  000  Old_age  Always  -  0
  9 Power_On_Hours  0x0032  056  056  000  Old_age  Always  -  32681
10 Spin_Retry_Count  0x0032  100  100  000  Old_age  Always  -  0
11 Calibration_Retry_Count 0x0032  100  253  000  Old_age  Always  -  0
12 Power_Cycle_Count  0x0032  100  100  000  Old_age  Always  -  28
192 Power-Off_Retract_Count 0x0032  200  200  000  Old_age  Always  -  14
193 Load_Cycle_Count  0x0032  165  165  000  Old_age  Always  -  106871
194 Temperature_Celsius  0x0022  114  108  000  Old_age  Always  -  36
196 Reallocated_Event_Count 0x0032  200  200  000  Old_age  Always  -  0
197 Current_Pending_Sector  0x0032  200  200  000  Old_age  Always  -  0
198 Offline_Uncorrectable  0x0030  200  200  000  Old_age  Offline  -  0
199 UDMA_CRC_Error_Count  0x0032  200  200  000  Old_age  Always  -  0
200 Multi_Zone_Error_Rate  0x0008  200  200  000  Old_age  Offline  -  0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
  1  0  0  Not_testing
  2  0  0  Not_testing
  3  0  0  Not_testing
  4  0  0  Not_testing
  5  0  0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The difference is that the FreeNAS 11 system have two Seagate usb-disks instead of Western Digital.
So for this Western Digital 2 TB usb-disk everything works for smartd.
I thought smartd would enable support for SMART in the disk.

Is the there a way to manually enable SMART support?

 

[SweetAndLow]

Hello FreeNAS forum,
I have a problem not being able to start smartd.
FreeNAS 11.0 running on a Dell PowerEdge 1850, 8 GB ECC memory, Xeon 64bit processor. I have one SCSI disk as boot, 36 GB. Then two external 3 TB usb-disk in ZFS mirror config.
smartctl -a /dev/da1 gives error:

Code:

40:SU:freenas:~anders> smartctl -a /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/da1: Unknown USB bridge [0x0bc2:0x3322 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

But command:
smartctl -a -d scsi /dev/da1
works fine:

Code:

42:SU:freenas:~anders> smartctl -a -d scsi /dev/da1
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:  Seagate
Product:  Expansion Desk
Revision:  9401
Compliance:  SPC-4
User Capacity:  3,000,592,981,504 bytes [3.00 TB]
Logical block size:  512 bytes
Physical block size:  4096 bytes
Logical Unit id:  0x5000000000000001
Device type:  disk
Local Time is:  Wed Aug  2 14:26:31 2017 CEST
SMART support is:  Available - device has SMART capability.
SMART support is:  Disabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:  0 C
Drive Trip Temperature:  0 C

Error Counter logging not supported

Device does not support Self Test logging

I tried to insert -d scsi in the /usr/local/etc/smartd.conf, but then I get error

Code:

Aug  1 16:47:12 freenas smartd[10166]: Unable to register SCSI device /dev/da1 at line 4 of file /usr/local/etc/smartd.conf
Aug  1 16:47:12 freenas smartd[10166]: Unable to register device /dev/da1 (no Directive -d removable). Exiting.

when I try to start smartd manually.

Original contents of /usr/local/etc/smartd.conf:

Code:

################################################
# smartd.conf generated by /etc/ix.rc.d/ix-smartd
################################################
/dev/da1 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py
/dev/da2 -a -n standby -W 0,0,0 -m anders@biox.kth.se -M exec /usr/local/www/freenasUI/tools/smart_alert.py

I realise that changes of this file will be erased at the next boot, but it should be good to test it when the system is up and running.
In the man page for smartd.conf the -d TYPE is listed, but it seems not to be accepted when smartd reads it.

Output from smartd -V:

smartd 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

smartd comes with ABSOLUTELY NO WARRANTY. This is free
software, and you are welcome to redistribute it under
the terms of the GNU General Public License; either
version 2, or (at your option) any later version.
See http://www.gnu.org for further details.

smartmontools release 6.5 dated 2016-05-07 at 11:17:46 UTC
smartmontools SVN rev 4318 dated 2016-05-07 at 11:18:20
smartmontools build host: amd64-portbld-freebsd11.0
smartmontools build with: C++98, GCC 4.2.1 Compatible FreeBSD Clang 4.0.0 (tags/RELEASE_400/final 297347)
smartmontools configure arguments: '--disable-dependency-tracking' '--enable-sample' '--with-nvme-devicescan=yes' '--with-initscriptdir=/usr/local/etc/rc.d' '--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd11.0' 'build_alias=amd64-portbld-freebsd11.0' 'CXX=c++' 'CXXFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing ' 'LDFLAGS= -fstack-protector' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-pipe -g -fstack-protector -fno-strict-aliasing'


Best wishes
Anders Liljeborg

USB drives should never be used with zfs/freenas. They will cause all kinds of problems and corrupt your pool. These USB drives also are the reason smartd will not stay because smart is not supported.

Sent from my Nexus 5X using Tapatalk