[SOLVED] ZFS Pool creates error while resilvering

J

jakobus

New Member
Sep 23, 2024
11
0
1
zpool status
Code: 
root@jkbs-lab:~# zpool status
  pool: pool1
 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 Sep 23 14:24:29 2024
        800G / 800G scanned, 180G / 800G issued at 70.9M/s
        53.9G resilvered, 22.55% done, 02:29:12 to go
config:

        NAME                                          STATE     READ WRITE CKSUM
        pool1                                         DEGRADED     0     0     0
          mirror-0                                    DEGRADED     0     0     0
            ata-WDC_WD20EFZX-68AWUN0_WD-WX92DA0LJJVZ  FAULTED      3   263     0  too many errors
            ata-ST2000VX008-2E3164_Z52A3Z9Y           ONLINE       0     0     0


smart data for sdb or ata-WDC_WD20EFZX-68AWUN0_WD-WX92DA0LJJVZ


Code: 
root@jkbs-lab:~# smartctl -a /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Skyhawk
Device Model:     ST2000VX008-2E3164
Serial Number:    Z52A3Z9Y
LU WWN Device Id: 5 000c50 0c605af05
Firmware Version: CV12
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5900 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5319
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Mon Sep 23 15:09:51 2024 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:                (   97) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 260) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x10b9) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       130154760
  3 Spin_Up_Time            0x0003   099   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3250
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       128925315
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       12527h+00m+00.000s
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       947
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       8591179810
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       1205
190 Airflow_Temperature_Cel 0x0022   064   058   045    Old_age   Always       -       36 (Min/Max 25/36)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2288
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       3267
194 Temperature_Celsius     0x0022   036   042   000    Old_age   Always       -       36 (0 10 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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 dont know what to do now, i already tried reformatting and removing the disk out of the case because of vibrations
 

Attachments

  • dmesg.log
    44.5 KB · Views: 4
That's smartctl output from the seagate while you have problems with the wd drive ...
But anyway let the resilver run until end and then take a look after zfs status again !
 
There are a lot of errors in the dmesg.log. Maybe a bad cable or broken drive controller?
I also see errors about misaligned writes. Maybe create a partition on the WD drive first (which you align to 4k sectors or 1MB) and use that partition instead of the whole drive?
 
waltar said:
That's smartctl output from the seagate while you have problems with the wd drive ...
But anyway let the resilver run until end and then take a look after zfs status again !
Click to expand...
I will post the correct one, just saw that. I can't let the resilvering because it will have to many errors

Code: 
root@jkbs-lab:~# smartctl -a /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EFZX-68AWUN0
Serial Number:    WD-WX92DA0LJJVZ
LU WWN Device Id: 5 0014ee 2be67ae24
Firmware Version: 81.00A81
User Capacity:    2,000,398,934,016 bytes [2.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 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Sep 23 16:30:42 2024 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:  (0x00) Offline data collection activity
                                        was never started.
                                        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:                (22260) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No 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:        ( 239) minutes.
SCT capabilities:              (0x303d) 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     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   197   197   021    Pre-fail  Always       -       3116
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       8
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       4
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       7
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       5
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       3
194 Temperature_Celsius     0x0022   122   114   000    Old_age   Always       -       25
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 456 (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 456 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.724  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.706  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.691  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.691  SET FEATURES [Set transfer mode]

Error 455 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.691  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.672  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.658  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.658  SET FEATURES [Set transfer mode]

Error 454 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.658  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.639  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.624  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.624  SET FEATURES [Set transfer mode]

Error 453 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.624  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.606  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.591  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.591  SET FEATURES [Set transfer mode]

Error 452 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.591  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.572  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.558  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.558  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported
 
Last edited:
leesteken said:
There are a lot of errors in the dmesg.log. Maybe a bad cable or broken drive controller?
I also see errors about misaligned writes. Maybe create a partition on the WD drive first (which you align to 4k sectors or 1MB) and use that partition instead of the whole drive?
Click to expand...
how would i do that when i need the whole disk for the raid 1 pool?
 
The HDD isn't in the Smart DB. So I would first install the current db with update-smart-drivedb and then post the smart data here again.
 
Last edited:
jakobus said:
how would i do that when i need the whole disk for the raid 1 pool?
Click to expand...
If you can't spare the 1MiB or so on the 2TB drive, then I guess you can't do that. But it looks like the drive has bigger issues than non-aligned writes. Start a long self-test (smartctl -t long /dev/sdb) and wait for several hours to determine if the drive itself thinks there are problems, or whether the problem is somewhere between the CPU and the drive, This is not specific to Proxmox or ZFS, so other (Linux) troubleshooting guides also apply.
 
JensF said:
The HDD isn't in the Smart DB. So I would first install the current db with update-smart-drivedb and then post the smart data here again.
Click to expand...
Code: 
root@jkbs-lab:~# smartctl -a /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (CMR)
Device Model:     WDC WD20EFZX-68AWUN0
Serial Number:    WD-WX92DA0LJJVZ
LU WWN Device Id: 5 0014ee 2be67ae24
Firmware Version: 81.00A81
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5610
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Sep 23 16:40:44 2024 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:  (0x00) Offline data collection activity
                                        was never started.
                                        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:                (22260) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No 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:        ( 239) minutes.
SCT capabilities:              (0x303d) 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     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   197   197   021    Pre-fail  Always       -       3116
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       8
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       4
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       7
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       5
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       3
194 Temperature_Celsius     0x0022   119   114   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 456 (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 456 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.724  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.706  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.691  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.691  SET FEATURES [Set transfer mode]

Error 455 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.691  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.672  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.658  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.658  SET FEATURES [Set transfer mode]

Error 454 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.658  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.639  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.624  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.624  SET FEATURES [Set transfer mode]

Error 453 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.624  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.606  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.591  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.591  SET FEATURES [Set transfer mode]

Error 452 occurred at disk power-on lifetime: 4 hours (0 days + 4 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
  -- -- -- -- -- -- --
  04 61 46 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 08      00:28:45.591  SET FEATURES [Set transfer mode]
  ec 00 00 00 00 00 a0 08      00:28:45.572  IDENTIFY DEVICE
  ec 00 00 00 00 00 a0 08      00:28:45.558  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:28:45.558  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported
 
Which SATA controller do you use? Your WD HDD is only in SATA II mode and your Seagate HDD even in SATA I!
 
JensF said:
Which SATA controller do you use? Your WD HDD is only in SATA II mode and your Seagate HDD even in SATA I!
Click to expand...
its the one from the mainboard (white cable in the middle)
IMG_20240923_170034.jpg
 
So not faster than SATA II. Right!
Check again if those cables are plugged in correctly.
The Smart error you got is SET FEATURES [Set transfer mode] So your HDD is trying SATA III mode but your controller only supports SATA II.
Are there some jumper pins on the HDD (depends how old these drive is)?
It could probably help to set the drive in SATA II mode: https://support-in.wd.com/app/answe...-serial-ata,-eide,-ssd-drives-jumper-settings
 
JensF said:
So not faster than SATA II. Right!
Check again if those cables are plugged in correctly.
The Smart error you got is SET FEATURES [Set transfer mode] So your HDD is trying SATA III mode but your controller only supports SATA II.
Are there some jumper pins on the HDD (depends how old these drive is)?
It could probably help to set the drive in SATA II mode: https://support-in.wd.com/app/answers/detailweb/a_id/1991/~/information-and-support-for-serial-ata,-eide,-ssd-drives-jumper-settings
Click to expand...
i dont think thats the problem, because this hdd worked perfectly fine in single disk operation with no mirroring
 
new dmesg after resilvering got aborted because of high error count


and this happened at shutdown

IMG_20240923_195956.jpg
 

Attachments

  • dmesg.log
    52.9 KB · Views: 0
Last edited:
This is what happened when i tried formatting the disk on my laptop

Code: 
[70689.285218] ACPI Error: No handler for Region [ECSI] (000000004152c8a5) [EmbeddedControl] (20220331/evregion-130)
[70689.285239] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20220331/exfldio-261)
[70689.285268] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.285394] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.285413] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322169] ACPI Error: No handler for Region [ECSI] (000000004152c8a5) [EmbeddedControl] (20220331/evregion-130)
[70689.322189] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20220331/exfldio-261)
[70689.322216] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322239] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322258] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70690.015311] ata1: SATA link down (SStatus 0 SControl 300)
[70690.343246] ata2: SATA link down (SStatus 0 SControl 300)
[70693.842041] scsi host2: uas_pre_reset: timed out
[70693.842075] sd 2:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
[70693.842092] sd 2:0:0:0: [sda] tag#20 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[70693.842132] xhci_hcd 0000:03:00.4: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[70693.842162] xhci_hcd 0000:03:00.4: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[70693.842299] sd 2:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 1 inflight: CMD
[70693.842311] sd 2:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 4b 75 70 22 00 04 00 00
[70693.842324] sd 2:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 2 inflight: CMD
[70693.842330] sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 4b 75 74 22 00 04 00 00
[70693.842428] sd 2:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[70693.842434] sd 2:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 4b 75 70 22 00 04 00 00
[70693.842439] I/O error, dev sda, sector 1265987618 op 0x1:(WRITE) flags 0x4800 phys_seg 512 prio class 2
[70693.842450] buffer_io_error: 502 callbacks suppressed
[70693.842453] Buffer I/O error on dev sda1, logical block 632993792, lost async page write
[70693.842463] Buffer I/O error on dev sda1, logical block 632993793, lost async page write
[70693.842468] Buffer I/O error on dev sda1, logical block 632993794, lost async page write
[70693.842473] Buffer I/O error on dev sda1, logical block 632993795, lost async page write
[70693.842490] Buffer I/O error on dev sda1, logical block 632993796, lost async page write
[70693.842494] Buffer I/O error on dev sda1, logical block 632993797, lost async page write
[70693.842499] Buffer I/O error on dev sda1, logical block 632993798, lost async page write
[70693.842504] Buffer I/O error on dev sda1, logical block 632993799, lost async page write
[70693.842510] Buffer I/O error on dev sda1, logical block 632993800, lost async page write
[70693.842514] Buffer I/O error on dev sda1, logical block 632993801, lost async page write
[70693.843449] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[70693.843457] sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 4b 75 74 22 00 04 00 00
[70693.843462] I/O error, dev sda, sector 1265988642 op 0x1:(WRITE) flags 0x800 phys_seg 512 prio class 2
[70694.782250] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[70695.028515] sd 2:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[70695.179244] usb 4-1: reset SuperSpeed USB device number 3 using xhci_hcd
[70695.197974] scsi host2: uas
[70695.324000] scsi 2:0:0:0: Direct-Access     ASMT     ASM1156-PM       0    PQ: 0 ANSI: 6
[70695.356039] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[70695.356049] sd 2:0:0:0: [sda] 4096-byte physical blocks
[70695.356192] sd 2:0:0:0: [sda] Write Protect is off
[70695.356194] sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
[70695.356414] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[70695.356562] sd 2:0:0:0: [sda] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[70695.356565] sd 2:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[70695.382253]  sda: sda1
[70695.382559] sd 2:0:0:0: [sda] Attached SCSI disk
 
jakobus said:
This is what happened when i tried formatting the disk on my laptop

Code: 
[70689.285218] ACPI Error: No handler for Region [ECSI] (000000004152c8a5) [EmbeddedControl] (20220331/evregion-130)
[70689.285239] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20220331/exfldio-261)
[70689.285268] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.285394] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.285413] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322169] ACPI Error: No handler for Region [ECSI] (000000004152c8a5) [EmbeddedControl] (20220331/evregion-130)
[70689.322189] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20220331/exfldio-261)
[70689.322216] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322239] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70689.322258] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20220331/psparse-529)
[70690.015311] ata1: SATA link down (SStatus 0 SControl 300)
[70690.343246] ata2: SATA link down (SStatus 0 SControl 300)
[70693.842041] scsi host2: uas_pre_reset: timed out
[70693.842075] sd 2:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
[70693.842092] sd 2:0:0:0: [sda] tag#20 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[70693.842132] xhci_hcd 0000:03:00.4: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[70693.842162] xhci_hcd 0000:03:00.4: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[70693.842299] sd 2:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 1 inflight: CMD
[70693.842311] sd 2:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 4b 75 70 22 00 04 00 00
[70693.842324] sd 2:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 2 inflight: CMD
[70693.842330] sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 4b 75 74 22 00 04 00 00
[70693.842428] sd 2:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[70693.842434] sd 2:0:0:0: [sda] tag#3 CDB: Write(10) 2a 00 4b 75 70 22 00 04 00 00
[70693.842439] I/O error, dev sda, sector 1265987618 op 0x1:(WRITE) flags 0x4800 phys_seg 512 prio class 2
[70693.842450] buffer_io_error: 502 callbacks suppressed
[70693.842453] Buffer I/O error on dev sda1, logical block 632993792, lost async page write
[70693.842463] Buffer I/O error on dev sda1, logical block 632993793, lost async page write
[70693.842468] Buffer I/O error on dev sda1, logical block 632993794, lost async page write
[70693.842473] Buffer I/O error on dev sda1, logical block 632993795, lost async page write
[70693.842490] Buffer I/O error on dev sda1, logical block 632993796, lost async page write
[70693.842494] Buffer I/O error on dev sda1, logical block 632993797, lost async page write
[70693.842499] Buffer I/O error on dev sda1, logical block 632993798, lost async page write
[70693.842504] Buffer I/O error on dev sda1, logical block 632993799, lost async page write
[70693.842510] Buffer I/O error on dev sda1, logical block 632993800, lost async page write
[70693.842514] Buffer I/O error on dev sda1, logical block 632993801, lost async page write
[70693.843449] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[70693.843457] sd 2:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 4b 75 74 22 00 04 00 00
[70693.843462] I/O error, dev sda, sector 1265988642 op 0x1:(WRITE) flags 0x800 phys_seg 512 prio class 2
[70694.782250] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[70695.028515] sd 2:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[70695.179244] usb 4-1: reset SuperSpeed USB device number 3 using xhci_hcd
[70695.197974] scsi host2: uas
[70695.324000] scsi 2:0:0:0: Direct-Access     ASMT     ASM1156-PM       0    PQ: 0 ANSI: 6
[70695.356039] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[70695.356049] sd 2:0:0:0: [sda] 4096-byte physical blocks
[70695.356192] sd 2:0:0:0: [sda] Write Protect is off
[70695.356194] sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
[70695.356414] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[70695.356562] sd 2:0:0:0: [sda] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[70695.356565] sd 2:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[70695.382253]  sda: sda1
[70695.382559] sd 2:0:0:0: [sda] Attached SCSI disk
Click to expand...
It's clearly not a Proxmox issue but a drive problem. Start a long self-test (smartctl -t long /dev/sdb, like I wrote before) and wait for several hours to determine if the drive itself detects any problems. That's usually enough for a RMA.
 
leesteken said:
Start a long self-test (smartctl -t long /dev/sdb, like I wrote before)
Click to expand...
jakobus said:
[70693.842453] Buffer I/O error on dev sda1, logical block 632993792, lost async page write [70693.842463] Buffer I/O error on dev sda1, logical block 632993793, lost async page write [70693.842468] Buffer I/O error on dev sda1, logical block 632993794, lost async page write [70693.842473] Buffer I/O error on dev sda1, logical block 632993795, lost async page write [70693.842490] Buffer I/O error on dev sda1, logical block 632993796, lost async page write [70693.842494] Buffer I/O error on dev sda1, logical block 632993797, lost async page write [70693.842499] Buffer I/O error on dev sda1, logical block 632993798, lost async page write [70693.842504] Buffer I/O error on dev sda1, logical block 632993799, lost async page write [70693.842510] Buffer I/O error on dev sda1, logical block 632993800, lost async page write [70693.842514] Buffer I/O error on dev sda1, logical block 632993801, lost async page write
Click to expand...
Just sayin....

you got problems. run a smart test on BOTH disks, but I suspect the issue isnt your drives. all those abrt's recorded by your WD suggests the problem is with cabling/motherboard. considering the age of the hardware, that might not be so surprising.
 
alexskysilk said:
Just sayin....

you got problems. run a smart test on BOTH disks, but I suspect the issue isnt your drives. all those abrt's recorded by your WD suggests the problem is with cabling/motherboard. considering the age of the hardware, that might not be so surprising.
Click to expand...
this was from my laptop via a dockingstation
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back