KeriBoti Posted August 2, 2022 Share Posted August 2, 2022 I just set up an array with brand new disks and ran a parity-sync on it, during which one of the drives (disk1) has encountered a few read errors. I looked in the diagnostics files where the errors were logged, but at the top of it it reads: "SMART overall-health self-assessment test result: PASSED" Being new to this whole SMART thing I have no clue what type of errors these are and what to make of them, so I'd appreciate it if someone could take a look at it and tell me if I should be worried. Also, I could't figure out how to attach files so I just dumped the file here like this (apologies if this is not the proper way to do it) smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.46-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate IronWolf Pro Device Model: ST12000NE0008-2PK103 Serial Number: ZTN0N6LM LU WWN Device Id: 5 000c50 0e32642e9 Firmware Version: EN02 User Capacity: 12,000,138,625,024 bytes [12.0 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/5387 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: Tue Aug 2 14:32:02 2022 CEST 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: scsi error aborted command 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 567) 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: (1077) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 082 056 044 - 157644095 3 Spin_Up_Time PO---- 095 095 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 4 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 068 060 045 - 6601374 9 Power_On_Hours -O--CK 100 100 000 - 20 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 3 18 Head_Health PO-R-- 100 100 050 - 0 187 Reported_Uncorrect -O--CK 061 061 000 - 39 188 Command_Timeout -O--CK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 064 049 040 - 36 (Min/Max 36/36) 192 Power-Off_Retract_Count -O--CK 100 100 000 - 2 193 Load_Cycle_Count -O--CK 100 100 000 - 6 194 Temperature_Celsius -O---K 036 041 000 - 36 (0 26 0 0 0) 197 Current_Pending_Sector -O--C- 100 100 000 - 296 198 Offline_Uncorrectable ----C- 100 100 000 - 296 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 200 Pressure_Limit PO---K 100 100 001 - 0 240 Head_Flying_Hours ------ 100 253 000 - 20h+34m+55.954s 241 Total_LBAs_Written ------ 100 253 000 - 4192632 242 Total_LBAs_Read ------ 100 253 000 - 23565606285 ||||||_ 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 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc1 GPL,SL VS 8 Device vendor specific log 0xc3 GPL,SL VS 56 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 10000 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 0xe2 GPL,SL - 160 Reserved SMART Extended Comprehensive Error Log Version: 1 (5 sectors) Device Error Count: 39 (device log contains only the most recent 20 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register 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 39 [18] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c7 07 60 00 00 Error: UNC at LBA = 0x1c2c70760 = 7562790752 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 03 b8 00 01 c2 c7 15 00 40 00 05:16:26.886 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c7 11 00 40 00 05:16:26.886 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c7 0d 00 40 00 05:16:26.886 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c7 09 00 40 00 05:16:26.885 READ FPDMA QUEUED 60 00 00 00 48 00 01 c2 c7 04 b8 40 00 05:16:26.885 READ FPDMA QUEUED Error 38 [17] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 f7 c8 00 00 Error: UNC at LBA = 0x1c2c6f7c8 = 7562786760 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 48 00 01 c2 c7 04 b8 40 00 05:16:23.209 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c7 00 b8 40 00 05:16:23.209 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 fc b8 40 00 05:16:23.208 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 f8 b8 40 00 05:16:23.208 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 f4 b8 40 00 05:16:23.208 READ FPDMA QUEUED Error 37 [16] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 d7 a0 00 00 Error: UNC at LBA = 0x1c2c6d7a0 = 7562778528 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 03 18 00 01 c2 c6 d7 98 40 00 05:16:19.494 READ FPDMA QUEUED 60 00 00 03 78 00 01 c2 c6 d3 28 40 00 05:16:19.494 READ FPDMA QUEUED 60 00 00 02 18 00 01 c2 c6 a6 40 40 00 05:16:19.494 READ FPDMA QUEUED 60 00 00 00 90 00 01 c2 c6 bd 18 40 00 05:16:19.494 READ FPDMA QUEUED 60 00 00 01 58 00 01 c2 c6 bb c0 40 00 05:16:19.494 READ FPDMA QUEUED Error 36 [15] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 c8 10 00 00 Error: UNC at LBA = 0x1c2c6c810 = 7562774544 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 f8 00 01 c2 c6 d6 a0 40 00 05:16:19.393 READ FPDMA QUEUED 60 00 00 03 78 00 01 c2 c6 d3 28 40 00 05:16:15.752 READ FPDMA QUEUED 60 00 00 00 c0 00 01 c2 c6 d2 68 40 00 05:16:15.734 READ FPDMA QUEUED 60 00 00 03 40 00 01 c2 c6 cf 28 40 00 05:16:15.734 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 cb 28 40 00 05:16:15.734 READ FPDMA QUEUED Error 35 [14] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 b8 80 00 00 Error: UNC at LBA = 0x1c2c6b880 = 7562770560 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 04 00 00 01 c2 c6 c7 28 40 00 05:16:15.710 READ FPDMA QUEUED 60 00 00 00 f8 00 01 c2 c6 c6 30 40 00 05:16:12.004 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 c2 30 40 00 05:16:12.004 READ FPDMA QUEUED 60 00 00 00 a0 00 01 c2 c6 c1 90 40 00 05:16:11.919 READ FPDMA QUEUED 60 00 00 03 e8 00 01 c2 c6 bd a8 40 00 05:16:11.919 READ FPDMA QUEUED Error 34 [13] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 a8 e8 00 00 Error: UNC at LBA = 0x1c2c6a8e8 = 7562766568 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 00 f8 00 01 c2 c6 b2 c8 40 00 05:16:11.869 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 ae c8 40 00 05:16:11.869 READ FPDMA QUEUED 60 00 00 00 88 00 01 c2 c6 ae 40 40 00 05:16:07.947 READ FPDMA QUEUED 60 00 00 00 18 00 01 c2 c6 ae 28 40 00 05:16:07.936 READ FPDMA QUEUED 60 00 00 03 e8 00 01 c2 c6 aa 40 40 00 05:16:07.936 READ FPDMA QUEUED Error 33 [12] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 99 60 00 00 Error: UNC at LBA = 0x1c2c69960 = 7562762592 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 01 e8 00 01 c2 c6 a8 58 40 00 05:16:07.821 READ FPDMA QUEUED 60 00 00 02 18 00 01 c2 c6 a6 40 40 00 05:16:07.821 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 a2 40 40 00 05:16:07.821 READ FPDMA QUEUED 60 00 00 00 f8 00 01 c2 c6 a1 48 40 00 05:16:03.970 READ FPDMA QUEUED 60 00 00 00 88 00 01 c2 c6 a0 c0 40 00 05:16:03.960 READ FPDMA QUEUED Error 32 [11] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 c2 c6 89 d0 00 00 Error: UNC at LBA = 0x1c2c689d0 = 7562758608 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 00 04 00 00 01 c2 c6 99 48 40 00 05:16:03.938 READ FPDMA QUEUED 60 00 00 01 e8 00 01 c2 c6 97 60 40 00 05:16:03.938 READ FPDMA QUEUED 60 00 00 04 00 00 01 c2 c6 93 60 40 00 05:16:03.938 READ FPDMA QUEUED 60 00 00 02 18 00 01 c2 c6 91 48 40 00 05:16:00.056 READ FPDMA QUEUED 60 00 00 00 f8 00 01 c2 c6 90 50 40 00 05:16:00.040 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 20 7562726880 # 2 Extended offline Completed: read failure 90% 20 7562734744 # 3 Extended offline Completed: read failure 90% 20 7562726880 # 4 Short offline Completed: read failure 90% 20 7562726880 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: 36 Celsius Power Cycle Min/Max Temperature: 36/36 Celsius Lifetime Min/Max Temperature: 26/50 Celsius Under/Over Temperature Limit Count: 0/0 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 01 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 (24) Index Estimated Time Temperature Celsius 25 2022-07-28 09:18 ? - ... ..(101 skipped). .. - 127 2022-08-01 13:36 ? - 0 2022-08-01 14:35 50 ******************************* 1 2022-08-01 15:34 ? - 2 2022-08-01 16:33 29 ********** 3 2022-08-01 17:32 37 ****************** 4 2022-08-01 18:31 ? - 5 2022-08-01 19:30 26 ******* 6 2022-08-01 20:29 39 ******************** 7 2022-08-01 21:28 41 ********************** 8 2022-08-01 22:27 41 ********************** 9 2022-08-01 23:26 40 ********************* ... ..( 2 skipped). .. ********************* 12 2022-08-02 02:23 40 ********************* 13 2022-08-02 03:22 39 ******************** 14 2022-08-02 04:21 39 ******************** 15 2022-08-02 05:20 39 ******************** 16 2022-08-02 06:19 38 ******************* 17 2022-08-02 07:18 38 ******************* 18 2022-08-02 08:17 39 ******************** ... ..( 3 skipped). .. ******************** 22 2022-08-02 12:13 39 ******************** 23 2022-08-02 13:12 ? - 24 2022-08-02 14:11 36 ***************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 3 --- Lifetime Power-On Resets 0x01 0x010 4 20 --- Power-on Hours 0x01 0x018 6 4192584 --- Logical Sectors Written 0x01 0x020 6 4329 --- Number of Write Commands 0x01 0x028 6 23565606269 --- Logical Sectors Read 0x01 0x030 6 43219126 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 20 --- Spindle Motor Power-on Hours 0x03 0x010 4 20 --- Head Flying Hours 0x03 0x018 4 6 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 86 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 296 --- 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 84 --- 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 36 --- Current Temperature 0x05 0x010 1 - --- Average Short Term Temperature 0x05 0x018 1 - --- Average Long Term Temperature 0x05 0x020 1 41 --- Highest Temperature 0x05 0x028 1 31 --- Lowest Temperature 0x05 0x030 1 - --- Highest Average Short Term Temperature 0x05 0x038 1 - --- 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 32 --- Number of Hardware Resets 0x06 0x010 4 15 --- 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) Index LBA Hours 0 7562647008 6 1 7562647009 6 2 7562647010 6 3 7562647011 6 4 7562647012 6 5 7562647013 6 6 7562647014 6 7 7562647015 6 8 7562650976 6 9 7562650977 6 10 7562650978 6 11 7562650979 6 12 7562650980 6 13 7562650981 6 14 7562650982 6 15 7562650983 6 16 7562658936 6 17 7562658937 6 18 7562658938 6 19 7562658939 6 20 7562658940 6 21 7562658941 6 22 7562658942 6 23 7562658943 6 24 7562662904 6 25 7562662905 6 26 7562662906 6 27 7562662907 6 28 7562662908 6 29 7562662909 6 30 7562662910 6 ... (265 entries not shown) SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 6 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 14 minutes ago, KeriBoti said: 197 Current_Pending_Sector -O--C- 100 100 000 - 296 198 Offline_Uncorrectable ----C- 100 100 000 - 296 14 minutes ago, KeriBoti said: # 1 Extended offline Completed: read failure 90% 20 7562726880 Makes me wonder what else is wrong with your system. Do any of your other drives have SMART warnings on the Dashboard page? Attach diagnostics to your NEXT post in this thread. Quote Link to comment
KeriBoti Posted August 2, 2022 Author Share Posted August 2, 2022 No, this is the only drive that reported errors, all others show "healthy" status on the dashboard. Could you explain to me briefly what the stats you quoted mean/indicate? Also attached are the diagnostics (note: I did reboot my system since the parity check, but I have another diagnostics dump from while the sync was still running and the errors have already occured. Should I attach that too?) tower-diagnostics-20220802-1431.zip Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 24 minutes ago, KeriBoti said: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 20 7562726880 # 2 Extended offline Completed: read failure 90% 20 7562734744 # 3 Extended offline Completed: read failure 90% 20 7562726880 # 4 Short offline Completed: read failure 90% 20 7562726880 Every one of these means the drive has failed and needs to be replaced. And you have way more pending than I would allow even without that. https://en.wikipedia.org/wiki/S.M.A.R.T.#Known_ATA_S.M.A.R.T._attributes 5 minutes ago, KeriBoti said: Should I attach that too? yes Quote Link to comment
KeriBoti Posted August 2, 2022 Author Share Posted August 2, 2022 6 minutes ago, trurl said: Every one of these means the drive has failed and needs to be replaced. So the brand new drive has basically already failed? How common is that? Couldn't this be caused by loose cabling? Here is the dump from before the reboot, while parity sync was still running: tower-diagnostics-20220802-0933.zip Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 Everything else looks good in those diagnostics, but I'd still like to see those taken during sync. Was this the initial parity build? Doesn't look like you have any data yet. Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 1 minute ago, KeriBoti said: Couldn't this be caused by loose cabling? No. SMART attributes are things detected by the drive firmware and are recorded in the drive firmware. Most of the time a drive doesn't even know if it has a bad connection since it doesn't receive any data. Sometimes it will receive inconsistent data (checksum) and that will be recorded in this SMART attribute: 39 minutes ago, KeriBoti said: 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 Haven't looked at those other diagnostics yet. Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 8 minutes ago, KeriBoti said: How common is that? Not very. Often people will test a disk before trusting it in their array though. Since this is all new and no data at risk no harm done except a drive that needs to be returned. Unassigned Devices Preclear Plugin is the current way to test disks on Unraid, but there are other ways including software from the drive manufacturers. Quote Link to comment
KeriBoti Posted August 2, 2022 Author Share Posted August 2, 2022 16 minutes ago, trurl said: Was this the initial parity build? Doesn't look like you have any data yet. Yes it was 7 minutes ago, trurl said: no harm done except a drive that needs to be returned. Guess I'll start looking into returning that drive then... Quote Link to comment
Solution trurl Posted August 2, 2022 Solution Share Posted August 2, 2022 Aug 2 00:10:59 Tower kernel: sd 1:0:4:0: [sdf] tag#4651 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=6s Aug 2 00:10:59 Tower kernel: sd 1:0:4:0: [sdf] tag#4651 Sense Key : 0x3 [current] [descriptor] Aug 2 00:10:59 Tower kernel: sd 1:0:4:0: [sdf] tag#4651 ASC=0x11 ASCQ=0x0 Aug 2 00:10:59 Tower kernel: sd 1:0:4:0: [sdf] tag#4651 CDB: opcode=0x88 88 00 00 00 00 01 c2 c4 b5 58 00 00 02 38 00 00 Aug 2 00:10:59 Tower kernel: blk_update_request: critical medium error, dev sdf, sector 7562638792 op 0x0:(READ) flags 0x0 phys_seg 57 prio class 0 Aug 2 00:10:59 Tower kernel: md: disk1 read error, sector=7562638728 Aug 2 00:10:59 Tower kernel: md: disk1 read error, sector=7562638736 Aug 2 00:10:59 Tower kernel: md: disk1 read error, sector=7562638744 ... Parity sync was still ongoing when those were taken, and later diagnostics seem to indicate parity valid, so it might be possible to rebuild disk1 to a new disk. But if disk1 didn't have any data on it yet I don't think I would bother, and it might be better to not trust parity anyway. You can start over without that disk if you want by doing New Config without it and rebuilding parity. Quote Link to comment
trurl Posted August 2, 2022 Share Posted August 2, 2022 Just now, trurl said: You can start over without that disk if you want by doing New Config without it and rebuilding parity. https://wiki.unraid.net/Manual/Tools#New_Config When you get a replacement disk you can add it later. Quote Link to comment
KeriBoti Posted August 2, 2022 Author Share Posted August 2, 2022 38 minutes ago, trurl said: You can start over without that disk if you want by doing New Config without it and rebuilding parity. Yeah, I think that's the best course of action now. Thanks for your help! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.