smartctl alternatives

Grinas

Grinas

Contributor
Joined
May 4, 2017
Messages
174
Is there an alternative to smartctl.

Literally every drive failure i have had smartctl shows as pass but i am still bombarded with alerts in the console/commadline which makes using the host via CLI a night mare.


I am currently getting alerts for a spare drive in CLI but smartctl says it passed the test.


Screenshot 2024-02-14 at 12.27.35 p.m..png



Code:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.63-production+truenas] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST10000VE001-3BX101
Serial Number:    WP00PJ2F
LU WWN Device Id: 5 000c50 0edac4c7b
Firmware Version: EV01
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database 7.3/5319
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Feb 14 12:28:53 2024 GMT
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:         (  559) 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:      ( 862) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x50bd)    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   081   064   044    Pre-fail  Always       -       126570497
  3 Spin_Up_Time            0x0003   091   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       14
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   045    Pre-fail  Always       -       309835356
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       4194
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       13
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   066   066   000    Old_age   Always       -       34
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       8590131203
190 Airflow_Temperature_Cel 0x0022   070   040   000    Old_age   Always       -       30 (Min/Max 24/33)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       8
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1916
194 Temperature_Celsius     0x0022   030   060   000    Old_age   Always       -       30 (0 24 0 0 0)
197 Current_Pending_Sector  0x0012   100   085   000    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0010   100   085   000    Old_age   Offline      -       6
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       4044 (219 103 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       105942459784
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       200985233951

SMART Error Log Version: 1
ATA Error Count: 46 (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 46 occurred at disk power-on lifetime: 884 hours (36 days + 20 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  31d+02:23:11.265  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:10.264  WRITE FPDMA QUEUED
  61 00 10 30 01 00 40 00  31d+02:23:09.825  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  31d+02:23:09.752  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:09.680  WRITE FPDMA QUEUED

Error 45 occurred at disk power-on lifetime: 884 hours (36 days + 20 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  31d+02:23:08.553  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED

Error 44 occurred at disk power-on lifetime: 879 hours (36 days + 15 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 80 ff ff ff 4f 00  30d+21:03:16.383  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+21:03:15.862  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.857  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.856  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.855  WRITE FPDMA QUEUED

Error 43 occurred at disk power-on lifetime: 877 hours (36 days + 13 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  30d+19:21:04.056  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  30d+19:21:03.525  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:21:03.055  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  30d+19:21:03.034  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:21:02.678  WRITE FPDMA QUEUED

Error 42 occurred at disk power-on lifetime: 877 hours (36 days + 13 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 00 43 03 40 00  30d+19:15:20.901  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:20.551  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:19.910  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:19.731  WRITE FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  30d+19:15:19.461  READ FPDMA QUEUED

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

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.


This drive is only a few weeks old and dont want to have to pay shipping costs for RMA unless i have to.
 
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Grinas said:
Is there an alternative to smartctl.
Click to expand...
No, what would that do?
Grinas said:
I am currently getting alerts for a spare drive in CLI but smartctl says it passed the test.
Click to expand...
No, you're reading too much into that single line. The disk hasn't run any SMART tests in months, so there are no tests to fail, but the disk already has six uncorrectable sectors, despite being almost brand-new.

There's a good chance that the disk will fail a long SMART test at this point, though it's not guaranteed.
Grinas said:
This drive is only a few weeks old and dont want to have to pay shipping costs for RMA unless i have to.
Click to expand...
It's certainly not remotely trustworthy. Load it a bit and it's likely to die outright or at least fail hard enough that Seagate will RMA it without question.
 
Grinas

Grinas

Contributor
Joined
May 4, 2017
Messages
174
Ericloewe said:
No, what would that do?

No, you're reading too much into that single line. The disk hasn't run any SMART tests in months, so there are no tests to fail, but the disk already has six uncorrectable sectors, despite being almost brand-new.

There's a good chance that the disk will fail a long SMART test at this point, though it's not guaranteed.

It's certainly not remotely trustworthy. Load it a bit and it's likely to die outright or at least fail hard enough that Seagate will RMA it without question.
Click to expand...

So it didnt fail after the long test. Should i just keep doing them till it does?

Any idea how to prevent the console/CLI alerts so its not a pain in the ass to work on some containers


Code:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.63-production+truenas] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST10000VE001-3BX101
Serial Number:    WP00PJ2F
LU WWN Device Id: 5 000c50 0edac4c7b
Firmware Version: EV01
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database 7.3/5319
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Feb 19 18:05:12 2024 GMT
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:      ( 113)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (  559) 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:      ( 862) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x50bd)    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   081   064   044    Pre-fail  Always       -       126583937
  3 Spin_Up_Time            0x0003   091   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       14
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   045    Pre-fail  Always       -       314489528
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       4319
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       13
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   066   066   000    Old_age   Always       -       34
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       8590131203
190 Airflow_Temperature_Cel 0x0022   068   040   000    Old_age   Always       -       32 (Min/Max 24/36)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       8
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2151
194 Temperature_Celsius     0x0022   032   060   000    Old_age   Always       -       32 (0 24 0 0 0)
197 Current_Pending_Sector  0x0012   100   085   000    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0010   100   085   000    Old_age   Offline      -       6
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       4056 (105 151 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       105942459784
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       200985247391

SMART Error Log Version: 1
ATA Error Count: 46 (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 46 occurred at disk power-on lifetime: 884 hours (36 days + 20 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  31d+02:23:11.265  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:10.264  WRITE FPDMA QUEUED
  61 00 10 30 01 00 40 00  31d+02:23:09.825  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  31d+02:23:09.752  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:09.680  WRITE FPDMA QUEUED

Error 45 occurred at disk power-on lifetime: 884 hours (36 days + 20 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  31d+02:23:08.553  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  31d+02:23:08.553  WRITE FPDMA QUEUED

Error 44 occurred at disk power-on lifetime: 879 hours (36 days + 15 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 80 ff ff ff 4f 00  30d+21:03:16.383  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+21:03:15.862  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.857  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.856  WRITE FPDMA QUEUED
  61 00 80 ff ff ff 4f 00  30d+21:03:15.855  WRITE FPDMA QUEUED

Error 43 occurred at disk power-on lifetime: 877 hours (36 days + 13 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00  30d+19:21:04.056  WRITE FPDMA QUEUED
  61 00 08 00 43 03 40 00  30d+19:21:03.525  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:21:03.055  WRITE FPDMA QUEUED
  61 00 10 ff ff ff 4f 00  30d+19:21:03.034  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:21:02.678  WRITE FPDMA QUEUED

Error 42 occurred at disk power-on lifetime: 877 hours (36 days + 13 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 00 43 03 40 00  30d+19:15:20.901  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:20.551  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:19.910  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00  30d+19:15:19.731  WRITE FPDMA QUEUED
  60 00 80 ff ff ff 4f 00  30d+19:15:19.461  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%      4206         -
# 2  Conveyance offline  Completed without error       00%        68         -
# 3  Extended offline    Completed without error       00%        13         -

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.
 
danb35

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Grinas said:
So it didnt fail after the long test.
Click to expand...
Yes, it did:
Code:
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%      4206         -
 
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Yeah, that's Seagate's way of saying "sorry, we sold you a piece of crap", which is not something companies do lightly.
 
Grinas

Grinas

Contributor
Joined
May 4, 2017
Messages
174
danb35 said:
Yes, it did:
Code:
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%      4206         -
Click to expand...

Ericloewe said:
Yeah, that's Seagate's way of saying "sorry, we sold you a piece of crap", which is not something companies do lightly.
Click to expand...


Why the hell then does smart test say it passed.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

I am not sure why the hell they even have a test result field if the result it gives is never correct.

It would be great if there was an actual alternative to smart that gave clear results.
 
Patrick M. Hausen

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
Grinas said:
Why the hell then does smart test say it passed.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Click to expand...
smartctl -a is not a test but simply a query of the device to send all its collected information. That information says "in general I feel ok", read, I'm powered up, I can answer this request, if you are lucky I will even hand you some previously written data blocks. It does not mean "I have just tested if I can read all my data blocks and they seem to be ok." That's what a SMART test does.

The test results are the lines way down in the smartctl output and they clearly state that the drive has problems.
 
Last edited:
dak180

dak180

Patron
Joined
Nov 22, 2017
Messages
310
Grinas said:
It would be great if there was an actual alternative to smart that gave clear results.
Click to expand...

If you are looking for a report that will highlight such things you can check out the link in my sig.
 
You must log in or register to reply here.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "smartctl alternatives"

Similar threads

T
SmartCTL and Badblocks Questions
Replies
2
Views
2K
Sumppi
S
scotrod
Should I trust smartctl or Scrutiny when it comes to S.M.A.R.T monitoring?
Replies
6
Views
3K
scotrod
scotrod
K
  • Locked
HDD with Currently unreadable (pending) sectors but is PASSING all tests.
Replies
1
Views
1K
Stux
Stux
Dopamin3
Failed HDD in vdev caused boot-pool error- something to worry about?
Replies
5
Views
1K
Dopamin3
Dopamin3
P
  • Locked
smartctl vs badblocks
Replies
7
Views
6K
Stux
Stux
Top