New build thats driving my crazy. SSD 870 QVO 8TB

N

neofusion

Contributor
Joined
Apr 2, 2022
Messages
159
McVit said:
i would like to think there is another issue then the Toshiba drives themselves as i get no S.M.A.R.T indications at all...and that the SSD array is also reporting read errors even though i have removed the SSD that had S.M.A.R.T Errors


My troubleshooting so far,

i have replaced a HBA card with another (same model and FW)

i have replaced the 8087 cables that connect the backplane to the HBA

is there a chance that the backplane could be bad?

or is there a potential problem with the HBA (roadcom 9207-8i) and the drives?
Click to expand...
I don't know how you got your drives and what adventures they enjoyed in their earlier life. Perhaps someone dropped the whole pallet and they are all actually broken? We will never know for sure.

My initial guess was the controller, but if you have tried different ones, ideally from different reputable sources while securing a good cooling solution for it, there's reason to start looking elsewhere.

I don't suppose you have a different system you could plop the HBA and drives into just to see if anything changes? It would help you deduce if you have a problem with the backplane, CPU or perhaps RAM.

I skimmed the thread again and can't find a full S.M.A.R.T. report, could you please post a report of one of the drives reporting errors?
It would also be interesting to see the output of: zpool status RaidZ2HDDx12
 
M

McVit

Dabbler
Joined
Sep 20, 2014
Messages
18
neofusion said:
I don't know how you got your drives and what adventures they enjoyed in their earlier life. Perhaps someone dropped the whole pallet and they are all actually broken? We will never know for sure.

My initial guess was the controller, but if you have tried different ones, ideally from different reputable sources while securing a good cooling solution for it, there's reason to start looking elsewhere.

I don't suppose you have a different system you could plop the HBA and drives into just to see if anything changes? It would help you deduce if you have a problem with the backplane, CPU or perhaps RAM.

I skimmed the thread again and can't find a full S.M.A.R.T. report, could you please post a report of one of the drives reporting errors?
It would also be interesting to see the output of: zpool status RaidZ2HDDx12
Click to expand...

The drives are brand new.

I thought the HBA card was the culprit aswell...and still could be but i think there i a low chance of 2 in a row being bad.

I have a few HBA cards(E) with the same controller on it i could try.

its worth a try, i can change to an older chassis with slower backplane (SATA 3Gbps) just to see if the problem persists

Below is 1 / 12 drives that are repporting Errors

Code:
root@truenas[/home/admin]# smartctl -a /dev/sdb    
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.107+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba MG09ACA... Enterprise Capacity HDD
Device Model:     TOSHIBA MG09ACA18TE
Serial Number:    Z2H0A51LFJDH
LU WWN Device Id: 5 000039 c38d10385
Firmware Version: 0105
User Capacity:    18,000,207,937,536 bytes [18.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 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 23 22:06:33 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: 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:                (  120) 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:        (1504) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       8575
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       36
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       559
 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       36
 23 Helium_Condition_Lower  0x0023   100   100   075    Pre-fail  Always       -       0
 24 Helium_Condition_Upper  0x0023   100   100   075    Pre-fail  Always       -       0
 27 MAMR_Health_Monitor     0x0023   100   100   030    Pre-fail  Always       -       199514
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       35
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       47
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       31 (Min/Max 18/45)
196 Reallocated_Event_Count 0x0033   100   100   010    Pre-fail  Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       2176
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       134348802
222 Loaded_Hours            0x0032   099   099   000    Old_age   Always       -       540
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       612
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       18518740887
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       6890963785

SMART Error Log Version: 1
ATA Error Count: 2176 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 2176 occurred at disk power-on lifetime: 510 hours (21 days + 6 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 3f db 53 40  Error: ICRC, ABRT at LBA = 0x0053db3f = 5495615

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 a0 00 a0 d9 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 70 00 30 d8 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 a8 08 88 d7 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 70 00 18 d7 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 50 00 c8 d6 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED

Error 2175 occurred at disk power-on lifetime: 409 hours (17 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 08 3f dc 7e 40  Error: ICRC, ABRT at LBA = 0x007edc3f = 8313919

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 10 40 dc 7e 40 00   9d+01:27:27.316  READ FPDMA QUEUED
  60 60 08 e0 d7 7e 40 00   9d+01:27:27.312  READ FPDMA QUEUED
  60 f8 00 e8 cf 7e 40 00   9d+01:27:27.312  READ FPDMA QUEUED
  60 68 10 78 c8 7e 40 00   9d+01:27:27.305  READ FPDMA QUEUED
  60 f8 08 78 c0 7e 40 00   9d+01:27:27.305  READ FPDMA QUEUED

Error 2174 occurred at disk power-on lifetime: 370 hours (15 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 ff a3 2f 40  Error: ICRC, ABRT at LBA = 0x002fa3ff = 3122175

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 18 08 00 a4 2f 40 00   7d+09:54:22.423  READ FPDMA QUEUED
  60 c8 00 38 9c 2f 40 00   7d+09:54:22.422  READ FPDMA QUEUED
  60 18 00 20 9c 2f 40 00   7d+09:54:22.422  READ FPDMA QUEUED
  60 20 00 00 9c 2f 40 00   7d+09:54:22.421  READ FPDMA QUEUED
  60 f0 00 10 99 2f 40 00   7d+09:54:22.420  READ FPDMA QUEUED

Error 2173 occurred at disk power-on lifetime: 369 hours (15 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 5f 7d eb 40  Error: ICRC, ABRT at LBA = 0x00eb7d5f = 15433055

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 18 08 60 7d eb 40 00   7d+09:47:06.903  READ FPDMA QUEUED
  60 50 00 10 7d eb 40 00   7d+09:47:06.903  READ FPDMA QUEUED
  60 50 00 b8 76 eb 40 00   7d+09:47:06.901  READ FPDMA QUEUED
  60 18 00 98 76 eb 40 00   7d+09:47:06.900  READ FPDMA QUEUED
  60 e8 00 b0 71 eb 40 00   7d+09:47:06.898  READ FPDMA QUEUED

Error 2172 occurred at disk power-on lifetime: 369 hours (15 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 6f 8b 4a 40  Error: ICRC, ABRT at LBA = 0x004a8b6f = 4885359

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 68 00 08 8a 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 f8 08 10 88 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 70 00 a0 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 18 08 88 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 18 00 68 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       403         -

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.



Code:
zpool status RaidZ2HDDx12

root@truenas[/home/admin]# zpool status RaidZ2HDDx12
  pool: RaidZ2HDDx12
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: scrub canceled on Fri Jul 21 21:02:33 2023
config:

        NAME                                      STATE     READ WRITE CKSUM
        RaidZ2HDDx12                              DEGRADED     0     0     0
          raidz2-0                                DEGRADED   402     0     0
            ebe8c2eb-2533-4a13-8aaa-3734fb5b1d8d  DEGRADED    32     0     0  too many errors
            a0a3f34d-d4d9-4110-a1aa-2315c0e4002f  ONLINE       0     0     0
            340a9673-ede1-453a-bb46-2ce484c6aa36  DEGRADED    72     0     0  too many errors
            5a48a761-b60a-40ff-9795-f7e9bfa76f47  ONLINE       0     0     0
            95f7aa5a-dd0c-4984-9e58-a7231cf8b929  ONLINE       6     0     0
            bae59d59-7c85-415d-a57c-50d736bf5f4f  ONLINE       0     0     0
            f1562200-2055-40af-902b-3e983b9a618a  DEGRADED   270     0     0  too many errors
            a359990b-a6a4-4165-b455-98712e5c215b  FAULTED    111     0     0  too many errors
            110cd40e-a2c2-4c5c-91f4-a4334717b57a  DEGRADED    18     0     0  too many errors
            9b2c5579-853b-4f0d-8394-2507fcee01b4  FAULTED     23     0     0  too many errors
            08e8bf74-f131-467b-8803-db9e27b277e0  ONLINE       0     0     0
            39845aed-cb63-4205-a306-f3ff0fa3138a  DEGRADED    16     0     0  too many errors

errors: No known data errors
 
N

neofusion

Contributor
Joined
Apr 2, 2022
Messages
159
McVit said:
The drives are brand new.

I thought the HBA card was the culprit aswell...and still could be but i think there i a low chance of 2 in a row being bad.

I have a few HBA cards(E) with the same controller on it i could try.

its worth a try, i can change to an older chassis with slower backplane (SATA 3Gbps) just to see if the problem persists

Below is 1 / 12 drives that are repporting Errors

Code:
root@truenas[/home/admin]# smartctl -a /dev/sdb 
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.107+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba MG09ACA... Enterprise Capacity HDD
Device Model:     TOSHIBA MG09ACA18TE
Serial Number:    Z2H0A51LFJDH
LU WWN Device Id: 5 000039 c38d10385
Firmware Version: 0105
User Capacity:    18,000,207,937,536 bytes [18.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 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 23 22:06:33 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: 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:                (  120) 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:        (1504) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       8575
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       36
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       559
 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       36
 23 Helium_Condition_Lower  0x0023   100   100   075    Pre-fail  Always       -       0
 24 Helium_Condition_Upper  0x0023   100   100   075    Pre-fail  Always       -       0
 27 MAMR_Health_Monitor     0x0023   100   100   030    Pre-fail  Always       -       199514
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       35
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       47
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       31 (Min/Max 18/45)
196 Reallocated_Event_Count 0x0033   100   100   010    Pre-fail  Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       2176
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       134348802
222 Loaded_Hours            0x0032   099   099   000    Old_age   Always       -       540
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       612
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       18518740887
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       6890963785

SMART Error Log Version: 1
ATA Error Count: 2176 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 2176 occurred at disk power-on lifetime: 510 hours (21 days + 6 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 3f db 53 40  Error: ICRC, ABRT at LBA = 0x0053db3f = 5495615

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 a0 00 a0 d9 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 70 00 30 d8 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 a8 08 88 d7 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 70 00 18 d7 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED
  60 50 00 c8 d6 53 40 00  13d+06:32:21.688  READ FPDMA QUEUED

Error 2175 occurred at disk power-on lifetime: 409 hours (17 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 08 3f dc 7e 40  Error: ICRC, ABRT at LBA = 0x007edc3f = 8313919

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 f8 10 40 dc 7e 40 00   9d+01:27:27.316  READ FPDMA QUEUED
  60 60 08 e0 d7 7e 40 00   9d+01:27:27.312  READ FPDMA QUEUED
  60 f8 00 e8 cf 7e 40 00   9d+01:27:27.312  READ FPDMA QUEUED
  60 68 10 78 c8 7e 40 00   9d+01:27:27.305  READ FPDMA QUEUED
  60 f8 08 78 c0 7e 40 00   9d+01:27:27.305  READ FPDMA QUEUED

Error 2174 occurred at disk power-on lifetime: 370 hours (15 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 ff a3 2f 40  Error: ICRC, ABRT at LBA = 0x002fa3ff = 3122175

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 18 08 00 a4 2f 40 00   7d+09:54:22.423  READ FPDMA QUEUED
  60 c8 00 38 9c 2f 40 00   7d+09:54:22.422  READ FPDMA QUEUED
  60 18 00 20 9c 2f 40 00   7d+09:54:22.422  READ FPDMA QUEUED
  60 20 00 00 9c 2f 40 00   7d+09:54:22.421  READ FPDMA QUEUED
  60 f0 00 10 99 2f 40 00   7d+09:54:22.420  READ FPDMA QUEUED

Error 2173 occurred at disk power-on lifetime: 369 hours (15 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 5f 7d eb 40  Error: ICRC, ABRT at LBA = 0x00eb7d5f = 15433055

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 18 08 60 7d eb 40 00   7d+09:47:06.903  READ FPDMA QUEUED
  60 50 00 10 7d eb 40 00   7d+09:47:06.903  READ FPDMA QUEUED
  60 50 00 b8 76 eb 40 00   7d+09:47:06.901  READ FPDMA QUEUED
  60 18 00 98 76 eb 40 00   7d+09:47:06.900  READ FPDMA QUEUED
  60 e8 00 b0 71 eb 40 00   7d+09:47:06.898  READ FPDMA QUEUED

Error 2172 occurred at disk power-on lifetime: 369 hours (15 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 6f 8b 4a 40  Error: ICRC, ABRT at LBA = 0x004a8b6f = 4885359

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 68 00 08 8a 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 f8 08 10 88 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 70 00 a0 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 18 08 88 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED
  60 18 00 68 87 4a 40 00   7d+09:39:05.309  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       403         -

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.



Code:
zpool status RaidZ2HDDx12

root@truenas[/home/admin]# zpool status RaidZ2HDDx12
  pool: RaidZ2HDDx12
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: scrub canceled on Fri Jul 21 21:02:33 2023
config:

        NAME                                      STATE     READ WRITE CKSUM
        RaidZ2HDDx12                              DEGRADED     0     0     0
          raidz2-0                                DEGRADED   402     0     0
            ebe8c2eb-2533-4a13-8aaa-3734fb5b1d8d  DEGRADED    32     0     0  too many errors
            a0a3f34d-d4d9-4110-a1aa-2315c0e4002f  ONLINE       0     0     0
            340a9673-ede1-453a-bb46-2ce484c6aa36  DEGRADED    72     0     0  too many errors
            5a48a761-b60a-40ff-9795-f7e9bfa76f47  ONLINE       0     0     0
            95f7aa5a-dd0c-4984-9e58-a7231cf8b929  ONLINE       6     0     0
            bae59d59-7c85-415d-a57c-50d736bf5f4f  ONLINE       0     0     0
            f1562200-2055-40af-902b-3e983b9a618a  DEGRADED   270     0     0  too many errors
            a359990b-a6a4-4165-b455-98712e5c215b  FAULTED    111     0     0  too many errors
            110cd40e-a2c2-4c5c-91f4-a4334717b57a  DEGRADED    18     0     0  too many errors
            9b2c5579-853b-4f0d-8394-2507fcee01b4  FAULTED     23     0     0  too many errors
            08e8bf74-f131-467b-8803-db9e27b277e0  ONLINE       0     0     0
            39845aed-cb63-4205-a306-f3ff0fa3138a  DEGRADED    16     0     0  too many errors

errors: No known data errors
Click to expand...
Thank you.

I don't have a lot of experience to draw on but the one time I saw CRC errors the cause ended a faulty ports on the HBA controller.
Since you have tried a different HBA and different cables already - bypassing the backplane entirely or with a different backplane seems like a sensible next troubleshooting step.
 
A

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
McVit said:
Hello guys!

This is my setup:

  • Supermicro 846 Chassi BPN-SAS2-846EL1
  • Asus x670E Creator
  • Amd Ryzen 7900
  • 4x32GB kingston 5600mhz cl40
  • 870QVO, x8, MZ-77Q8T0BW, RaidZ1
  • Toshiba 512MB 18TB, x12, MG09ACA18TE, RaidZ2
  • Broadcom 9207-8i SAS2308 6G SATA SAS HBA PCIe x8 3.0 LSI RAID IT Dell 0VGXKD
  • Onboard 10gbps

i finally bit the bullet and built a large NAS. everything has been going great until i just about finished the data migration from my old storage solution:

View attachment 68192

this is the SSD raid and this is the second time i install this setup and get the same result, lots of read errors (and only read errors)
I thought maybe it was the raid controller last time so i replaced it with a new one (same model thought)

Is there a known issue with Samsung 870QVO and ZFS?
Iam at a loss here, if there is this many read errors, can i trust the data that has been migrated?
what can i do to troubleshoot?
Click to expand...
When AMD 7950X came out I almost made the plunge to replace my desktop, however there was little or no reviews with fully populated DIMM's and QVL from motherboard vendors and even advices from RAM manufacturers suggested there isn't really anything available that will work reliably.

So my guess is on CPU/RAM interaction.
 
M

McVit

Dabbler
Joined
Sep 20, 2014
Messages
18
Apollo said:
When AMD 7950X came out I almost made the plunge to replace my desktop, however there was little or no reviews with fully populated DIMM's and QVL from motherboard vendors and even advices from RAM manufacturers suggested there isn't really anything available that will work reliably.

So my guess is on CPU/RAM interaction.
Click to expand...

its a possible, but how does one verify?
would a memtest catch these kind of errors?
 
M

McVit

Dabbler
Joined
Sep 20, 2014
Messages
18
systract said:
It seems that Toshiba has problem with TrueNAS especially if you have a lot of them in one machine.

Good thing is Toshiba has really good RMA policy, they just refund you so you could buy other brands.

On the other hand, Samsung just repair the fault drive then send it back to you:mad:.
Click to expand...

As you have a very similar setup to mine, may i ask what RAM you are using? and maybe what settings you are at?
 
S

systract

Dabbler
Joined
Oct 7, 2022
Messages
32
McVit said:
As you have a very similar setup to mine, may i ask what RAM you are using? and maybe what settings you are at?
Click to expand...
Memory: 4 X Crucial CT32G48C40U5

Storage:
pool1: 4 Samsung 980p RAIDZ2
pool2: 8 HDD RAIDZ2

LSI Broadcom SAS 9300-8i 8-Port 12Gb/s SATA+SAS PCI-Express 3.0 Low Profile Host Bus Adapter

Also here is memory support list:

ProArt X670E-CREATOR WIFI｜Motherboards｜ASUS Global

Built for creators, ProArt X670E-Creator WiFi features 16+2 power stages (70A), PCIe® 5.0, DDR5 support, USB4®, 10 Gb & 2.5 Gb LAN, WiFi 6E and four M.2 slots
www.asus.com www.asus.com
 
Last edited:
A

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
McVit said:
its a possible, but how does one verify?
would a memtest catch these kind of errors?
Click to expand...
Memtest would normally catch such memory related errors, but from what I understand from the 7900 series (which I have no practical experience with) is that the motherboard does run some level of training with the memory controller under certain conditions and I would think timing/voltage levels would be somewhat different each time training occurs.
If memory controller settings are different from one run to the next, you can't really trust the platform to be error free unless you are able to validate enough test runs with Memtest to build a history and gain a certain level of confidance, but this is going to take a fair amount of time.
 
M

McVit

Dabbler
Joined
Sep 20, 2014
Messages
18
Update Time!

went through this list this evening:

#1Update BIOS, was on realease from factory...last bos releases "Improve memory compatibility"
booted up truenas and ran a ZFS clear pool. Did another Scrub and the errors kept piling up again.

#2 Hard set RAM to 4800Mhz
booted up truenas and ran a ZFS clear pool. Did another Scrub and the errors kept piling up again.

#3 Remove 2 out of 4 dimms
booted up truenas and ran a ZFS clear pool. Did another Scrub and the errors kept piling up again.

#5 switched out the 2 dimms for the other pair, Scrub is running and still no errors (only run for 20mins or so) but still a lot better then before.

will update with results in the morning after a full run
 
A

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
McVit said:
#5 switched out the 2 dimms for the other pair, Scrub is running and still no errors (only run for 20mins or so) but still a lot better then before.

will update with results in the morning after a full run
Click to expand...
Are you saying there are no errors being reported?

You should have a look at the specs for the processor on AMD website:
https://www.amd.com/en/product/12746

Under the "Max Memory Speed" section you have:
Max Memory Speed

2x1R
DDR5-5200

2x2R
DDR5-5200

4x1R
DDR5-3600

4x2R
DDR5-3600
Click to expand...

As per my previous post, you shouldn't try to run you memory above DDR5-3600 when all DIMM's are populated, which means not running EXPO memory settings.
 
S

systract

Dabbler
Joined
Oct 7, 2022
Messages
32
Apollo said:
Are you saying there are no errors being reported?

You should have a look at the specs for the processor on AMD website:
https://www.amd.com/en/product/12746

Under the "Max Memory Speed" section you have:


As per my previous post, you shouldn't try to run you memory above DDR5-3600 when all DIMM's are populated, which means not running EXPO memory settings.
Click to expand...

I am running on 4 X Crucial 32GB DDR5-4800, never had any memory problem.

In my understanding the board can install higher speed ram, but the actual speed is limited by Max Memory Speed.

​

 
M

McVit

Dabbler
Joined
Sep 20, 2014
Messages
18
Apollo said:
Are you saying there are no errors being reported?

You should have a look at the specs for the processor on AMD website:
https://www.amd.com/en/product/12746

Under the "Max Memory Speed" section you have:


As per my previous post, you shouldn't try to run you memory above DDR5-3600 when all DIMM's are populated, which means not running EXPO memory settings.
Click to expand...
Yes it would seem that one pair of dimms are bad, or one stick of the pair is bad.
Right now with only 2 sticks of RAM in the system i no longer have read errors!
 
A

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
You should check the sticks that give you trouble individually to make sure there is really a bad stick. Run the test at stock speed if possible.
 
You must log in or register to reply here.

Similar threads

Z0eff
First build: All flash 8x8TB RAIDz2 (Samsung 870 QVO 8TB), any red flags?
2
Replies
27
Views
3K
Z0eff
Z0eff
S
New SSD drives not detected in my new supermicro truenas system
Replies
7
Views
3K
NugentS
NugentS
S
SAS Expanders, QNAP Hardware will it TrueNAS? Is this crazy talk? HELP!!
Replies
0
Views
1K
swezey
S
J
Critique my proposed build for a quiet 1U all-SSD rack mount NAS
Replies
0
Views
1K
jb002
J
A
Another X11SCH Low Power build ...or?
Replies
2
Views
1K
a1x
A
Top