[Update: Seller Complaints Accumulating] HGST Ultrastar He10 - 10TB @ $129.95

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
H

heromode

Active Member
May 25, 2020
401
229
43
Samir said:
Real pro-tip--don't buy fakes from china and get a genuine used card and cables for truly trouble-free operation. ;)
Click to expand...
I buy the cables from china, not the card. My LSI 3008 is from a professional german shop, i paid 150€ for it, and is absolutely genuine.

The chinese cables are great, and the correct price level. Western made cables are daylight robbery.

edit: my bad, the way i said it made it seem like i buy the LSI cards from China. Not so. Your pro-pro-tip was warranted due to my poorly formed sentence.
 
Last edited:
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
Hi, i used the 'scsi-SATA_HGST_HUH721010AL_XXXXXXX' just as an example, each drive has a slightly different code. Find your drive in /dev/disk/by-id/ ( ls -la /dev/disk/by-id/ )

^^ edit sorry, you're on freebsd, but just find your drive wherever it is in BSD, every drive has a unique ending. Use grep with capital H in Helium.

or alternatively just run lsblk, and identify your drive there.

the helium level should show on any HUH* drive. It is under the 'Vendor Specific SMART Attributes with Thresholds:'
I admit i've never run it on a SAS drive, but should be there too by all logic.

oh yeah, u need to use capital H on helium.

Here is my Vendor Specific SMART Attributes with Thresholds output as reference:

Code: 
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   132   132   054    Pre-fail  Offline      -       103
  3 Spin_Up_Time            0x0007   154   154   024    Pre-fail  Always       -       446 (Average 408)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       15
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   128   128   020    Pre-fail  Offline      -       18
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       12798
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       15
22 Helium_Level            0x0023   100   100   025    Pre-fail  Always       -       100
192 Power-Off_Retract_Count 0x0032   088   088   000    Old_age   Always       -       14493
193 Load_Cycle_Count        0x0012   088   088   000    Old_age   Always       -       14493
194 Temperature_Celsius     0x0002   136   136   000    Old_age   Always       -       44 (Min/Max 19/53)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
Click to expand...
Nothing I do will make the sas disks show the vendor specific codes honestly I think it's a sas related logic and it just doesn't show that data?.

lsblk is not valid in bsd
ls -la /dev/da2/ using either serial number or logical unit id number does nothing.
Running the smrtcommand on my hgst 3tb stat drives on the same machine through the same hba and expander gives the vender specifc output
shown below.

Code: 
smartctl -a /dev/da9

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       80
  3 Spin_Up_Time            0x0007   119   119   024    Pre-fail  Always       -       521 (Average 522)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       23
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   121   121   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       10738
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       23
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       314
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       314
194 Temperature_Celsius     0x0002   181   181   000    Old_age   Always       -       33 (Min/Max 15/38)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
I'm beginning to wonder if smartctl in truenas is borked. I've noticed an line of code in the -x that might be why..

Code: 
Vendor (Seagate Cache) information
  Blocks sent to initiator = 5534258198216704
I'm wondering if for some reason smartclt is thinking the drives are seagates and that is why it will not report the data.
 
Last edited:
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
I'm beginning to wonder if smartctl in truenas is borked. I've noticed an line of code in the -x that might be why..

Code: 
Vendor (Seagate Cache) information
  Blocks sent to initiator = 5534258198216704
I'm wondering if for some reason smartclt is thinking the drives are seagates and that is why it will not report the data.
Click to expand...
Yeah, this is very interesting. That Seagate reference is weird! We are running the same version: smartctl 7.2 2020-12-30 r5155

My full -x output for your reference:

Code: 
# smartctl -x /dev/disk/by-id/scsi-SATA_HGST_HUH721010AL_2YK9XX7D
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.22-4-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Ultrastar He10
Device Model:     HGST HUH721010ALE604
Serial Number:    2YK9XX7D
LU WWN Device Id: 5 000cca 273eeca61
Firmware Version: LHGNW384
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Apr 18 20:09:50 2022 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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:                (   93) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (1116) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   016    -    0
  2 Throughput_Performance  P-S---   132   132   054    -    103
  3 Spin_Up_Time            POS---   154   154   024    -    446 (Average 408)
  4 Start_Stop_Count        -O--C-   100   100   000    -    15
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   128   128   020    -    18
  9 Power_On_Hours          -O--C-   099   099   000    -    12801
10 Spin_Retry_Count        PO--C-   100   100   060    -    0
12 Power_Cycle_Count       -O--CK   100   100   000    -    15
22 Helium_Level            PO---K   100   100   025    -    100
192 Power-Off_Retract_Count -O--CK   088   088   000    -    14500
193 Load_Cycle_Count        -O--C-   088   088   000    -    14500
194 Temperature_Celsius     -O----   146   146   000    -    41 (Min/Max 19/53)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    0
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      1  Comprehensive SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x04       GPL     R/O    256  Device Statistics log
0x04       SL      R/O    255  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x0c       GPL     R/O   5501  Pending Defects log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x12       GPL     R/O      1  SATA NCQ Non-Data log
0x13       GPL     R/O      1  SATA NCQ Send and Receive log
0x15       GPL     R/W      1  Rebuild Assist log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x24       GPL     R/O    256  Current Device Internal Status Data log
0x25       GPL     R/O    256  Saved Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%         1         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
Device State:                        Active (0)
Current Temperature:                    41 Celsius
Power Cycle Min/Max Temperature:     26/48 Celsius
Lifetime    Min/Max Temperature:     19/53 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -40/70 Celsius
Temperature History Size (Index):    128 (47)

Index    Estimated Time   Temperature Celsius
  48    2022-04-18 18:02    44  *************************
  49    2022-04-18 18:03    44  *************************
  50    2022-04-18 18:04    44  *************************
  51    2022-04-18 18:05    43  ************************
...    ..( 11 skipped).    ..  ************************
  63    2022-04-18 18:17    43  ************************
  64    2022-04-18 18:18    42  ***********************
...    ..(  5 skipped).    ..  ***********************
  70    2022-04-18 18:24    42  ***********************
  71    2022-04-18 18:25    43  ************************
...    ..( 12 skipped).    ..  ************************
  84    2022-04-18 18:38    43  ************************
  85    2022-04-18 18:39    42  ***********************
...    ..( 10 skipped).    ..  ***********************
  96    2022-04-18 18:50    42  ***********************
  97    2022-04-18 18:51    41  **********************
  98    2022-04-18 18:52    41  **********************
  99    2022-04-18 18:53    41  **********************
100    2022-04-18 18:54    42  ***********************
...    ..(  6 skipped).    ..  ***********************
107    2022-04-18 19:01    42  ***********************
108    2022-04-18 19:02    43  ************************
109    2022-04-18 19:03    42  ***********************
...    ..(  9 skipped).    ..  ***********************
119    2022-04-18 19:13    42  ***********************
120    2022-04-18 19:14    41  **********************
...    ..( 10 skipped).    ..  **********************
   3    2022-04-18 19:25    41  **********************
   4    2022-04-18 19:26    42  ***********************
...    ..( 12 skipped).    ..  ***********************
  17    2022-04-18 19:39    42  ***********************
  18    2022-04-18 19:40    41  **********************
...    ..( 15 skipped).    ..  **********************
  34    2022-04-18 19:56    41  **********************
  35    2022-04-18 19:57    42  ***********************
...    ..( 10 skipped).    ..  ***********************
  46    2022-04-18 20:08    42  ***********************
  47    2022-04-18 20:09    44  *************************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4              15  ---  Lifetime Power-On Resets
0x01  0x010  4           12801  ---  Power-on Hours
0x01  0x018  6     43683494116  ---  Logical Sectors Written
0x01  0x020  6        38066357  ---  Number of Write Commands
0x01  0x028  6     34726701943  ---  Logical Sectors Read
0x01  0x030  6       148172713  ---  Number of Read Commands
0x01  0x038  6     46085700950  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4            8124  ---  Spindle Motor Power-on Hours
0x03  0x010  4            8124  ---  Head Flying Hours
0x03  0x018  4           14500  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4         4309039  ---  Read Recovery Attempts
0x03  0x030  4               1  ---  Number of Mechanical Start Failures
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              41  ---  Current Temperature
0x05  0x010  1              42  N--  Average Short Term Temperature
0x05  0x018  1              41  N--  Average Long Term Temperature
0x05  0x020  1              53  ---  Highest Temperature
0x05  0x028  1              19  ---  Lowest Temperature
0x05  0x030  1              52  N--  Highest Average Short Term Temperature
0x05  0x038  1              25  N--  Lowest Average Short Term Temperature
0x05  0x040  1              47  N--  Highest Average Long Term Temperature
0x05  0x048  1              25  N--  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              60  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4               3  ---  Number of Hardware Resets
0x06  0x010  4              48  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
0xff  =====  =               =  ===  == Vendor Specific Statistics (rev 1) ==
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c)
No Defects Logged

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            4  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
 
H

heromode

Active Member
May 25, 2020
401
229
43
I'm expecting a couple of 8TB HUH728080AL5205 SAS drives to arrive any day now, plus then i wait for cables from china. So at some point i'll be able to pull data from them to compare.

Edit, quick search came up with this: GitHub - truenas/py-SMART: Wrapper for smartctl (smartmontools)

Edit2: maybe boot your freenas truenas box with a Debian 11 live USB to see if your running a python wrapper over smartctl
 
Last edited:
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
I'm expecting a couple of 8TB HUH728080AL5205 SAS drives to arrive any day now, plus then i wait for cables from china. So at some point i'll be able to pull data from them to compare.

Edit, quick search came up with this: GitHub - truenas/py-SMART: Wrapper for smartctl (smartmontools)

Edit2: maybe boot your freenas truenas box with a Debian 11 live USB to see if your running a python wrapper over smartctl
Click to expand...
I'm assuming your drives are sata correct? because when I run -a on my 3tb sata hgst's I get the vender specific logs just fine.

When I run the code you run exactly but just changing to the SN of my disk I get this..

I'm finding that it apears that Sas drives don't output info like their sata counterparts and if they are "oem" drives which these are as SN check on HGST site for warenty says to take them back to a vender.
I'm wondering if the firmware will need to be changed to a straight HGST only firmware.. How ever it will likely still not output like that of it's sata brethren.

Code: 
root@aeronas:~ # smartctl -x /dev/disk/by-id/scsi-SATA_HGST_HUH721010AL_2TJSYR3D
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/disk/by-id/scsi-SATA_HGST_HUH721010AL_2TJSYR3D: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

root@aeronas:~ #
I found this command.
Code: 
root@aeronas:~ # sg_logs -a /dev/da2
    HGST      HUH721010AL42C0   A3Z4

Supported log pages  [0x0]:
    0x00        Supported log pages [sp]
    0x02        Write error [we]
    0x03        Read error [re]
    0x05        Verify error [ve]
    0x06        Non medium [nm]
    0x08        Format status [fs]
    0x0d        Temperature [temp]
    0x0e        Start-stop cycle counter [sscc]
    0x0f        Application client [ac]
    0x10        Self test results [str]
    0x15        Background scan results [bsr]
    0x18        Protocol specific port [psp]
    0x19        General Statistics and Performance [gsp]
    0x1a        Power condition transitions [pct]
    0x2f        Informational exceptions [ie]
    0x30        Performance counters (Hitachi) [pc_hi]
    0x37        Cache (seagate) [c_se]

Write error counter page  [0x2]
  Errors corrected without substantial delay = 0
  Errors corrected with possible delays = 0
  Total rewrites or rereads = 0
  Total errors corrected = 0
  Total times correction algorithm processed = 604518
  Total bytes processed = 145636742172672 [145 TB]
  Total uncorrected errors = 0

Read error counter page  [0x3]
  Errors corrected without substantial delay = 0
  Errors corrected with possible delays = 3
  Total rewrites or rereads = 0
  Total errors corrected = 3
  Total times correction algorithm processed = 3654187
  Total bytes processed = 42666751029248 [42 TB]
  Total uncorrected errors = 0

Verify error counter page  [0x5]
  Errors corrected without substantial delay = 0
  Errors corrected with possible delays = 0
  Total rewrites or rereads = 0
  Total errors corrected = 0
  Total times correction algorithm processed = 47085
  Total bytes processed = 303104
  Total uncorrected errors = 0

Non-medium error page  [0x6]
  Non-medium error count = 0

Format status page  [0x8]
  Format data out: <not available>
  Grown defects during certification <not available>
  Total blocks reassigned during format <not available>
  Total new blocks reassigned <not available>
  Power on minutes since format <not available>

Temperature page  [0xd]
  Current temperature = 32 C
  Reference temperature = 85 C

Start-stop cycle counter page  [0xe]
  Date of manufacture, year: 2018, week: 12
  Accounting date, year: 2018, week: 12
  Specified cycle count over device lifetime = 50000
  Accumulated start-stop cycles = 16
  Specified load-unload count over device lifetime = 600000
  Accumulated load-unload cycles = 1201

Application client page  [0xf]
00     0f 00 40 00 00 00 03 fc  00 00 00 00 00 00 00 00
10     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
20     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
30     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
.....  [truncated after 64 of 16388 bytes (use '-H' to see the rest)]

Self-test results page  [0x10]
  Parameter code = 1, accumulated power-on hours = 28417
    self-test code: background extended [2]
    self-test result: aborted by SEND DIAGNOSTIC [1]
  Parameter code = 2, accumulated power-on hours = 0
    self-test code: background extended [2]
    self-test result: self test in progress [15]
  Parameter code = 3, accumulated power-on hours = 28250
    self-test code: background short [1]
    self-test result: completed without error [0]

Background scan results page  [0x15]
  Status parameters:
    Accumulated power on minutes: 1708011 [h:m  28466:51]
    Status: background scan enabled, none active (waiting for BMS interval timer to expire)
    Number of background scans performed: 169
    Background medium scan progress: 0.00 %
    Number of background medium scans performed: 169

Protocol Specific port page for SAS SSP  (sas-2) [0x18]
relative target port id = 1
  generation code = 2
  number of phys = 1
  phy identifier = 0
    attached SAS device type: expander device
    attached reason: SMP phy control function
    reason: unknown
    negotiated logical link rate: 12 Gbps
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=1
    SAS address = 0x5000cca26a9c4c55
    attached SAS address = 0x500304801eec03bf
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 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 = 2
  number of phys = 1
  phy identifier = 1
    attached SAS device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown rate
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca26a9c4c56
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0

General Statistics and Performance  [0x19]
Statistics and performance log parameter
  number of read commands = 542418940
  number of write commands = 331306294
  number of logical blocks received = 35555845257
  number of logical blocks transmitted = 10416687263
  read command processing intervals = 0
  write command processing intervals = 0
  weighted number of read commands plus write commands = 0
  weighted read command processing plus write command processing = 0
Idle time log parameter
  idle time intervals = 1908871769
Time interval log parameter for general stats
  time interval negative exponent = 2
  time interval integer = 5

Power condition transitions page  [0x1a]
  Accumulated transitions to active = 33484
  Accumulated transitions to idle_a = 33485
  Accumulated transitions to idle_b = 0
  Accumulated transitions to idle_c = 0
  Accumulated transitions to standby_z = 0
  Accumulated transitions to standby_y = 0

Informational Exceptions page  [0x2f]
  IE asc = 0x0, ascq = 0x0
    Current temperature = 32 C
    Threshold temperature = 85 C  [common extension]
  parameter code = 0x1, contents in hex:
00     00 01 03 03 64 64 19

HGST/WDC performance counters page [0x30]
  Zero Seeks = 8637
  Seeks >= 2/3 = 23092
  Seeks >= 1/3 and < 2/3 = 29424
  Seeks >= 1/6 and < 1/3 = 46274
  Seeks >= 1/12 and < 1/6 = 47229
  Seeks > 0 and < 1/12 = 21034
  Overrun Counter = 1
  Underrun Counter = 45274
  Device Cache Full Read Hits = 9220
  Device Cache Partial Read Hits = 285889
  Device Cache Write Hits = 406573
  Device Cache Fast Writes = 461900
  Device Cache Read Misses = 3146404

HGST/WDC miscellaneous page [0x37, 0x0]
  Power on hours = 28466
  Total Bytes Read = 42666751029248
  Total Bytes Written = 145636742172672
  Max Drive Temp (Celsius) = 35
  GList Size = 0
  Number of Information Exceptions = 0
  MED EXC = 0
  HDW EXC = 0
  Total Read Commands = 542418940
  Total Write Commands = 331306294
  Flash Correction Count = 0
root@aeronas:~ # sg_logs -x /dev/da2
Supported log pages  [0x0]:
    0x00        Supported log pages [sp]
    0x02        Write error [we]
    0x03        Read error [re]
    0x05        Verify error [ve]
    0x06        Non medium [nm]
    0x08        Format status [fs]
    0x0d        Temperature [temp]
    0x0e        Start-stop cycle counter [sscc]
    0x0f        Application client [ac]
    0x10        Self test results [str]
    0x15        Background scan results [bsr]
    0x18        Protocol specific port [psp]
    0x19        General Statistics and Performance [gsp]
    0x1a        Power condition transitions [pct]
    0x2f        Informational exceptions [ie]
    0x30        Performance counters (Hitachi) [pc_hi]
    0x37        Cache (seagate) [c_se]
 
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
I'm assuming your drives are sata correct? because when I run -a on my 3tb sata hgst's I get the vender specific logs just fine.
Click to expand...
Correct
I know this is a SAS specific thread, and i was assuming smartctl would output just the same for SAS drives, because once again, the drives are mechanically exactly the same. Let's see if i'm gonna be proven a complete fool here. sometimes in the near future i'll have some HUH* SAS drives to test on, but atm i have none.
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
Also as far as your suggestion on changing boot.. my Truenas is in a vm on esxi with hba pci-passthrough.. The more I've been gathering the more I think this is a sas issue not wanting to give up any secrets rather then an issue with OS. I'm not exactly wanting to take a production system down. But I may. Shouldn't be too hard to just boot them vm into a live linux install for basic testing.
 
H

heromode

Active Member
May 25, 2020
401
229
43
When i receive my second hand SAS drives i know i'll be pissed off if i'm not gonna be able to check the helium levels on them.

Regarding the mechanics once more, no HDD manufacturer makes physically separate SAS drives anymore, there is no point.

You can't make them faster by spinning them at 10k rpm, and you can't make them more reliable etc.. If you look at the HGST he8, he10 and he12 spec sheets you see arrows to the left pointing to the SATA versions on all parameters except formatting, interface and power attributes. Because they are the same.

https://documents.westerndigital.co...astar-sas-series/data-sheet-ultrastar-he8.pdf

https://documents.westerndigital.co...c500-series/data-sheet-ultrastar-dc-hc510.pdf

https://documents.westerndigital.co...c500-series/data-sheet-ultrastar-dc-hc520.pdf

nothing but arrows to the left.
 
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
Also as far as your suggestion on changing boot.. my Truenas is in a vm on esxi with hba pci-passthrough.. The more I've been gathering the more I think this is a sas issue not wanting to give up any secrets rather then an issue with OS. I'm not exactly wanting to take a production system down. But I may. Shouldn't be too hard to just boot them vm into a live linux install for basic testing.
Click to expand...
Don't bother, i'll report here once i have my drives and cables.

Edit in the meantime, you could try to figure out if truenas is really using a python wrapper for smartctl. In linux i think the command is 'which' to see what is actually being run when you type smartctl.

or locate the actual smartctl binary and run it including the path.
 
Last edited:
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
When i receive my second hand SAS drives i know i'll be pissed off if i'm not gonna be able to check the helium levels on them.

Regarding the mechanics once more, no HDD manufacturer makes physically separate SAS drives anymore, there is no point.

You can't make them faster by spinning them at 10k rpm, and you can't make them more reliable etc.. If you look at the HGST he8, he10 and he12 spec sheets you see arrows to the left pointing to the SATA versions on all parameters except formatting, interface and power attributes. Because they are the same.

https://documents.westerndigital.co...astar-sas-series/data-sheet-ultrastar-he8.pdf

https://documents.westerndigital.co...c500-series/data-sheet-ultrastar-dc-hc510.pdf

https://documents.westerndigital.co...c500-series/data-sheet-ultrastar-dc-hc520.pdf

nothing but arrows to the left.
Click to expand...
I understand that the mechanical portion of the drive is the same. From what I've been readin sparcly is that it appears that the sas side of the controllers scsi seems to not have any uniformity and alot of things are hidden from smart escpecially if they are OEM drives.
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
Don't bother, i'll report here once i have my drives and cables.

Edit in the meantime, you could try to figure out if truenas is really using a python wrapper for smartctl. In linux i think the command is 'which' to see what is actually being run when you type smartctl.

or locate the actual smartctl binary and run in including the path.
Click to expand...
Code: 
root@aeronas:~ # which smartctl -a /dev/da2
/usr/local/sbin/smartctl
-a: Command not found.
/dev/da2: Command not found.
 
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
Code: 
root@aeronas:~ # which smartctl -a /dev/da2
/usr/local/sbin/smartctl
-a: Command not found.
/dev/da2: Command not found.
Click to expand...
nano /usr/local/sbin/smartctl

(to see if it's ascii or binary)

# ls -la /usr/sbin/smartctl
-rwxr-xr-x 1 root root 896912 Mar 8 2021 /usr/sbin/smartctl
 
Last edited:
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
I understand that the mechanical portion of the drive is the same. From what I've been readin sparcly is that it appears that the sas side of the controllers scsi seems to not have any uniformity and alot of things are hidden from smart escpecially if they are OEM drives.
Click to expand...
If that is the case, i will be contacting the smartctl devs and crying until i get my helium readings!
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
Well out of curiosity I called HGST support to ask if th
heromode said:
nano /usr/local/sbin/smartctl

(to see if it's ascii or binary)

# ls -la /usr/sbin/smartctl
-rwxr-xr-x 1 root root 896912 Mar 8 2021 /usr/sbin/smartctl
Click to expand...
Btw I just got off the phone with WD/HGST asking if there was a way to check helium levels on my M/N and S/N and they said NO.
but below is nano output and your ls -la

Code: 
^?ELF^B^A^A     ^@^@^@^@^@^@^@^@^B^@>^@^A^@^@^@��%^@^@^@^@^@@^@^@^@^@^@^@^@8n
^@^@^@^@^@^@^@^@^@@^@8^@^K^@@^@^_^@^^^@^F^@^@^@^D^@^@^@@^@^@^@^@^@^@^@@^@ ^@^@^@^@^@@^@ ^@^@^@^@^@h^B^@^@^@^@^@>
^@^@^@^@^@ �*^@^@^@^@^@ �*^@^@^@^@^@^X^B^@^@^@^@^@^@�^C^@^@^@^@^@^@^@^P^@^@^@^@^@^@^A^@^@^@^F^@^@^@�f
^@^@^@^@^@Ж*^@^@^@^@^@Ж*^@^@^@^@^@�^E^@^@^@^@^@^@�<^A^@^@^@^@^@^@^P^@^@^@^@^@^@^B^@^@^@^F^@^@^@Xc
^@^@^@^@^@X�*^@^@^@^@^@X�*^@^@^@^@^@�^A^@^@^@^@^@^@�^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@R�td^D^@^@^@ c
^@^@^@^@^@ �*^@^@^@^@^@ �*^@^@^@^@^@^X^B^@^@^@^@^@^@�^C^@^@^@^@^@^@^A^@^@^@^@^@^@^@P�td^D^@^@^@^L       ^E^@^@^>
        ^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^Q  ^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@"   ^@^@^R^>
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^V
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^\
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@!
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@*
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@:
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@?
^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@�^B^@^@^Q^@^X^@��*^@^@^@^@^@^X^@^@^@^@^@^@^@�^C^@^@^Q^@^[^@P�+^@^@^>
^@^@0^@^@^@^P^@^@^@^A^@^A^@t
^@^@P^@^@^@^P^@^@^@^A^@^B^@�
^@^@P^@^@^@^@^@^@^@ӯk^E^@^@^E^@S
^@^@^P^@^@^@�lz^M^@^@^F^@^
^@^@^P^@^@^@t)�^H^@^@^D^@h
^@^@^@^@^@^@P&y^K^@^@^C^@�
^@^@^@^@^@^@�(z^G^@^@^B^@�
^@^@^P^@^@^@�(z^G^@^@^G^@�
^@^@^@^@^@^@^G^@^@^@t^@^@^@^H^@^@^@^Z^@^@^@^SH^@^@^A�^H^@^@^@^@^A^@^@^B�^P^@^@^@�^@l^P^B^@^@ �P^A$^@^D�^@^@^@^H>
��S���^WS^_��^H���3�^N^Tl����BxIk�2��^R^UӪ�\k^B`p^RwcD��^N
��^R^@h^E��^U^C�z^H����^X^F�^P?��Pv��ݣk
��_��^��^@^@^@�^@^@^@T^@^@^@^@^@^@^@^@^@^@^@*^@^@^@_^@^@^@@^@^@^@�^@^@^@^@^@^@^@s^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@>
^@^@^@^@^@^@^@E^@^@^@>^@^@^@B^@^@^@Q^@^@^@^@^@^@^@"^@^@^@^@^@^@^@/^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@R^@^@^@H>
^@^@^@^@^@^@^@^@^@^@^@��*^@^@^@^@^@^G^@^@^@�^@^@^@^@^@^@^@^@^@^@^@��*^@^@^@^@^@^G^@^@^@^W^@^@^@^@^@^@^@^@^@^@^@>
^@Smartctl open device: %s failed: %s
^@afterselect,off^@Option -t pending,N (N=%d) must have 0 <= N <= 65535
^@Option -s aam,N must have 0 <= N <= 254
^@-identify^@ioctl[,N], ataioctl[,N], scsiioctl[,N], nvmeioctl[,N]^@protocol^@SET FEATURES [Disable SATA featur>
^@%d^@No information found^@. %u:%u %n^@%u-%u %n^@. 15:8 Must be set to 0x80^@ 50 Capabilities^@ 57-58 Current >
^@APM disable failed: %s
^@Write cache reordering %sable failed: %s
^@ATA IDLE command failed: %s
^@SMART Extended Comprehensive Error Log (GP Log 0x03) not supported

^@Read SMART Extended Self-test Log failed

^@Selective Self-tests/Logging not supported

^@Logical Sectors Written^@Pending Error Count^@naa^@, zeroed^@Zoned Device:     %s
^@Unknown(0x%04x)^@Transport Type:   Parallel, %s
^@ATA/ATAPI-4 X3T13/1153D revision 6^@ATA8-ACS T13/1699-D revision 3c^@ATA8-ACS T13/1699-D revision 3f^@ACS-2 T>
^@SATA NCQ Send and Receive log^@logged_count^@ at LBA = 0x%08x = %u^@Invalid Error Log index = 0x%02x (T13/132>

^@over_limit_count^@0x%02x%s%s (rev %d) ==
^@R_ERR response for host-to-device non-data FIS^@$Id: dev_interface.cpp 5115 2020-11-09 22:07:22Z chrfranke $$>
^@Buffer not set for DATA IN/OUT command^@JMB39x: Restore original sector (%szero filled)
^@JMB39x: Zero filling original data
^@jmb_get_sector_type(data) == 1^@0x%04x:0x%04x^@smartmontools home page: https://www.smartmontools.org/
^@-v 170,raw48,Grown_Failing_Block_Ct -v 171,raw48,Program_Fail_Count -v 172,raw48,Erase_Fail_Count -v 173,raw4>
THIS DRIVE MAY OR MAY NOT BE AFFECTED,
see the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/207951en
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632758^@CC3[5-9A-Z]^@A firmware update for this drive may be >
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/218171en^@ST3(250[68]2|32062|40062|50063|75064)0NS^@-v 9,msec24>
^@Firmware Version:                   %s
                                              [ Read 2240 lines ]
^G Get Help     ^O Write Out    ^W Where Is     ^K Cut Text     ^J Justify      ^C Cur Pos      M-U Undo
^X Exit         ^R Read File    ^\ Replace      ^U Paste Text   ^T To Spell     ^_ Go To Line   M-E Redo
Code: 
root@aeronas:~ # ls -la /usr/local/sbin/smartctl
-r-xr-xr-x  1 root  wheel  685560 Apr 14 23:09 /usr/local/sbin/smartctl
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
WOW!!

that is real news.
Click to expand...
Not for sure. How ever the more I've been digging into this though I think its just Sas drives or scsi in general doesn't talk to smart much more then some basic info.
as I said same HBA and Expander talking to the 3tb HGST sata drives it will give full out-put and it's not a function of BDS vs Linux but rather Sas vs Sata

Code: 
root@aeronas:~ # smartctl -x /dev/da9
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Ultrastar 7K4000
Device Model:     Hitachi HUS724030ALE641
Serial Number:    P8G8KPWR
LU WWN Device Id: 5 000cca 22cc3e56f
Firmware Version: MJ8OA5F0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Apr 18 14:30:04 2022 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled

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

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                (   24) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        (   1) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   016    -    0
  2 Throughput_Performance  P-S---   136   136   054    -    80
  3 Spin_Up_Time            POS---   119   119   024    -    521 (Average 522)
  4 Start_Stop_Count        -O--C-   100   100   000    -    23
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   121   121   020    -    34
  9 Power_On_Hours          -O--C-   099   099   000    -    10741
10 Spin_Retry_Count        PO--C-   100   100   060    -    0
12 Power_Cycle_Count       -O--CK   100   100   000    -    23
192 Power-Off_Retract_Count -O--CK   100   100   000    -    314
193 Load_Cycle_Count        -O--C-   100   100   000    -    314
194 Temperature_Celsius     -O----   181   181   000    -    33 (Min/Max 15/38)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    0
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x04       GPL     R/O      7  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x12       GPL     R/O      1  SATA NCQ Non-Data log
0x20       GPL     R/O      1  Streaming performance log [OBS-8]
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80       GPL     R/W     63  Host vendor specific log
0x81-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xb2       GPL     VS      63  Device vendor specific log
0xc8       GPL     VS     617  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10584         -
# 2  Extended offline    Completed without error       00%     10498         -
# 3  Short offline       Completed without error       00%     10418         -
# 4  Short offline       Completed without error       00%     10178         -
# 5  Extended offline    Completed without error       00%     10091         -
# 6  Short offline       Completed without error       00%     10023         -
# 7  Short offline       Completed without error       00%     10013         -
# 8  Short offline       Completed without error       00%      9846         -
# 9  Extended offline    Completed without error       00%      9758         -
#10  Short offline       Completed without error       00%      9678         -
#11  Short offline       Completed without error       00%      9510         -
#12  Extended offline    Completed without error       00%      9422         -
#13  Short offline       Completed without error       00%      9342         -
#14  Short offline       Completed without error       00%      9176         -
#15  Extended offline    Completed without error       00%      9088         -
#16  Short offline       Completed without error       00%      9043         -
#17  Short offline       Completed without error       00%      9010         -
#18  Short offline       Completed without error       00%      8770         -
#19  Extended offline    Completed without error       00%      8682         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
Device State:                        SMART Off-line Data Collection executing in background (4)
Current Temperature:                    33 Celsius
Power Cycle Min/Max Temperature:     25/35 Celsius
Lifetime    Min/Max Temperature:     15/38 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -40/70 Celsius
Temperature History Size (Index):    128 (90)

Index    Estimated Time   Temperature Celsius
  91    2022-04-18 12:23    33  **************
...    ..(126 skipped).    ..  **************
  90    2022-04-18 14:30    33  **************

SCT Error Recovery Control:
           Read:      1 (0.1 seconds)
          Write:      1 (0.1 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 2) ==
0x01  0x008  4              23  ---  Lifetime Power-On Resets
0x01  0x018  6     41564556434  ---  Logical Sectors Written
0x01  0x020  6       735317484  ---  Number of Write Commands
0x01  0x028  6     42947793217  ---  Logical Sectors Read
0x01  0x030  6       299172214  ---  Number of Read Commands
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           10739  ---  Spindle Motor Power-on Hours
0x03  0x010  4           10739  ---  Head Flying Hours
0x03  0x018  4             314  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4               0  ---  Read Recovery Attempts
0x03  0x030  4               0  ---  Number of Mechanical Start Failures
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              33  ---  Current Temperature
0x05  0x010  1              32  N--  Average Short Term Temperature
0x05  0x018  1              31  N--  Average Long Term Temperature
0x05  0x020  1              38  ---  Highest Temperature
0x05  0x028  1              15  ---  Lowest Temperature
0x05  0x030  1              36  N--  Highest Average Short Term Temperature
0x05  0x038  1              25  N--  Lowest Average Short Term Temperature
0x05  0x040  1              35  N--  Highest Average Long Term Temperature
0x05  0x048  1              25  N--  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              60  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4              31  ---  Number of Hardware Resets
0x06  0x010  4              12  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            0  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
 
H

heromode

Active Member
May 25, 2020
401
229
43
pr1malr8ge said:
Not for sure. How ever the more I've been digging into this though I think its just Sas drives or scsi in general doesn't talk to smart much more then some basic info.
as I said same HBA and Expander talking to the 3tb HGST sata drives it will give full out-put and it's not a function of BDS vs Linux but rather Sas vs Sata
Click to expand...
that id22 data still does exist in the SAS controller PCB. No matter what the WD/HGST guys are saying, the correct place to ask about this would be the smartmontools dev team.

Helium filled drives are among the most significant technological advancement in HDD technology in the past decade, if that parameter exists in the SAS HDD PCB IC ROM, then it will be pulled out of there, one way or the other. I think this discussion will yet lead to positive results. I will certainly contact the smartmontools team once i get my drives and can confirm this.
 
H

heromode

Active Member
May 25, 2020
401
229
43
If this parameter doesn't exist in SAS drives, well, then it doesn't exist in SATA drives either, and the helium_level reading is another scam just like the SMR scam. Either way, i think this discussion is very significant.

If the Helium_Level reading is real, it will be pulled out of the SAS drives one way or the other.
 
P

pr1malr8ge

Member
Nov 27, 2017
63
21
8
42
heromode said:
that id22 data still does exist in the SAS controller PCB. No matter what the WD/HGST guys are saying, the correct place to ask about this would be the smartmontools dev team.

Helium filled drives are among the most significant technological advancement in HDD technology in the past decade, if that parameter exists in the SAS HDD PCB IC ROM, then it will be pulled out of there, one way or the other. I think this discussion will yet lead to positive results. I will certainly contact the smartmontools team once i get my drives and can confirm this.
Click to expand...
Another issue I've ran into is the smart background long..
Long story short when I first got the drives I downed my working truenas to run some tests first as I didn't have space to test any of the drives with the current machine running. I figured since they already went through the infant mortality period and the little bit of smart data availible showing no errors I ran a short test that completed then decided to run a long test. When it came back over a day I decided I didn't want to have my truenas down that long. So I shut down the system put all of the old drives back in the system and then proceeded to plop a single 10tb drive at a time to expand my pool.
With all of that said, after all of the drives have been inserviced I noticed the background long was not completing and this was about a week after the last drive was inserviced.

With that I started a new test and canceled the old test..

I watched the new test progress and then it reset to 0.0% and never showed complete
minus saying it's waiting on an bms interval timer to expire.
I'm wondering if all 6 drives have to scan 1 at a time then when all 6 are done it will then show completed?
how ever more then 1 drive is scanning at a time so that shouldn't be it.
side note; nothing I can do to abort the current one in progress. -X returns
Abort self test failed [unsupported field in scsi command]

Code: 
SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background long   Aborted (by user command)   -   28417                 - [-   -    -]
# 2  Background long   Self test in progress ...   -     NOW                 - [-   -    -]
# 3  Background short  Completed                   -   28250                 - [-   -    -]

Long (extended) Self-test duration: 65535 seconds [1092.2 minutes]
Code: 
Self-test results page  [0x10]
  Parameter code = 1, accumulated power-on hours = 28417
    self-test code: background extended [2]
    self-test result: aborted by SEND DIAGNOSTIC [1]
  Parameter code = 2, accumulated power-on hours = 0
    self-test code: background extended [2]
    self-test result: self test in progress [15]
  Parameter code = 3, accumulated power-on hours = 28250
    self-test code: background short [1]
    self-test result: completed without error [0]

Background scan results page  [0x15]
  Status parameters:
    Accumulated power on minutes: 1708151 [h:m  28469:11]
    Status: background scan enabled, none active (waiting for BMS interval timer to expire)
    Number of background scans performed: 169
    Background medium scan progress: 0.00 %
    Number of background medium scans performed: 169
Here is da3 which shows what the da2 did when it was "scaning"

Code: 
Self-test results page  [0x10]
  Parameter code = 1, accumulated power-on hours = 28395
    self-test code: background extended [2]
    self-test result: aborted by SEND DIAGNOSTIC [1]
  Parameter code = 2, accumulated power-on hours = 0
    self-test code: background extended [2]
    self-test result: self test in progress [15]
  Parameter code = 3, accumulated power-on hours = 28249
    self-test code: background short [1]
    self-test result: completed without error [0]

Background scan results page  [0x15]
  Status parameters:
    Accumulated power on minutes: 1706858 [h:m  28447:38]
    Status: background medium scan is active
    Number of background scans performed: 168
    Background medium scan progress: 93.08 %
    Number of background medium scans performed: 168
 
Last edited:
You must log in or register to reply here.
Top Bottom