New Tested good drives reporting Smart Long Test Failure

[kirkdickinson]

I have a z2 pool with 6 8TB WD Red Plus drives. I had intended on replacing them with 6 16TB Seagate EXOS drives. I ran conveyance, short test, and long test on all of them with HD Sentinel. All the drives had 0 hours when I got them and passed all the tests on HD Sentinel.

I started swapping them out. I did one Monday and another on Tuesday.

I checked my S.M.A.R.T reports on the pool today and see that they both have failed the long test.

The one I put in Monday, Failed twice and the one I put in Tuesday has failed once. Not sure how to progress with this. I have $1700 worth of new drives and if the first 2 have failed this test, I am really wanting to test my luck replacing the other 4 existing drives.

Is there any way to get further information on this failed test? Is there a chance that this is a "false failure?"

 

[winnielinnie]

Is there any way to get further information on this failed test? Is there a chance that this is a "false failure?"

It could have been an "aborted" test. I agree that "FAILED" should only be reserved for truly failed tests.

You can check with smartctl in the command-line:

Code:

smartctl -l selftest /dev/ada7

 

[WI_Hedgehog]

It could have been an "aborted" test. I agree that "FAILED" should only be reserved for truly failed tests.

You can check with smartctl in the command-line:

Code:

smartctl -l selftest /dev/ada7

might you perhaps mean:
smartctl --xall /dev/ada4

 

[kirkdickinson]

Thanks for the responses.

I ran the smartctl --xall /dev/ada7 command in the shell. Looks like the two failures say Aborted by host. Why would that be happening?

Last login: Wed Aug 30 15:00:51 on pts/6
FreeBSD 13.1-RELEASE-p7 n245428-4dfb91682c1 TRUENAS

TrueNAS (c) 2009-2023, iXsystems, Inc.
All rights reserved.
TrueNAS code is released under the modified BSD license with some
files copyrighted by (c) iXsystems, Inc.

For more information, documentation, help or support, go here:
http://truenas.com
Welcome to TrueNAS

Warning: the supported mechanisms for making configuration changes
are the TrueNAS WebUI and API exclusively. ALL OTHERS ARE
NOT SUPPORTED AND WILL RESULT IN UNDEFINED BEHAVIOR AND MAY
RESULT IN SYSTEM FAILURE.

root@TrueNAS1[~]# smartctl --xall /dev/ada7
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p7 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: ST16000NM000J-2TW103
Serial Number: ZR5CGPAV
LU WWN Device Id: 5 000c50 0e59ebe95
Firmware Version: SN04
User Capacity: 16,000,900,661,248 bytes [16.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 [for details use: -P showall]
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 Aug 30 15:04:14 2023 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Disabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Write SCT (Get) Feature Control Command failed: Input/output error
Wt Cache Reorder: Unknown (SCT Feature Control command failed)

=== 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: (1354) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x70bd) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 083 065 044 - 211673728
3 Spin_Up_Time PO---- 098 098 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 2
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 072 060 045 - 14318594
9 Power_On_Hours -O--CK 100 100 000 - 83
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 2
18 Unknown_Attribute PO-R-- 100 100 050 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 062 059 000 - 38 (Min/Max 34/41)
192 Power-Off_Retract_Count -O--CK 100 100 000 - 2
193 Load_Cycle_Count -O--CK 100 100 000 - 118
194 Temperature_Celsius -O---K 038 041 000 - 38 (0 24 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
200 Multi_Zone_Error_Rate PO---K 100 100 001 - 0
240 Head_Flying_Hours ------ 100 100 000 - 78 (180 114 0)
241 Total_LBAs_Written ------ 100 253 000 - 6518324426
242 Total_LBAs_Read ------ 100 253 000 - 6398869293
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x04 GPL R/O 256 Device Statistics log
0x04 SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x0a GPL R/W 8 Device Statistics Notification
0x0c GPL R/O 2048 Pending Defects log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x13 GPL R/O 1 SATA NCQ Send and Receive log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x24 GPL R/O 768 Current Device Internal Status Data log
0x2f GPL - 1 Set Sector Configuration
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 160 Device vendor specific log
0xa2 GPL VS 16320 Device vendor specific log
0xa4 GPL,SL VS 160 Device vendor specific log
0xa6 GPL VS 192 Device vendor specific log
0xa8-0xa9 GPL,SL VS 136 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xad GPL VS 16 Device vendor specific log
0xb1 GPL,SL VS 160 Device vendor specific log
0xb6 GPL VS 1920 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc1 GPL,SL VS 8 Device vendor specific log
0xc3 GPL,SL VS 24 Device vendor specific log
0xc6 GPL VS 5184 Device vendor specific log
0xc7 GPL,SL VS 8 Device vendor specific log
0xc9 GPL,SL VS 8 Device vendor specific log
0xca GPL,SL VS 16 Device vendor specific log
0xcd GPL,SL VS 1 Device vendor specific log
0xce GPL VS 1 Device vendor specific log
0xcf GPL VS 512 Device vendor specific log
0xd1 GPL VS 656 Device vendor specific log
0xd2 GPL VS 10256 Device vendor specific log
0xd4 GPL VS 2048 Device vendor specific log
0xda GPL,SL VS 1 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 68 -
# 2 Conveyance offline Completed without error 00% 30 -
# 3 Extended offline Completed without error 00% 27 -
# 4 Extended offline Aborted by host 90% 1 -
# 5 Extended offline Aborted by host 90% 1 -
# 6 Short offline Completed without error 00% 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.

SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
Device State: Active (0)
Current Temperature: 38 Celsius
Power Cycle Min/Max Temperature: 34/41 Celsius
Lifetime Min/Max Temperature: 24/41 Celsius
Under/Over Temperature Limit Count: 0/14
SMART Status: 0xc24f (PASSED)
Vendor specific:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version: 2
Temperature Sampling Period: 4 minutes
Temperature Logging Interval: 59 minutes
Min/Max recommended Temperature: 10/40 Celsius
Min/Max Temperature Limit: 5/60 Celsius
Temperature History Size (Index): 128 (88)

Index Estimated Time Temperature Celsius
89 2023-08-25 09:20 ? -
... ..( 37 skipped). .. -
127 2023-08-26 22:42 ? -
0 2023-08-26 23:41 26 *******
1 2023-08-27 00:40 ? -
2 2023-08-27 01:39 24 *****
3 2023-08-27 02:38 32 *************
4 2023-08-27 03:37 31 ************
5 2023-08-27 04:36 30 ***********
6 2023-08-27 05:35 30 ***********
7 2023-08-27 06:34 30 ***********
8 2023-08-27 07:33 29 **********
9 2023-08-27 08:32 30 ***********
10 2023-08-27 09:31 35 ****************
11 2023-08-27 10:30 36 *****************
... ..( 2 skipped). .. *****************
14 2023-08-27 13:27 36 *****************
15 2023-08-27 14:26 37 ******************
... ..( 10 skipped). .. ******************
26 2023-08-28 01:15 37 ******************
27 2023-08-28 02:14 36 *****************
28 2023-08-28 03:13 36 *****************
29 2023-08-28 04:12 35 ****************
30 2023-08-28 05:11 34 ***************
31 2023-08-28 06:10 30 ***********
32 2023-08-28 07:09 30 ***********
33 2023-08-28 08:08 30 ***********
34 2023-08-28 09:07 ? -
35 2023-08-28 10:06 34 ***************
36 2023-08-28 11:05 41 **********************
... ..( 5 skipped). .. **********************
42 2023-08-28 16:59 41 **********************
43 2023-08-28 17:58 40 *********************
... ..( 3 skipped). .. *********************
47 2023-08-28 21:54 40 *********************
48 2023-08-28 22:53 39 ********************
49 2023-08-28 23:52 39 ********************
50 2023-08-29 00:51 40 *********************
51 2023-08-29 01:50 39 ********************
... ..( 4 skipped). .. ********************
56 2023-08-29 06:45 39 ********************
57 2023-08-29 07:44 38 *******************
58 2023-08-29 08:43 38 *******************
59 2023-08-29 09:42 39 ********************
60 2023-08-29 10:41 41 **********************
... ..( 5 skipped). .. **********************
66 2023-08-29 16:35 41 **********************
67 2023-08-29 17:34 39 ********************
... ..( 10 skipped). .. ********************
78 2023-08-30 04:23 39 ********************
79 2023-08-30 05:22 38 *******************
... ..( 8 skipped). .. *******************
88 2023-08-30 14:13 38 *******************

SCT Error Recovery Control:
Read: 100 (10.0 seconds)
Write: 100 (10.0 seconds)

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 2 --- Lifetime Power-On Resets
0x01 0x010 4 83 --- Power-on Hours
0x01 0x018 6 6518324426 --- Logical Sectors Written
0x01 0x020 6 14395234 --- Number of Write Commands
0x01 0x028 6 6398869263 --- Logical Sectors Read
0x01 0x030 6 34402779 --- Number of Read Commands
0x01 0x038 6 - --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 83 --- Spindle Motor Power-on Hours
0x03 0x010 4 78 --- Head Flying Hours
0x03 0x018 4 118 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 0 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 2 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion
0x04 0x018 4 0 -D- Physical Element Status Changed
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 38 --- Current Temperature
0x05 0x010 1 39 --- Average Short Term Temperature
0x05 0x018 1 - --- Average Long Term Temperature
0x05 0x020 1 41 --- Highest Temperature
0x05 0x028 1 26 --- Lowest Temperature
0x05 0x030 1 39 --- Highest Average Short Term Temperature
0x05 0x038 1 34 --- Lowest Average Short Term Temperature
0x05 0x040 1 - --- Highest Average Long Term Temperature
0x05 0x048 1 - --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 60 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 5 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 3 --- Number of Hardware Resets
0x06 0x010 4 2 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
0xff ===== = = === == Vendor Specific Statistics (rev 1) ==
0xff 0x008 7 0 --- Vendor Specific
0xff 0x010 7 0 --- Vendor Specific
0xff 0x018 7 0 --- Vendor Specific
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

Pending Defects log (GP Log 0x0c)
No Defects Logged

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description

 

[winnielinnie]

might you perhaps mean:
smartctl --xall /dev/ada4

Just -l selftest to narrow it down to only the selftest results. If the results show "aborted", then it means that the tests didn't actually "fail". The full S.M.A.R.T. output isn't needed for this.

 

[winnielinnie]

# 4 Extended offline Aborted by host 90% 1 -
# 5 Extended offline Aborted by host 90% 1 -

Called it.

 

[winnielinnie]

Looks like the two failures say Aborted by host. Why would that be happening?

Why it says "FAILED" in the TrueNAS GUI? This is something that needs a feature request. (I think I submitted one a while back, requesting that "aborted" tests should read "ABORTED", not "FAILED". Otherwise, it can confuse the user and make them believe their drives are failing.)

EDIT: Found these bug reports, yet the fix is only applied to SCALE, not Core:

[NAS-120498] - iXsystems TrueNAS Jira

ixsystems.atlassian.net

[NAS-120537] - iXsystems TrueNAS Jira

ixsystems.atlassian.net

It still doesn't address the issue of using the word "FAILED" for an aborted test.


For your implied question: Why would a SMART selftest "abort"? Several reasons.

• You initiated another test while a current test was running.
• You ran the test on a system that uses powersaving, which doesn't know the internal test progress of a drive.
• You manually aborted the test.
• You lost power during a test.
• You rebooted during a test.
• Etc.

 

[kirkdickinson]

Thanks for all the help here.

The Long test is scheduled to run every Sunday. Short tests are scheduled to run Tuesdays and Fridays. I didn't manuall initiate another test. Since I installed them on Monday and Tuesday, and the long tests took a whole day with HD Sentinel, is it possible, that the system automatically ran the long test on the new drives and it clashed with the short test? Don't see that as likely with the one installed on Monday.

I don't have powersaving enabled.
I did not manually abort
I did not lose power
I did not reboot

Would it abort a long test if there is a replication pull from the other server during the test? I have a replication pull that runs at midnight every day.

Should I see what the test show tomorrow and then proceed from there? Is it safe to keep replacing disks with this current issue?

Thanks

 

[winnielinnie]

Something caused the test to abort, and this is common when powersaving is used. You can even see a long selftest finished with no errors after the two aborted tests. (Those aborted tests were interrupted at only 10% into the scan.)

I don't see any concern with your drives based on the SMART output and test results. However, a long selftest for 16 TiB drives every week can be excessive. Short tests can suffice. If you're running these long tests every week, and they take a long time to complete, you're going to end up having the drives undergoing long selftests during periods of disk activity (such as shares, backups, scrubs, etc.)

If you have weekly short selftests + monthly scrubs + ZFS will inform you of any errors during read operations... then you're quite covered. You can ease up on the long selftests, maybe once every month or season.

Would it abort a long test if there is a replication pull from the other server during the test? I have a replication pull that runs at midnight every day.

It "shouldn't". SMART tests run with low priority, so such a task will stretch out the selftest's duration, since it needs to give way to the I/O operations of the replication task.