Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Nov 2019 12:08:48 +1030
From:      "O'Connor, Daniel" <darius@dons.net.au>
To:        freebsd-stable <freebsd-stable@freebsd.org>
Subject:   smartd, mfi, SAS and SATA
Message-ID:  <72D950A5-4DFE-4CF6-A2C1-77A37D51B89E@dons.net.au>

next in thread | raw e-mail | index | archive | help
Hi everyone,
I recently took delivery of a Supermicro X11SRM-F with a Broadcom =
MegaRAID 9361-8i SAS 8 port card which has 4 Intel D3-S4610 960 GB SSDs =
and 4 Hitachi/WD Ultrastar HC300 4TB drives each in a RAID5.

I have /usr/local/etc/smartd.conf with just 'DEVICESCAN' and when smartd =
starts I see..
Nov 21 01:17:49 maarsy-acq3 smartd[2103]: Opened configuration file =
/usr/local/etc/smartd.conf
Nov 21 01:17:49 maarsy-acq3 smartd[2103]: Drive: DEVICESCAN, implied =
'-a' Directive on line 23 of file /usr/local/etc/smartd.conf
Nov 21 01:17:49 maarsy-acq3 smartd[2103]: Configuration file =
/usr/local/etc/smartd.conf was parsed, found DEVICESCAN, scanning =
devices
Nov 21 01:17:49 maarsy-acq3 smartd[2103]: Device: /dev/pass0, opened
Nov 21 01:17:49 maarsy-acq3 smartd[2103]: Device: /dev/pass0, [HGST     =
HUS726T4TAL5204  C40H], lu id: 0x5000cca097502308, S/N: V6HE27MR, 4.00 =
TB
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass0, is SMART =
capable. Adding to "monitor" list.
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass1, opened
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass1, [HGST     =
HUS726T4TAL5204  C40H], lu id: 0x5000cca09751d2c8, S/N: V6HEZZZR, 4.00 =
TB
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass1, is SMART =
capable. Adding to "monitor" list.
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass2, opened
Nov 21 01:17:50 maarsy-acq3 smartd[2103]: Device: /dev/pass2, [HGST     =
HUS726T4TAL5204  C40H], lu id: 0x5000cca097509ad8, S/N: V6HEA6ZR, 4.00 =
TB
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass2, is SMART =
capable. Adding to "monitor" list.
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass3, opened
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass3, [HGST     =
HUS726T4TAL5204  C40H], lu id: 0x5000cca0974f1630, S/N: V6HDHALR, 4.00 =
TB
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass3, is SMART =
capable. Adding to "monitor" list.
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass4, type =
changed from 'scsi' to 'sat'
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass5, type =
changed from 'scsi' to 'sat'
Nov 21 01:17:51 maarsy-acq3 smartd[2103]: Device: /dev/pass6, type =
changed from 'scsi' to 'sat'
Nov 21 01:17:52 maarsy-acq3 smartd[2103]: Device: /dev/pass7, type =
changed from 'scsi' to 'sat'
Nov 21 01:17:52 maarsy-acq3 smartd[2103]: Monitoring 0 ATA/SATA, 4 =
SCSI/SAS and 0 NVMe devices
Nov 21 01:17:53 maarsy-acq3 smartd[2105]: smartd has fork()ed into =
background mode. New PID=3D2105.
Nov 21 01:17:53 maarsy-acq3 smartd[2105]: file /var/run/smartd.pid =
written containing PID 2105

So it is monitoring the SAS disks but has ignored the SATA SSDs :(

[maarsy-acq3 1:33] ~> camcontrol devlist
<HGST HUS726T4TAL5204 C40H>        at scbus8 target 8 lun 0 (pass0)
<HGST HUS726T4TAL5204 C40H>        at scbus8 target 9 lun 0 (pass1)
<HGST HUS726T4TAL5204 C40H>        at scbus8 target 10 lun 0 (pass2)
<HGST HUS726T4TAL5204 C40H>        at scbus8 target 11 lun 0 (pass3)
<ATA INTEL SSDSC2KB96 0120>        at scbus8 target 12 lun 0 (pass4)
<ATA INTEL SSDSC2KB96 0120>        at scbus8 target 13 lun 0 (pass5)
<ATA INTEL SSDSC2KB96 0120>        at scbus8 target 14 lun 0 (pass6)
<ATA INTEL SSDSC2KB96 0120>        at scbus8 target 15 lun 0 (pass7)
<Verbatim STORE N GO PMAP>         at scbus9 target 0 lun 0 (da0,pass8)

If I run smartctl on an SSD I get..
[maarsy-acq3 1:33] ~> sudo smartctl -a /dev/pass4|less
smartctl 7.0 2018-12-30 r4883 [FreeBSD 12.0-RELEASE amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, =
www.smartmontools.org

Smartctl open device: /dev/pass4 [SAT] failed: SATA device detected,
MegaRAID SAT layer is reportedly buggy, use '-d sat' to try anyhow

And using what it suggests seems to work - does anyone know a way to =
force it to work with DEVICESCAN?

For now I've just hard coded it like so..
DEFAULT -m root
/dev/pass0
/dev/pass1
/dev/pass2
/dev/pass3
/dev/pass4 -d sat
/dev/pass5 -d sat
/dev/pass6 -d sat
/dev/pass7 -d sat

but it seems clunky.. also I see these slightly puzzling messages for =
each SSD..
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], =
opened
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], =
INTEL SSDSC2KB960G8, S/N:PHYF92630636960CGN, WWN:5-5cd2e4-150f430c3, =
FW:XCV10120, 960 GB
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], =
found in smartd database: Intel S4510/S4610/S4500/S4600 Series SSDs
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], not =
capable of SMART Health Status check
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], =
can't monitor Offline_Uncorrectable count - no Attribute 198
Nov 21 01:37:08 maarsy-acq3 smartd[3656]: Device: /dev/pass4 [SAT], is =
SMART capable. Adding to "monitor" list.

Which I am hoping aren't anything to worry about..

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?72D950A5-4DFE-4CF6-A2C1-77A37D51B89E>