Solved help with smartctl output

I have 2 discs in mirror mode with zfs , Western Digital Black 2.00TB each
Code:
zpool status
give me errors from while to while in one disk , I run a scrub in the pool and no errors
even one time the disk was dettached automatically

so, I dettach the disk from the pool, I try to wipe it with zeros and dd gives me I/O error after 15GB or more written
I run
Code:
smartctl -t show /dev/ada1

and there is bad news, I dont understand if I can recover the disk
the ouput is this

Code:
smartctl 7.4 2023-08-01 r5530 [FreeBSD 14.1-RELEASE amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Black
Device Model:     WDC WD2003FZEX-00SRLA0
Serial Number:    WD-WCC6N0PEZC60
LU WWN Device Id: 5 0014ee 2bf6d62cb
Firmware Version: 01.01A01
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5528
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:    Wed Jun 19 09:06:43 2024 -03
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:         (    0) 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:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 207) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x203d)    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   181   179   021    Pre-fail  Always       -       3908
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       905
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1444
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       897
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       329
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       620
194 Temperature_Celsius     0x0022   112   100   000    Old_age   Always       -       35
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   137   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: 564 (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 564 occurred at disk power-on lifetime: 1444 hours (60 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 41 00 00 00 00 40  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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a0 01 00 00 00 00 40 08      02:09:37.206  PACKET
  60 01 b8 af 88 e0 40 08      02:09:37.200  READ FPDMA QUEUED
  a0 01 00 00 00 00 40 08      02:09:37.195  PACKET
  60 01 a8 00 00 00 40 08      02:09:37.189  READ FPDMA QUEUED
  a0 01 00 00 00 00 40 08      02:09:37.184  PACKET

Error 563 occurred at disk power-on lifetime: 1438 hours (59 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 10 00 00 00 40  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
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 562 occurred at disk power-on lifetime: 1438 hours (59 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 00 30 3b 4e 40  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
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 561 occurred at disk power-on lifetime: 1438 hours (59 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 00 30 3b 4e 40  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
  -- -- -- -- -- -- -- --  ----------------  --------------------

Error 560 occurred at disk power-on lifetime: 1438 hours (59 days + 22 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 41 00 30 3b 4e 40  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
  -- -- -- -- -- -- -- --  ----------------  --------------------

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%      1444         -
# 2  Extended offline    Interrupted (host reset)      10%         0         -
# 3  Extended offline    Interrupted (host reset)      90%         0         -

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.

The above only provides legacy SMART information - try 'smartctl -x' for more
 
I'm assuming since you mentioned this is part of a mirror, and that you tried wiping it with dd that when you say "recover" you're talking about the drive itself and not any data on it.

In my experience, if you cannot zero a drive with dd, it is dead. Time to retire it.

You can try running smartctl with -t long to do an extensive test.
 
I'm assuming since you mentioned this is part of a mirror, and that you tried wiping it with dd that when you say "recover" you're talking about the drive itself and not any data on it.

In my experience, if you cannot zero a drive with dd, it is dead. Time to retire it.

You can try running smartctl with -t long to do an extensive test.

before detach it , I made a backup..and yes, I dont have any good vision about recover the disk..when dd fails.is dead
 
Could be power related? PSU crapping out after running for some time? Property 197, 198 and 199 are still all zero, so I don't think the disk itself has gone bad. Definitely try to run a long test, and let it actually finish, there are two long tests that could not be finished due to a reboot of the system.
 
Could be power related? PSU crapping out after running for some time? Property 197, 198 and 199 are still all zero, so I don't think the disk itself has gone bad. Definitely try to run a long test, and let it actually finish, there are two long tests that could not be finished due to a reboot of the system.

Yes, the problems disappear when remove and plugin the sata power connector

long test in way...I am conected via ssh to my home..so I have a lot of time to run the test

and change the power supply when I go home
 
... give me errors from while to while in one disk ...
... and dd gives me I/O error after 15GB or more written ...
What were the errors? You can find the messages in the output of dmesg (if you haven't rebooted), or in /var/log/messages. Older versions of that file are archived and compressed there for a while.

As SirDice already said, given that the smartctl output shows no media errors, and all the error in the smartctl log are just "abort", I suspect the problem to be cabling or power supply. But exact error messages would help.
 
What were the errors? You can find the messages in the output of dmesg (if you haven't rebooted), or in /var/log/messages. Older versions of that file are archived and compressed there for a while.

As SirDice already said, given that the smartctl output shows no media errors, and all the error in the smartctl log are just "abort", I suspect the problem to be cabling or power supply. But exact error messages would help.

Turned off the machine,I think I can reproduce the error, a simple dd write to the disc abort with a I/O error
when i have the machine I will post the error
 
SirDice and ralphbsz , 100% right , the problem is the power source
now I turn on my computer, make a

dd if=/dev/zero of=/dev/ada1 bs=2M status="progress"

so far is 230GB done, before was 15GB and above and end with a I/O error

thanks!!!!
 
Back
Top