Seagate ST8000NM0075 no smart data over SAS

[cookiesowns]

So..............

I decided to be a guinea pig and go with the Seagate ST8000NM0075 512E SAS V5 drives, along with dual LSI 9300-8I HBA's.

Array Setup:

24x 8TB Segate 8TB V5 SAS drives

Supermicro 24bay Dual SAS3.0 Expander

2x Avago LSI 9300-8i in x8 wideport, 1 per expander. MultiPath in FreeNAS is working fine.

Running FreeNAS 9.10, and it runs great in 4x 6 drive Z2 config. Scrubs at 3GB/s when new, and can easily push 800+MB/s over ZFS send and NCAT, probably even more as the bottleneck is a 40% fragmented sending pool that's 90% full.....

That said, right now, the biggest bummer is that there is basically no meaningful SMART data I can get out of these drives.

The only output I get is something like this:

smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE amd64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: ST8000NM0075
Revision: E001
Compliance: SPC-4
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LB provisioning type: unreported, LBPME=0, LBPRZ=0
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000c5008XXXXXX
Serial number: ZA10GXXXXXXXXXX
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Wed Mar 30 10:39:47 2016 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Elements in grown defect list: 0

Error Counter logging not supported

Device does not support Self Test logging
Device does not support Background scan results logging



It tells me NOTHING, no temperature no nothing. The Avago LSI cards are on P10 IT firmware. I know the card is fine because on Windows with MSM, I can get the drive temperatures no problem.

SAS3IRCU is no help either.

 

[maglin]

Would using the P20 firmware maybe help? Running a short test will get you temps at the time of the test. I have the Seagate 8TB SATA archive drives on a SAS2 expander and will check it out. Also maybe update smart CTL


Sent from my iPhone using Tapatalk

 

[cookiesowns]

Would using the P20 firmware maybe help? Running a short test will get you temps at the time of the test. I have the Seagate 8TB SATA archive drives on a SAS2 expander and will check it out. Also maybe update smart CTL


Sent from my iPhone using Tapatalk

P20 firmware is only for SAS2 HBA's. I'm on SAS3 HBA's with SAS3 expanders.

 

[depasseg]

I think the driver is v9, so your firmware should also be on v9. I don't think it shouldn't make a difference for SMART reporting, but you never know.

 

[Kz8]

I was assembling an array on Dell's H730p megaraid (rebranded LSI/Avago) with a bunch of ST8000NM0075 -s today, and for this specific drive as of time of this writing, to get smartctl to read SMART metrics, I had to patch smartctl sources according to comment 22 to get it output like in my comment 24 of this thread: https://www.smartmontools.org/ticket/678#comment:24

 

[Chris Moore]

I decided to be a guinea pig and go with the Seagate ST8000NM0075 512E SAS V5 drives, along with dual LSI 9300-8I HBA's.

Did you get this working?

 

[kettnsaeg]

Doing a short test with said ST8000NM0075 SAS drives now gives the following informations in 11.2-U4.1 (out of the box in my case). The temperature of the drives seems to be new (?):

Code:

smartctl -a /dev/da2
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              ST8000NM0075
Revision:             E004
Compliance:           SPC-4
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x500XXXXX60b
Serial number:        ZA1XXXXD
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Wed May 29 23:36:30 2019 CEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     38 C
Drive Trip Temperature:        60 C

RIG is: CSE826B (SAS2 Backplane), X9DRD-7LN4F-JBOD, integrated Broadcom 2308 controller in IT-mode and 6 of the said drives plus one hot-spare drive.

As I am still *verry* new to this system I get that there should be more Information in the test. Which is why I added a WD-Blue for short time to do a "sanity" smart-check. This gave proper results. I'd be open to providing more information on the SAS drives if that's of use to anyone.

 

[Chris Moore]

smartctl -a /dev/da2

Use a -x instead of a -a and you will see more detail, but SAS drives just don't respond the same way SATA drives do.

 

[Chris Moore]

You should look at the script below for monitoring SAS drive health.
More details in the original thread if I recall correctly.

SAS version:

If a drive is over a chosen limit temperature then the chosen warning symbol will be added to the end of the device name. If it is over the critical temperature then it's the critical symbol that will be added instead of the warning symbol.

Then there is a detailed block for each drive with the SMART attributes, the error log, and the details of the last self-test.

The output (there's only one drive is this example because I've done the tests with a file provided by cyberjock (thanks to him BTW) as I don't have any SAS drive but look at the output example of the SATA version if you want to see what it looks like with more than one drive): http://pastebin.com/56LuTdKe

The script: http://pastebin.com/veDv2FfZ Don't forget to put your email address and your drives labels in the parameters section at the top of the script ;)

 

[kettnsaeg]

I'd like to add one (maybe obvious to experienced users) thing in this case:

Do not make the mistake I did... use a proper shell, *not* the GUI shell. The bugfix in the referenced smartmontools ticket seems to work properly and smartctl -x gives following Info this way:

Code:

smartctl -x /dev/da2

smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              ST8000NM0075
Revision:             E004
Compliance:           SPC-4
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0xxxxxxxxxxxxx
Serial number:        Zxxxxxxxxx
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sat Jun  1 00:59:08 2019 CEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     34 C
Drive Trip Temperature:        60 C

Manufactured in week �� of year 20��
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  62
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  69
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 2075112
  Blocks received from initiator = 50148304
  Blocks read from cache and sent to initiator = 69145
  Number of read and write commands whose size <= segment size = 296053
  Number of read and write commands whose size > segment size = 340

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 41.03
  number of minutes until next internal SMART test = 53

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:     440056        0         0    440056          0          0.793           0
write:         0        0         0         0          0         27.870           0
verify:   162178        0         0    162178          0          0.269           0

Non-medium error count:        0

Self-test execution status:             90% of test remaining
SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background long   Self test in progress ...   -     NOW                 - [-   -    -]
# 2  Background short  Completed                   -      31                 - [-   -    -]
# 3  Background short  Completed                   -      17                 - [-   -    -]
# 4  Background short  Completed                   -       7                 - [-   -    -]
# 5  Background long   Aborted (device reset ?)    -       2                 - [-   -    -]
# 6  Background short  Completed                   -       1                 - [-   -    -]

Long (extended) Self Test duration: 47220 seconds [787.0 minutes]

Background scan results log
  Status: no scans active
    Accumulated power on time, hours:minutes 41:02 [2462 minutes]
    Number of background scans performed: 0,  scan progress: 0.00%
    Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 0
  number of phys = 1
  phy identifier = 0
    attached device type: expander device
    attached reason: SMP phy control function
    reason: power on
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=1
    SAS address = xxxxxxxxxxxxxxxxxxxxxx
    attached SAS address = xxxxxxxxxxxxxxxxxxxxxxx
    attached phy identifier = 15
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0
relative target port id = 2
  generation code = 0
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = xxxxxxxxxxxxxxxxxxxx
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0

And here's another Info to this drive and SMART: I found out that these drives do seem to give astronomicly high read error rates in the SMART Info. I've found others dealing with the same amount of errors on servethehome. Referencing e.g. this document on error calculations (sata) for Seagate drives and citing Seagate on post #14

...I heard back from Seagate. They are saying that this is a normal value for hard drives and that Seagate drives report raw error values, not filtered or rate, like other manufacturers...

I'll be at least looking into those, reading up and setting up the sas script before trusting in the system.