ZFS Problems enabling smartd service

ujjain

ujjain

I've used Linux for guys, but I don't know much about BSD, so I'd love some help.

I'd like to replace my Synology by a NAS-VM. The H330 HBA is passthrough'ed to the VM. Everything looks nice, but I'm quiet new to this and can't be sure.

One of the issues is that there's absolutely no smart information on the disks, even though I can read the smart info from a Linux VM.
Code: 
nas4free: ~# zfs list
NAME                   USED  AVAIL  REFER  MOUNTPOINT
nvme                  1.13M  77.0G    88K  /mnt/nvme
tank                  14.5M  14.0T   192K  /tank
tank/backups           176K  14.0T   176K  /tank/backups
tank/benchmarks       10.5M  14.0T  10.5M  /tank/benchmarks
tank/media             176K  14.0T   176K  /tank/media
tank/nas4free         2.00M  14.0T  2.00M  /tank/nas4free
tank/xpenology_4tb_1   112K  14.0T   112K  -
tank/xpenology_4tb_2   112K  14.0T   112K  -
nas4free: ~# gpart list
Geom name: mfisyspd0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 7814037127
first: 40
entries: 152
scheme: GPT
Providers:
1. Name: mfisyspd0p1
   Mediasize: 4000778813440 (3.6T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 4194304
   Mode: r1w1e1
   rawuuid: abf38377-8455-11e7-9561-005056bc5d71
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: volume1
   length: 4000778813440
   offset: 4194304
   type: freebsd-zfs
   index: 1
   end: 7814029311
   start: 8192
Consumers:
1. Name: mfisyspd0
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e2

Geom name: mfisyspd1
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 7814037127
first: 40
entries: 152
scheme: GPT
Providers:
1. Name: mfisyspd1p1
   Mediasize: 4000778813440 (3.6T)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 4194304
   Mode: r1w1e1
   rawuuid: ac8baed6-8455-11e7-9561-005056bc5d71
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: volume1
   ...
first: 40
entries: 152
scheme: GPT
Providers:
1. Name: da0p1
   Mediasize: 524288 (512K)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 20480
   Mode: r0w0e0
   rawuuid: 34a233d6-8453-11e7-ab7f-005056bc5d71
   rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
   label: gptboot
   length: 524288
   offset: 20480
   type: freebsd-boot
   index: 1
   end: 1063
   start: 40
2. Name: da0p2
   Mediasize: 1073741824 (1.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 4194304
   Mode: r1w0e0
   rawuuid: 34a4fe64-8453-11e7-ab7f-005056bc5d71
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: gptroot
   length: 1073741824
   offset: 4194304
   type: freebsd-ufs
   index: 2
   end: 2105343
   start: 8192
3. Name: da0p3
   Mediasize: 4294967296 (4.0G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1077936128
   Mode: r1w1e0
   rawuuid: 34a65a1a-8453-11e7-ab7f-005056bc5d71
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: gptswap
   length: 4294967296
   offset: 1077936128
   type: freebsd-swap
   index: 3
   end: 10493951
   start: 2105344
4. Name: da0p4
   Mediasize: 16097738752 (15G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1077936128
   Mode: r0w0e0
   rawuuid: 34a7c323-8453-11e7-ab7f-005056bc5d71
   rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 16097738752
   offset: 5372903424
   type: freebsd-ufs
   index: 4
   end: 41934847
   start: 10493952
Consumers:
1. Name: da0
   Mediasize: 21474836480 (20G)
   Sectorsize: 512
   Mode: r2w1e1

nas4free: ~# smartctl -i /dev/mfi
mfi0%        mfisyspd0%   mfisyspd0p1% mfisyspd1%   mfisyspd1p1% mfisyspd2%   mfisyspd2p1% mfisyspd3%   mfisyspd3p1% mfisyspd4%   mfisyspd4p1% mfisyspd5%   mfisyspd5p1%
nas4free: ~# camcontrol devlist -v
scbus0 on ata0 bus 0:
<>                                 at scbus0 target -1 lun ffffffff ()
scbus1 on ata1 bus 0:
<>                                 at scbus1 target -1 lun ffffffff ()
scbus2 on mpt0 bus 0:
<VMware Virtual disk 2.0>          at scbus2 target 0 lun 0 (pass0,da0)
<>                                 at scbus2 target -1 lun ffffffff ()
scbus-1 on xpt0 bus 0:
<>                                 at scbus-1 target -1 lun ffffffff (xpt0)
nas4free: ~#

Zpool status:

nas4free: ~# zpool status
  pool: nvme
 state: ONLINE
  scan: none requested
config:

    NAME        STATE     READ WRITE CKSUM
    nvme        ONLINE       0     0     0
     nvd2      ONLINE       0     0     0

errors: No known data errors

  pool: tank
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Sat Aug 19 00:34:05 2017
config:

    NAME             STATE     READ WRITE CKSUM
    tank             ONLINE       0     0     0
     raidz2-0       ONLINE       0     0     0
       mfisyspd0p1  ONLINE       0     0     0
       mfisyspd1p1  ONLINE       0     0     0
       mfisyspd2p1  ONLINE       0     0     0
       mfisyspd3p1  ONLINE       0     0     0
       mfisyspd4p1  ONLINE       0     0     0
       mfisyspd5p1  ONLINE       0     0     0
    logs
     nvd1           ONLINE       0     0     0
    cache
     nvd0           ONLINE       0     0     0

errors: No known data errors
nas4free: ~#

nas4free: ~# smartctl -i /dev/mfisyspd
mfisyspd0%   mfisyspd0p1% mfisyspd1%   mfisyspd1p1% mfisyspd2%   mfisyspd2p1% mfisyspd3%   mfisyspd3p1% mfisyspd4%   mfisyspd4p1% mfisyspd5%   mfisyspd5p1%
nas4free: ~# smartctl -i /dev/mfisyspd3
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-RELEASE-p1 amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/mfisyspd3: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

nas4free: ~#
 
ujjain said:
...One of the issues is that there's absolutely no smart information on the disks, even though I can read the smart info from a Linux VM.
Click to expand...
I'm not really well acquainted with raid configurations but the *mfi prefix in the output of smartctl -i /dev/mfisyspd means that this is hardware raid -- maybe that's why...
 
Not all mfi(4) based cards have hardware RAID. Some cards are plain HBAs. But, some of these cards don't allow direct access at all (required for smartctl(8)), some can be 'forwarded' by using the -d option to smartctl(8) and some do allow direct access.
 
  • Thanks
Reactions: gfx
The Dell PERC H330 has 2 controller modes, RAID and HBA. I've configured it to operate as HBA with Nas4free in a virtual machine.
 
ujjain said:
One of the issues is that there's absolutely no smart information on the disks, even though I can read the smart info from a Linux VM.
Click to expand...
You probably need to load the [semi-]undocumented mfip(4) kernel module: # kldload mfip. Once you do that, the physical disks should show up in a # camcontrol devlist report as pass(4)N devices and you can use those device names in sysutils/smartmontools. Note that you don't want to do any other I/O on the passN devices as you'll be accessing the physical drives "behind the controller's back".
Code: 
(0:33) host:~terry# camcontrol devlist
<HITACHI HUS156030VLS600 E774>     at scbus0 target 0 lun 0 (pass0)
<HITACHI HUS156030VLS600 E774>     at scbus0 target 1 lun 0 (pass1)
<HITACHI HUS156030VLS600 E774>     at scbus0 target 2 lun 0 (pass2)
<HITACHI HUS156030VLS600 E774>     at scbus0 target 3 lun 0 (pass3)
<HITACHI HUS156030VLS600 E774>     at scbus0 target 4 lun 0 (pass4)
<HITACHI HUS156030VLS600 E774>     at scbus0 target 5 lun 0 (pass5)
<DP BACKPLANE 1.07>                at scbus0 target 32 lun 0 (pass6,ses0)
<TEAC DVD-ROM DV-28SW R.2A>        at scbus1 target 0 lun 0 (cd0,pass7)
(0:34) host:~terry# smartctl -a /dev/pass0
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HITACHI
Product:              HUS156030VLS600
Revision:             E774
Compliance:           SPC-4
User Capacity:        300,000,000,000 bytes [300 GB]
Logical block size:   512 bytes
[...]
 
You must log in or register to reply here.
Back
Top