CAM status: SCSI Status Error during resilvering and checksum errors

napalmd

Dabbler
Joined
Aug 24, 2017
Messages
11
Hello.
I have this server running 24/7 for about 6 years now:

FreeNAS-11.1-U7
XEON E3-1220 V3
SUPERMICRO SERVER 826E16
Motherboard MBD-X10SLM
16GB Ram
LSI SAS3108

Started with 7x4TB in raidz2
then added 2x8tb mirror to the pool
and then added more 2x8tb to the same pool
I also have a 500gb cache drive

2 weeks ago I got an email about a failing 4tb hard drive I confirmed it with smart and ordered replacement. Then I proceeded to replace the drive according to instructions I put bad drive offline, shutdown the server and replaced the drive. I took the opportunity to clean the dust of the drives took them of their slots and reinsert them.
After I power up the system I go to the gui and replaced the drive and it started resilvering. all good so far but then an 8tb drive started giving this errors and UDMA_CRC_Error_Count started increasing.
It looks like bad connection. but I was afraid to shutdown during resilver so I let it run. I just want to know the best course of action right now because zpool status says to Wait for the resilver to complete.:

Code:
  pool: storage5                                                                                                                   
 state: DEGRADED                                                                                                                   
status: One or more devices is currently being resilvered.  The pool will                                                           
        continue to function, possibly in a degraded state.                                                                         
action: Wait for the resilver to complete.                                                                                         
  scan: resilver in progress since Mon Jan 22 15:20:00 2024                                                                         
        21.1T scanned at 232M/s, 19.9T issued at 218M/s, 36.4T total                                                               
        1.71T resilvered, 54.73% done, 0 days 21:58:30 to go                                                                       
config:                                                                                                                             
                                                                                                                                    
        NAME                                            STATE     READ WRITE CKSUM                                                 
        storage5                                        DEGRADED     0     0     0                                                 
          raidz2-0                                      ONLINE       0     0     0                                                 
            gptid/75123f50-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/7627289d-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/7778ae43-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/78bb002c-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/79e99291-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/715d621c-b939-11ee-9c62-0cc47ac6de45  ONLINE       0     0     0  (resilvering)                                   
            gptid/7c3546e8-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0                                                 
          mirror-1                                      ONLINE       0     0     0                                                 
            gptid/3b535bc9-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0                                                 
            gptid/3bf74286-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0                                                 
          mirror-2                                      DEGRADED     0     0     0                                                 
            gptid/f6ada8d8-38c0-11ec-b8d2-0cc47ac6de45  DEGRADED     0     0   156  too many errors  (resilvering)                 
            gptid/f749f2d1-38c0-11ec-b8d2-0cc47ac6de45  ONLINE       0     0     0                                                 
        cache                                                                                                                       
          gptid/24313233-3fca-11eb-9a9d-0cc47ac6de45    ONLINE       0     0     0                                                 
                                                                                                                                    
errors: No known data errors   


Code:
Jan 22 16:45:16 freenas (da3:mrsas0:0:3:0): WRITE(10). CDB: 2a 00 00 40 01 d8 00 00 08 00
Jan 22 16:45:16 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 16:45:16 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 16:50:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 231 to 1034
Jan 22 16:50:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 231 to 1035
Jan 22 16:52:14 freenas ZFS: vdev state changed, pool_guid=17226110643858325054 vdev_guid=15474057923386265386
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 47 ad 6d 88 00 01 00 00
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 47 ad 6f 88 00 01 00 00
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:09:02 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:14:33 freenas (da3:mrsas0:0:3:0): READ(16). CDB: 88 00 00 00 00 03 87 7a 34 30 00 00 01 00 00 00
Jan 22 17:14:33 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:14:33 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 e7 ce f0 f0 00 01 00 00
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 e7 ce f1 f0 00 01 00 00
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:16:47 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:17:37 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 e0 05 4d e8 00 01 00 00
Jan 22 17:17:37 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:17:37 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:17:38 freenas (da3:mrsas0:0:3:0): WRITE(10). CDB: 2a 00 00 40 01 d8 00 00 08 00
Jan 22 17:17:38 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:17:38 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:20:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 1034 to 6565
Jan 22 17:20:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 1035 to 6565
Jan 22 17:20:38 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 d7 cc bd 48 00 01 00 00
Jan 22 17:20:38 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:20:38 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:21:05 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 a8 1f 4a e8 00 01 00 00
Jan 22 17:21:05 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:21:05 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:02 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 17 fc 08 e0 00 01 00 00
Jan 22 17:26:02 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:02 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:03 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 17 fc 07 e0 00 01 00 00
Jan 22 17:26:03 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:03 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:08 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 2a cc 91 f0 00 00 c8 00
Jan 22 17:26:08 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:08 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 52 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 53 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 50 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 4f 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 4e 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 51 60 00 01 00 00
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:44 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:26:45 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f 81 54 60 00 01 00 00
Jan 22 17:26:45 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:26:45 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:27:36 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 08 1a 0b 88 00 01 00 00
Jan 22 17:27:36 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:27:36 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:31:02 freenas (da3:mrsas0:0:3:0): READ(16). CDB: 88 00 00 00 00 03 97 ac 4a 98 00 00 01 00 00 00
Jan 22 17:31:02 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:31:02 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:39:11 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 17 e1 c2 e0 00 01 00 00
Jan 22 17:39:11 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:39:11 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 17 f7 25 e0 00 01 00 00
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 17 f7 2c e0 00 01 00 00
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:39:33 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:44:31 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 47 f9 72 c8 00 01 00 00
Jan 22 17:44:31 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:44:31 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:50:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 6565 to 14959
Jan 22 17:50:09 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 6565 to 14959
Jan 22 17:50:27 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f bc 42 98 00 01 00 00
Jan 22 17:50:27 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:50:27 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:55:42 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 77 c6 66 90 00 01 00 00
Jan 22 17:55:42 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:55:42 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:59:28 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f e6 01 10 00 01 00 00
Jan 22 17:59:28 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:59:28 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 17:59:29 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 6f e6 08 10 00 01 00 00
Jan 22 17:59:29 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 17:59:29 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 18:00:09 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 78 18 a5 60 00 01 00 00
Jan 22 18:00:09 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 18:00:09 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 18:00:57 freenas (da3:mrsas0:0:3:0): READ(10). CDB: 28 00 71 76 aa b0 00 00 c8 00
Jan 22 18:00:57 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 18:00:57 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 18:17:10 freenas (da3:mrsas0:0:3:0): WRITE(16). CDB: 8a 00 00 00 00 02 4a 2d ba d0 00 00 01 00 00 00
Jan 22 18:17:10 freenas (da3:mrsas0:0:3:0): CAM status: SCSI Status Error
Jan 22 18:17:10 freenas (da3:mrsas0:0:3:0): SCSI status: OK
Jan 22 18:20:08 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 14959 to 18699
Jan 22 18:20:08 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 14959 to 18699
Jan 22 18:50:08 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 18699 to 18701
Jan 22 18:50:08 freenas smartd[6232]: Device: /dev/da3 [SAT], ATA error count increased from 18699 to 18701


Code:
root@freenas:~ # smartctl -a /dev/da3
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD80EDAZ-11TA3A0
Serial Number:    VGK2KREG
LU WWN Device Id: 5 000cca 0beeb71c9
Firmware Version: 81.00A81
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
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:    Tue Jan 23 17:59:18 2024 WET
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:                (   87) 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:        ( 909) 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   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0004   128   128   054    Old_age   Offline      -       108
  3 Spin_Up_Time            0x0007   159   159   024    Pre-fail  Always       -       514 (Average 507)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       28
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000a   100   100   067    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0004   128   128   020    Old_age   Offline      -       18
  9 Power_On_Hours          0x0012   098   098   000    Old_age   Always       -       19670
 10 Spin_Retry_Count        0x0012   100   100   060    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       28
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       833
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       833
194 Temperature_Celsius     0x0002   180   180   000    Old_age   Always       -       36 (Min/Max 23/49)
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       -       22370

SMART Error Log Version: 1
ATA Error Count: 22370 (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 22370 occurred at disk power-on lifetime: 19670 hours (819 days + 14 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 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  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 00 00 d0 4a 23 40 00   1d+02:29:30.233  READ FPDMA QUEUED
  60 00 00 d0 49 23 40 00   1d+02:29:30.232  READ FPDMA QUEUED
  60 00 08 d0 48 23 40 00   1d+02:29:30.228  READ FPDMA QUEUED
  60 00 00 d0 47 23 40 00   1d+02:29:30.223  READ FPDMA QUEUED
  60 00 10 d0 40 23 40 00   1d+02:29:30.218  READ FPDMA QUEUED

Error 22369 occurred at disk power-on lifetime: 19670 hours (819 days + 14 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 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  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 00 10 a0 09 13 40 00   1d+02:19:44.074  READ FPDMA QUEUED
  60 00 08 a0 08 13 40 00   1d+02:19:44.059  READ FPDMA QUEUED
  60 00 00 a0 07 13 40 00   1d+02:19:44.059  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   1d+02:19:44.055  READ LOG EXT
  2f 00 01 10 00 00 00 00   1d+02:19:44.055  READ LOG EXT

Error 22368 occurred at disk power-on lifetime: 19670 hours (819 days + 14 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 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  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 00 00 a0 07 13 40 00   1d+02:19:44.055  READ FPDMA QUEUED
  60 00 10 a0 09 13 40 00   1d+02:19:44.037  READ FPDMA QUEUED
  60 00 08 a0 08 13 40 00   1d+02:19:44.037  READ FPDMA QUEUED
  60 10 00 28 68 51 40 00   1d+02:19:43.692  READ FPDMA QUEUED
  60 10 00 98 66 4f 40 00   1d+02:19:43.405  READ FPDMA QUEUED

Error 22367 occurred at disk power-on lifetime: 19670 hours (819 days + 14 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 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  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 00 08 e0 ee 40 40 00   1d+02:14:47.358  READ FPDMA QUEUED
  60 00 00 e0 ed 40 40 00   1d+02:14:47.357  READ FPDMA QUEUED
  60 00 08 e0 ec 40 40 00   1d+02:14:47.357  READ FPDMA QUEUED
  60 00 00 e0 eb 40 40 00   1d+02:14:47.357  READ FPDMA QUEUED
  60 00 08 e0 ea 40 40 00   1d+02:14:47.356  READ FPDMA QUEUED

Error 22366 occurred at disk power-on lifetime: 19670 hours (819 days + 14 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 41 00 00 00 00 00  Error: ICRC, ABRT at LBA = 0x00000000 = 0

  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 00 08 28 1a 40 40 00   1d+02:14:46.398  READ FPDMA QUEUED
  60 00 00 28 19 40 40 00   1d+02:14:46.397  READ FPDMA QUEUED
  60 00 10 28 18 40 40 00   1d+02:14:46.379  READ FPDMA QUEUED
  60 00 08 28 17 40 40 00   1d+02:14:46.378  READ FPDMA QUEUED
  60 e0 00 48 16 40 40 00   1d+02:14:46.378  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     19649         -
# 2  Short offline       Completed without error       00%     19644         -
# 3  Short offline       Completed without error       00%     19481         -
# 4  Short offline       Completed without error       00%     19313         -
# 5  Short offline       Completed without error       00%     19145         -
# 6  Short offline       Completed without error       00%     18977         -
# 7  Short offline       Completed without error       00%     18809         -
# 8  Short offline       Completed without error       00%     18641         -
# 9  Extended offline    Completed without error       00%     18512         -
#10  Short offline       Completed without error       00%     18473         -
#11  Short offline       Completed without error       00%     18305         -
#12  Short offline       Completed without error       00%     18137         -
#13  Short offline       Completed without error       00%     17969         -
#14  Short offline       Completed without error       00%     17801         -
#15  Short offline       Completed without error       00%     17633         -
#16  Short offline       Completed without error       00%     17464         -
#17  Short offline       Completed without error       00%     17296         -
#18  Short offline       Completed without error       00%     17128         -
#19  Extended offline    Completed without error       00%     16999         -
#20  Short offline       Completed without error       00%     16960         -
#21  Short offline       Completed without error       00%     16792         -

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.


I did a short smart test but I didn't do a long because it might slow the resilver a lot.
thanks.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
chksum errors are often (but not always) the result of a cabling issue which you may have knocked or its worn out.
 

napalmd

Dabbler
Joined
Aug 24, 2017
Messages
11
This is a rack server and I just cleaned from the front panel, I didn't open top cover so the only explanation is that some dust stayed in the sata connector?!
The resilver just finished. Now what should I do? Power off system, pull out the drive examine connectors and clen, reinsert drive, power on system.
And then should I make a smart long test or replace drive to resilver mirror?
Code:
  pool: storage5
 state: DEGRADED
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: http://illumos.org/msg/ZFS-8000-9P
  scan: resilvered 3.14T in 2 days 03:09:41 with 0 errors on Wed Jan 24 18:29:41 2024
config:

        NAME                                            STATE     READ WRITE CKSUM
        storage5                                        DEGRADED     0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/75123f50-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/7627289d-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/7778ae43-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/78bb002c-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/79e99291-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/715d621c-b939-11ee-9c62-0cc47ac6de45  ONLINE       0     0     0
            gptid/7c3546e8-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
          mirror-1                                      ONLINE       0     0     0
            gptid/3b535bc9-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0
            gptid/3bf74286-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0
          mirror-2                                      DEGRADED     0     0     0
            gptid/f6ada8d8-38c0-11ec-b8d2-0cc47ac6de45  DEGRADED     0     0   168  too many errors
            gptid/f749f2d1-38c0-11ec-b8d2-0cc47ac6de45  ONLINE       0     0     0
        cache
          gptid/24313233-3fca-11eb-9a9d-0cc47ac6de45    ONLINE       0     0     0

errors: No known data errors
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
It depends on the kind of backplane you are using.
If its an expander - then its probably not cabling. Try moving the drive to another slot, resilver, zpool clear and see what happens
If its got individual per drive cables - then reseat / replace the cable.

Its probably an expander
 

napalmd

Dabbler
Joined
Aug 24, 2017
Messages
11
Yes it is a backplane but all slots are full. what i could to is put it in the slot where is the cache drive right?
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
You can power off, and switch drives around. ZFS doesn't care where the drives are as they are identified by UUID, and not by /dev/sda or whatever
 

napalmd

Dabbler
Joined
Aug 24, 2017
Messages
11
So there was a lot of dust in the sata port, that could explain the errors:
Imagem WhatsApp 2024-01-24 às 20.56.17_4e0502c6.jpg

Cleaned it and booted server, and now it says pool healthy!
What should I do now? scrub or smart long on drive?
Code:
  pool: storage5
 state: ONLINE
  scan: resilvered 3.14T in 2 days 03:09:41 with 0 errors on Wed Jan 24 18:29:41 2024
config:

        NAME                                            STATE     READ WRITE CKSUM
        storage5                                        ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/75123f50-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/7627289d-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/7778ae43-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/78bb002c-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/79e99291-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
            gptid/715d621c-b939-11ee-9c62-0cc47ac6de45  ONLINE       0     0     0
            gptid/7c3546e8-9a37-11e7-a035-0cc47ac6de45  ONLINE       0     0     0
          mirror-1                                      ONLINE       0     0     0
            gptid/3b535bc9-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0
            gptid/3bf74286-d7ce-11ea-93e3-0cc47ac6de45  ONLINE       0     0     0
          mirror-2                                      ONLINE       0     0     0
            gptid/f6ada8d8-38c0-11ec-b8d2-0cc47ac6de45  ONLINE       0     0     0
            gptid/f749f2d1-38c0-11ec-b8d2-0cc47ac6de45  ONLINE       0     0     0
        cache
          gptid/24313233-3fca-11eb-9a9d-0cc47ac6de45    ONLINE       0     0     0

errors: No known data errors
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Clean out the rest of the drive bays - urgently
Then run a scrub

[Note to self - must check my drive bays soon.]
 
Last edited:
Top