Disk info isn't showing after upgrade from TrueNAS Core

[kacper]

I finally switched out the HPE Raid card on our DL80 server for a Dell 0T93GD (12Gbps LSI 3008). TrueNAS Core kept giving me kernel panics while booting, I'd figure it was some kind of kernel driver bug so I upgraded to TrueNAS Scale. However disks in my RAIDZ2 pool don't show any disk info.

I have a separate issue with at least two of the disks (Samsung 750 Evo/500Gb). I don't know if it's the AIC disk shelve (https://www.aicipc.com/en/productdetail/59) or the drives and their firmware that's giving me grief as they do not report any SMART errors. I think I've only observed two of the same disks having issues so maybe they indeed are bad as the other ones seem unaffected.

Two of the drives show up with disk information (sdl and sdg) but that's because I yanked them out of the array while troubleshooting and replaced them via the GUI.

Code:

root@nas[~]# zpool status "ESXi SSD"
  pool: ESXi SSD
 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: resilvered 796K in 00:00:00 with 0 errors on Thu Jan  5 12:54:33 2023
config:

        NAME                                      STATE     READ WRITE CKSUM
        ESXi SSD                                  DEGRADED     0     0     0
          raidz2-0                                DEGRADED     0     0     0
            5e9160d2-6212-4ff7-8dca-bc490eb382b1  FAULTED      0    24     0  too many errors
            sdj2                                  ONLINE       0     0     0
            sds2                                  ONLINE       0     0     0
            sdk2                                  ONLINE       0     0     2
            sdo2                                  ONLINE       0     0     0
            sdf2                                  ONLINE       0     0     0
            sdn2                                  ONLINE       0     0     0
            sdr2                                  ONLINE       0     0     0
          raidz2-1                                ONLINE       0     0     0
            sdh2                                  ONLINE       0     0     0
            sdt2                                  ONLINE       0     0     0
            da58a7fd-eb00-45a4-af37-2ff0a78d70e6  ONLINE       0     0     0
            sdp2                                  ONLINE       0     0     0

errors: No known data errors

 

[sretalla]

sdl is shown as having no scheduled SMART tests, so saying there are no SMART errors on that drive may be based on poor information.

Have you actually looked at the output from smartctl -a /dev/sdl ?

Just to be clear, the status of SMART shown on the screen you shared above for the last 2 tests as SUCCESS does not mean that no errors were found (just that the test was able to complete).

 

[sretalla]

you should also check the cabling/connection for sdk

 

[joeschmuck]

they do not report any SMART errors

If you are just using the SMART report that tht GUI provides, that is just a general overall summary. It's not very reliable to be honest.

The zpool results indicate that you had some write errors, yet the scrub states no errors were present in the data and nothing repaired. This is good news.

Here is what I'd recommend:
1) First of all and the most important: Follow the forum rules and post your system specs. This can and often does help us trace the root cause of a problem down. And it looks like you are virtualizing TrueNAS on ESXi. While that is fine, some folks don't do it correctly so details on how the drives are being passed through or if they are virtualized is very important.
2) The following commands are performed from the Shell:
2a) type zpool scrub ESXi SSD and let the scrub finish.
2b) type zpool status ESXi SSD and post the output. I suspect it will look similar to the one previously posted. If there are no errors at all, you are done. If there is still an error as I suspect, continue to step 3.
3) Reboot the computer.
4) perform step 2b again. If the problem remains, post the output so we can provide further advice.
5) Let's check you hard drive sdl.
5a) First of all, find out the serial number of the drive. The device ID 'sdl' can be assigned to any drive even though typically the drive ID will stay the same so this is why we want the drive serial number so we keep track of things. Type smartctl -a /dev/sdl and post the resulting output. We can then look at the data and find out if the hard drive was having some issue. It could be a data cable issue or something else.
6) If we find out there is no real physical issue, the last command I'd run is zpool clear ESXi SSD and then check the zpool status again.

 

[kacper]

sdl is shown as having no scheduled SMART tests, so saying there are no SMART errors on that drive may be based on poor information.

Have you actually looked at the output from smartctl -a /dev/sdl ?

Just to be clear, the status of SMART shown on the screen you shared above for the last 2 tests as SUCCESS does not mean that no errors were found (just that the test was able to complete).

Code:

root@nas[~]# smartctl -a /dev/sdl
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.79+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 750 EVO 500GB
Serial Number:    S36SNWCH725034X
LU WWN Device Id: 5 002538 d70306d3d
Firmware Version: MAT01B6Q
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jan  5 15:41:59 2023 CET
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:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
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:                (    0) seconds.
Offline data collection
capabilities:                    (0x53) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No 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:        ( 265) 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: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       50891
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       59
177 Wear_Leveling_Count     0x0013   084   084   000    Pre-fail  Always       -       77
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   078   056   000    Old_age   Always       -       22
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   099   099   000    Old_age   Always       -       140
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       47
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       30121448713

SMART Error Log Version: 1
No Errors Logged

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%     50386         -
# 2  Short offline       Completed without error       00%     50381         -

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
  255        0    65535  Read_scanning was completed without error
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.

you should also check the cabling/connection for sdk

I've already checked the cabling to the disk shelf and even swapped the SAS cable for another. There are also other disks (HDDs) in the same JBOD without issues.

If you are just using the SMART report that tht GUI provides, that is just a general overall summary. It's not very reliable to be honest.

The zpool results indicate that you had some write errors, yet the scrub states no errors were present in the data and nothing repaired. This is good news.

Here is what I'd recommend:
1) First of all and the most important: Follow the forum rules and post your system specs. This can and often does help us trace the root cause of a problem down. And it looks like you are virtualizing TrueNAS on ESXi. While that is fine, some folks don't do it correctly so details on how the drives are being passed through or if they are virtualized is very important.
2) The following commands are performed from the Shell:
2a) type zpool scrub ESXi SSD and let the scrub finish.
2b) type zpool status ESXi SSD and post the output. I suspect it will look similar to the one previously posted. If there are no errors at all, you are done. If there is still an error as I suspect, continue to step 3.
3) Reboot the computer.
4) perform step 2b again. If the problem remains, post the output so we can provide further advice.
5) Let's check you hard drive sdl.
5a) First of all, find out the serial number of the drive. The device ID 'sdl' can be assigned to any drive even though typically the drive ID will stay the same so this is why we want the drive serial number so we keep track of things. Type smartctl -a /dev/sdl and post the resulting output. We can then look at the data and find out if the hard drive was having some issue. It could be a data cable issue or something else.
6) If we find out there is no real physical issue, the last command I'd run is zpool clear ESXi SSD and then check the zpool status again.

1) I'm not virtualizing TrueNAS on ESXi i just happen to have named the pool like that cause I use the entire pool for a ESXi datastore.
2) I'll post once the scrub finishes
3) I've rebooted the server multiple times before but I'd give it another shot
5) Se above for smartctl output
6) I've also done that and the errors always return

HPE DL80 g9
Xeon CPU E5-2603 v3 @ 1.60GHz
16 GB ECC RAM
Dell 0T93GD (12Gbps LSI 3008)
Mellanox MT27710 ConnectX-4 Lx

 

[jgreco]

HPE DL80 g9
Xeon CPU E5-2603 v3 @ 1.60GHz
16 GB ECC RAM
Dell 0T93GD (12Gbps LSI 3008)
Mellanox MT27710 ConnectX-4 Lx

With Samsung 750 EVO's? And RAIDZ2 hosting ESXi datastores (i.e. block storage)?

This is a catastrophe looking for a place to go all Chernobyl.

The 750 EVO is one of the crappiest SSD's known to man, it was made with lots of tradeoffs.

Samsung 750 EVO's Ready for Sacrifice: A modern SSD endurance experiment

We are doing our first SSD endurance experiment with two Samsung 750 EVO 120GB SSDs. These are modern planar TLC NAND SSDs.

www.servethehome.com

With write endurance of 100TBW. The use of RAIDZ2 guarantees that you are burning through more endurance than would be consumed with a proper mirror design, 16GB and SCALE is incredibly dubious because this gives you only 8GB ARC on a workload where we normally recommend a minimum of 64GB ARC (i.e. 128GB RAM on SCALE).

Resource - The path to success for block storage

ZFS does two different things very well. One is storage of large sequentially-written files, such as archives, logs, or data files, where the file does not have the middle bits modified after creation. This is optimal for RAIDZ. It's what most...

www.truenas.com

 

[sretalla]

199 CRC_Error_Count 0x003e 099 099 000 Old_age Always - 140

That's 140 CRC errors reported by the drive.

It may not only be cabling, but the connection between the drive and the controller would be implicated by those errors.

For a drive that old, 47 POR recoveries isn't so high, but compared to only 59 power cycles, that means almost all your power cycles are hard power cuts to the drive... maybe not using UPS?

 

[joeschmuck]

Thanks for posting the data. As you can see, quite a few comments and that is actually a good thing. The comments/advice is meant to help you, not upset you.

The SMART data on that drive with the CRC_Errors that i was expecting, check all your other drives, see if they have the same type of things going on. If it's just the one drive, then power down, swap the drive data cable with a different drive. And remember, track the drive serial number, not the drive ident. These CRC_Errors will never go away on the drive, it's permanently recorded. The goal is to ensure they do not increment further. And your zpool errors are likely to not remain cleared unless this is fixed. Sometimes the dta cable just needs to be reseated, or it may need to be replaced. As @sretalla said, it also could be the controller (HBA) causing it. Only do one thing at a time and then monitor for changes. If the problem continues, do something else.

@jgreco has provided you very good advice and he's an ESXi expert (well I think so). Heed his warnings.

Best of luck to you.