Pool keeps degrading

[diogen]

Actually, could this be related?

It would be really strange for WD Gold drives since they support TLER (time limited error recovery)

https://images-eu.ssl-images-amazon.com/images/I/91%2BC6aoAEgS.pdf

And WD's RAID edition drives (what WD Gold is) can't have TLER disabled

Western Digital Support | Western Digital

Find detailed answers to your support questions for your Western Digital products.

support-en.wd.com

Where did your HDDs come from?

EDIT:
Here is a post from 2 years ago describing identical issues

Reddit - The heart of the internet

www.reddit.com

Looks like TLER is disabled in the latest batch of WD Gold drives...

 

[buswedg]

My drives came direct from WD. And they definitely are reverting back to disabled on a cold restart.

 

[buswedg]

Hopefully that fixes it. I see a lot of those dmesg's note timeouts exceeding 30sec. So unresponsive drives seem to be the issue. Lets see.

 

[Visseroth]

I haven't read everything but here's a thought...
Could it be command compatibility issues between a SAS backplane and SATA drives?

I've run into simular issues with my server though not to the same extent, I turned off SMART (yea, not smart I know, no pun intended) and just ran the drives and waited for errors before swapping a drive out then later when it was time to do a drive upgrade changed to SAS drives and things have been smooth since.

Just a thought.

 

[buswedg]

I haven't read everything but here's a thought...
Could it be command compatibility issues between a SAS backplane and SATA drives?

I've run into simular issues with my server though not to the same extent, I turned off SMART (yea, not smart I know, no pun intended) and just ran the drives and waited for errors before swapping a drive out then later when it was time to do a drive upgrade changed to SAS drives and things have been smooth since.

Just a thought.

The drives are connected direct to the expander card. Pretty sure it supports sata drives. And either way, I've tried to direct connect them to the HBA too.

 

[buswedg]

Started a scrub last night and just woke up to this. Joy.

Code:

  pool: storage-pool
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
  scan: scrub in progress since Thu Sep  8 16:18:44 2022
        46.3T scanned at 1.00G/s, 43.3T issued at 959M/s, 47.8T total
        1.09M repaired, 90.64% done, 01:21:34 to go
config:

        NAME                                      STATE     READ WRITE CKSUM
        storage-pool                              ONLINE       0     0     0
          raidz2-0                                ONLINE       0     0     0
            1766c859-9231-4127-ad35-882937845b76  ONLINE       0     0     0
            89b557d9-cc55-463c-9124-3765cff9aaac  ONLINE       0     0     2  (repairing)
            4a07f2eb-442c-430d-9db6-0e5fd80302a9  ONLINE       0     0    32  (repairing)
            c6287e21-49e0-4ffe-86a1-78a33bbbec70  ONLINE       0     0     0
            1c817e68-35de-4b8c-be59-4e98fc1fc9fe  ONLINE       0     0     1  (repairing)
            28dba822-3f63-4e2c-82ad-8e4467bc81a1  ONLINE       0     0     0
        cache
          f5456732-9153-44fb-977b-fe5f1021b959    ONLINE       0     0     0

errors: No known data errors

 

[Arwen]

Let me clarify something.

You used to get DEGRADED or FAULTED drives before, yes?

Now they remain ONLINE, yes?


Having the drives remain ONLINE indicates that the TLER, (Time Limited Error Recovery), is now working. And perhaps you had a few bad blocks that ZFS could not correctly spare out the bad blocks because of the the drives dropping off-line, (aka DEGRADED or FAULTED).

 

[buswedg]

Let me clarify something.

You used to get DEGRADED or FAULTED drives before, yes?

Now they remain ONLINE, yes?


Having the drives remain ONLINE indicates that the TLER, (Time Limited Error Recovery), is now working. And perhaps you had a few bad blocks that ZFS could not correctly spare out the bad blocks because of the the drives dropping off-line, (aka DEGRADED or FAULTED).

ok, fair enough. I'll stick with it then and see if one of the drives drops to DEGRAGED or FAULTED over the weekend without a forced scrub.

 

[buswedg]

Nope, still happening.

 

[buswedg]

Here is another dump of dmesg:

Code:

[271212.477060] mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
[271212.477092] mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
[271212.477110] mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
[271212.477153] sd 0:0:0:0: [sda] tag#4559 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=6s
[271212.477159] sd 0:0:0:0: [sda] tag#4559 CDB: Write(16) 8a 00 00 00 00 05 40 ce 91 40 00 00 00 40 00 00
[271212.477165] blk_update_request: I/O error, dev sda, sector 22562115904 op 0x1:(WRITE) flags 0x700 phys_seg 1 prio class 0
[271212.477175] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=5 type=2 offset=11549655793664 size=32768 flags=180880
[271212.477196] sd 0:0:0:0: [sda] tag#4604 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=6s
[271212.477202] sd 0:0:0:0: [sda] tag#4604 Sense Key : Medium Error [current] [descriptor]
[271212.477206] sd 0:0:0:0: [sda] tag#4604 Add. Sense: Unrecovered read error
[271212.477210] sd 0:0:0:0: [sda] tag#4604 CDB: Read(16) 88 00 00 00 00 04 b9 d5 15 78 00 00 00 10 00 00
[271212.477215] blk_update_request: critical medium error, dev sda, sector 20297618808 op 0x0:(READ) flags 0x700 phys_seg 1 prio class 0
[271212.477220] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=61 type=1 offset=10390233280512 size=8192 flags=180880
[271212.486257] mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
[271212.495453] sd 0:0:0:0: [sda] tag#4544 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=8s
[271212.504559] mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
[271212.504601] sd 0:0:0:0: [sda] tag#4551 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=8s
[271212.515431] sd 0:0:0:0: [sda] tag#4544 CDB: Read(16) 88 00 00 00 00 04 06 cf 58 78 00 00 02 40 00 00
[271212.525687] sd 0:0:0:0: [sda] tag#4551 CDB: Read(16) 88 00 00 00 00 04 06 cf 5a b8 00 00 00 40 00 00
[271212.537757] blk_update_request: I/O error, dev sda, sector 17294121080 op 0x0:(READ) flags 0x700 phys_seg 9 prio class 0
[271212.553729] blk_update_request: I/O error, dev sda, sector 17294121656 op 0x0:(READ) flags 0x700 phys_seg 1 prio class 0
[271212.553740] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=5 type=1 offset=8852442738688 size=32768 flags=180980
[271212.564421] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=5 type=1 offset=8852442443776 size=294912 flags=40080c80
[271212.573573] sd 0:0:0:0: [sda] tag#4555 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=8s
[271212.744993] sd 0:0:0:0: [sda] tag#4555 CDB: Read(16) 88 00 00 00 00 04 06 cf 5a f8 00 00 00 40 00 00
[271212.754936] blk_update_request: I/O error, dev sda, sector 17294121720 op 0x0:(READ) flags 0x700 phys_seg 1 prio class 0
[271212.766712] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=5 type=1 offset=8852442771456 size=32768 flags=180980
[271212.766729] sd 0:0:0:0: [sda] tag#4552 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=6s
[271212.792833] sd 0:0:0:0: [sda] tag#4552 CDB: Write(16) 8a 00 00 00 00 05 3e 7c 16 f0 00 00 00 40 00 00
[271212.792844] blk_update_request: I/O error, dev sda, sector 22523156208 op 0x1:(WRITE) flags 0x700 phys_seg 5 prio class 0
[271212.814618] zio pool=storage-pool vdev=/dev/disk/by-partuuid/1766c859-9231-4127-ad35-882937845b76 error=5 type=2 offset=11529708429312 size=32768 flags=180880

 

[Arwen]

Hmm, all the errors are on a single drive now. Please supply the current output of smartctl -x /dev/sda which might tell us something, (or not...).

I am wondering, (with no real evidence yet), if the other disks had their bad blocks fixed by sparing out. (Now that the timeout is not a problem.) But, perhaps SDA ran out of spares... which we should see in an updated SMART output.

 

[awasb]

@buswedg

By any chance: Is Link(State)PowerManagement enabled in BIOS? If so, turn it off. As well as any other power management feature that could affect onboard SATA or PCI(e) (again: in BIOS).

If You plugged drives back to HBA, You can ignore the onboard SATA power management.

 

[buswedg]

Hmm, all the errors are on a single drive now. Please supply the current output of smartctl -x /dev/sda which might tell us something, (or not...).

I am wondering, (with no real evidence yet), if the other disks had their bad blocks fixed by sparing out. (Now that the timeout is not a problem.) But, perhaps SDA ran out of spares... which we should see in an updated SMART output.

Code:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.131+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Gold
Device Model:     WDC WD161KRYZ-01AGBB0
Serial Number:    3RJ8KEDA
LU WWN Device Id: 5 000cca 2c3e0136a
Firmware Version: 01.01H01
User Capacity:    16,000,900,661,248 bytes [16.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-4 published, ANSI INCITS 529-2018
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Sep 11 09:17:56 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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 249) Self-test routine in progress...
                                        90% of test remaining.
Total time to complete Offline
data collection:                (  101) 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:        (1709) 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   001    -    0
  2 Throughput_Performance  P-S---   149   149   054    -    44
  3 Spin_Up_Time            POS---   084   084   001    -    331 (Average 339)
  4 Start_Stop_Count        -O--C-   100   100   000    -    35
  5 Reallocated_Sector_Ct   PO--CK   100   100   001    -    0
  7 Seek_Error_Rate         PO-R--   100   100   001    -    0
  8 Seek_Time_Performance   P-S---   128   128   020    -    18
  9 Power_On_Hours          -O--C-   100   100   000    -    1619
 10 Spin_Retry_Count        PO--C-   100   100   001    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    34
 22 Helium_Level            PO---K   100   100   025    -    100
192 Power-Off_Retract_Count -O--CK   100   100   000    -    112
193 Load_Cycle_Count        -O--C-   100   100   000    -    112
194 Temperature_Celsius     -O----   063   063   000    -    32 (Min/Max 24/42)
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--   100   100   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  30001  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
0x2f       GPL     -        1  Set Sector Configuration
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xb7           SL  VS       1  Device vendor specific log
0xd8       GPL,SL  VS       1  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)
Device Error Count: 1
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 [0] occurred at disk power-on lifetime: 1610 hours (67 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 43 00 00 00 00 00 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 18 00 04 b9 d5 15 78 40 00  3d+03:21:27.927  READ FPDMA QUEUED
  61 00 40 00 28 00 05 40 ce 91 40 40 00  3d+03:21:21.904  WRITE FPDMA QUEUED
  61 00 40 00 20 00 05 3e 7c 16 f0 40 00  3d+03:21:21.904  WRITE FPDMA QUEUED
  60 00 40 00 10 00 04 06 cf 5a f8 40 00  3d+03:21:19.356  READ FPDMA QUEUED
  60 00 40 00 08 00 04 06 cf 5a b8 40 00  3d+03:21:19.355  READ FPDMA QUEUED

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%      1586         -
# 2  Short offline       Completed without error       00%      1538         -
# 3  Extended offline    Completed without error       00%      1515         -
# 4  Short offline       Completed without error       00%      1418         -
# 5  Short offline       Completed without error       00%      1370         -
# 6  Extended offline    Completed without error       00%      1345         -
# 7  Short offline       Completed without error       00%      1250         -
# 8  Short offline       Completed without error       00%      1223         -
# 9  Short offline       Completed without error       00%      1207         -
#10  Extended offline    Interrupted (host reset)      70%      1180         -
#11  Short offline       Completed without error       00%      1135         -
#12  Short offline       Completed without error       00%      1087         -
#13  Short offline       Completed without error       00%      1041         -
#14  Short offline       Completed without error       00%       972         -
#15  Short offline       Completed without error       00%       923         -
#16  Short offline       Completed without error       00%       875         -
#17  Short offline       Completed without error       00%       840         -
#18  Extended offline    Completed without error       00%       796         -
#19  Short offline       Completed without error       00%       772         -

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:                        DST executing in background (3)
Current Temperature:                    32 Celsius
Power Cycle Min/Max Temperature:     30/34 Celsius
Lifetime    Min/Max Temperature:     24/42 Celsius
Under/Over Temperature Limit Count:   0/0
SMART Status:                        0xc24f (PASSED)
Minimum supported ERC Time Limit:    65 (6.5 seconds)

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 (108)

Index    Estimated Time   Temperature Celsius
 109    2022-09-11 07:10    31  ************
 110    2022-09-11 07:11    32  *************
 ...    ..( 52 skipped).    ..  *************
  35    2022-09-11 08:04    32  *************
  36    2022-09-11 08:05    33  **************
  37    2022-09-11 08:06    32  *************
  38    2022-09-11 08:07    33  **************
  39    2022-09-11 08:08    32  *************
 ...    ..( 38 skipped).    ..  *************
  78    2022-09-11 08:47    32  *************
  79    2022-09-11 08:48    31  ************
 ...    ..( 17 skipped).    ..  ************
  97    2022-09-11 09:06    31  ************
  98    2022-09-11 09:07    32  *************
  99    2022-09-11 09:08    31  ************
 100    2022-09-11 09:09    31  ************
 101    2022-09-11 09:10    32  *************
 ...    ..(  6 skipped).    ..  *************
 108    2022-09-11 09:17    32  *************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4              34  ---  Lifetime Power-On Resets
0x01  0x010  4            1619  ---  Power-on Hours
0x01  0x018  6    178025561910  ---  Logical Sectors Written
0x01  0x020  6       350369289  ---  Number of Write Commands
0x01  0x028  6    321772929964  ---  Logical Sectors Read
0x01  0x030  6       827826270  ---  Number of Read Commands
0x01  0x038  6      5831254550  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4            1595  ---  Spindle Motor Power-on Hours
0x03  0x010  4            1595  ---  Head Flying Hours
0x03  0x018  4             112  ---  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              32  ---  Current Temperature
0x05  0x010  1              31  N--  Average Short Term Temperature
0x05  0x018  1              30  N--  Average Long Term Temperature
0x05  0x020  1              42  ---  Highest Temperature
0x05  0x028  1              24  ---  Lowest Temperature
0x05  0x030  1              39  N--  Highest Average Short Term Temperature
0x05  0x038  1              25  N--  Lowest Average Short Term Temperature
0x05  0x040  1              36  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             172  ---  Number of Hardware Resets
0x06  0x010  4              68  ---  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            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  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

 

[k0d3g3ar]

FWIW, I've had similar situations happen to me before with 18TB drives. And they were WD drives.

Strange thing that solved this for me was to scrap the drives (They were REDs) and replace with the HGST versions. Once I used those "Enterprise" drives, all my problems went away. And I got the issues with RaidZ configurations with HBA Broadcom card interfacing everything. And on a decent server with a ton of memory. I can't speak to WD Gold, but I saw major improvements with HGST drives here. Of course, YMMV.

 

[buswedg]

@buswedg

By any chance: Is Link(State)PowerManagement enabled in BIOS? If so, turn it off. As well as any other power management feature that could affect onboard SATA or PCI(e) (again: in BIOS).

If You plugged drives back to HBA, You can ignore the onboard SATA power management.

I've still got the drives connected to the expander. I can try and move them to the mb headers. I was hoping that the timeout setting was going to fix this, so didn't end up making that switch.

Oh, and I see a setting here in the BIOS:
SATA and RST Configuration --> Aggressive Link Power Management --> Enabled

Should I keep that disabled either way?

 

[buswedg]

FWIW, I've had similar situations happen to me before with 18TB drives. And they were WD drives.

Strange thing that solved this for me was to scrap the drives (They were REDs) and replace with the HGST versions. Once I used those "Enterprise" drives, all my problems went away. And I got the issues with RaidZ configurations with HBA Broadcom card interfacing everything. And on a decent server with a ton of memory. I can't speak to WD Gold, but I saw major improvements with HGST drives here. Of course, YMMV.

Yeh, I'm worried this might be the case. Particularly something funny happening with TrueNAS and this type of large capacity WD drive.

 

[awasb]

I've still got the drives connected to the expander. I can try and move them to the mb headers. I was hoping that the timeout setting was going to fix this, so didn't end up making that switch.

Oh, and I see a setting here in the BIOS:
SATA and RST Configuration --> Aggressive Link Power Management --> Enabled

Should I keep that disabled either way?

Please try to switch. The shorter the "chain" / the less complex your setup, the easier it is to sort out causes of error. AFAICS Your MoBo has enough ports to do it without any additional effort. (Please select Southbridge -> SATA and RST Configuration -> Configure SATA as to "AHCI". Don't - under no circumstance - set it to "RAID", please.)

And yes: please disable all sort of (possibly related) ACPI options and other "advanced" power management (like rapid storage extensions). Just for testing and to be sure, nothing else get's in your way.

 

[Arwen]

@buswedg - Hmm, I don't see in the SMART output what I expected. Unless this is it;

0x0c GPL R/O 30001 Pending Defects log

My skill with SMART output is limited, perhaps someone else can help further.
But, at least the issue now seems to be with just 1 disk. Let us know if any other disk starts throwing errors.

Or, maybe disabling this option will help;

SATA and RST Configuration --> Aggressive Link Power Management --> Enabled

 

[buswedg]

@buswedg - Hmm, I don't see in the SMART output what I expected. Unless this is it;

0x0c GPL R/O 30001 Pending Defects log

My skill with SMART output is limited, perhaps someone else can help further.
But, at least the issue now seems to be with just 1 disk. Let us know if any other disk starts throwing errors.

Or, maybe disabling this option will help;

SATA and RST Configuration --> Aggressive Link Power Management --> Enabled

This is typical behavior of the problem. It is sometimes one disk (never the same disk). Sometimes multiple disks at once. Often both read/write errors. Which, when cleared and scrubbed, lead to subsequent checksum errors. I've not seen sda show read/writes more often than other disks.

And I imagine that BIOS setting will only effect drives connected direct to the mb headers. I've got my boot pool and another drive connect direct to the mb at the moment. But, they aren't part of the array.

I'll take the advice here and disconnect the array later today, then shift all drives direct to the mb. I'll the re-import and see how we go. I think this is either going to be a) some unrecognized incompatibility between TrueNAS SCALE and these types of drives or b) I've been extremely unlucky and got two dud HBAs, and/or two bad set of cables.

I don't think the drives (in terms of hardware issues) are a problem. I've been watching the smart outputs pretty closely. And spent a week doing burn-in with badblocks etc.

FYI -- I did end up making that BIOS setting switch, so that doesn't create an issue while I test out the new setup.

 

[buswedg]

Ok, some other good news. I got in touch with a friend who can lend me a ThinkSystem 430-16i HBA and cables for a while. I'm pretty sure that card should be compatible with TrueNAS.

I'll still try the switch direct to the mb. But if that ends up correcting the problem, this would be another good way to then confirm that my current HBA and/or cables are the problem.

I guess if I see the same issue using a new HBA + cables and don't see the problem when connecting direct to the mb, then at that point, I'll probably end up throwing the server out the window.