January 26, 20251 yr Hallo zusammen, Ist es normal, dass man immer bei einer Party Überprüfung Fehler auf der Paritätsfesplatte hat oder ist die Festplatte schon am sterben? 26-01-2025 16:07Unraid Parity disk SMART health [187]Warning [DXP2800] - reported uncorrect is 194ST16000NM000J-2TW103_xxx(sdd)warning 26-01-2025 16:05Unraid Parity disk SMART health [187]Warning [DXP2800] - reported uncorrect is 193ST16000NM000J-2TW103_xxx (sdd)warning Grüße
January 26, 20251 yr Author Quote martctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.68-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Exos X18 Device Model: ST16000NM000J-2TW103 Serial Number: xxx LU WWN Device Id: 5 000c50 0e8099bed 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: In smartctl database 7.3/5625 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: Sun Jan 26 16:44:11 2025 CET 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 unsupported field in scsi 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) 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: (1589) 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-- 077 058 044 - 0/55985472 3 Spin_Up_Time PO---- 090 090 000 - 0 4 Start_Stop_Count -O--CK 100 100 020 - 46 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 078 060 045 - 0/59716031 9 Power_On_Hours -O--CK 098 098 000 - 2155 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 4 18 Head_Health PO-R-- 100 100 050 - 0 187 Reported_Uncorrect -O--CK 001 001 000 - 194 188 Command_Timeout -O--CK 100 100 000 - 0 0 0 190 Airflow_Temperature_Cel -O---K 059 057 000 - 41 (Min/Max 22/42) 192 Power-Off_Retract_Count -O--CK 100 100 000 - 1 193 Load_Cycle_Count -O--CK 100 100 000 - 54 194 Temperature_Celsius -O---K 041 043 000 - 41 (0 22 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 Pressure_Limit PO---K 100 100 001 - 0 240 Head_Flying_Hours ------ 100 100 000 - 171h+18m+59.281s 241 Total_LBAs_Written ------ 100 253 000 - 33005937612 242 Total_LBAs_Read ------ 100 253 000 - 166019718212 ||||||_ 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 R/O 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) Device Error Count: 213 (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 213 [12] occurred at disk power-on lifetime: 2154 hours (89 days + 18 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 -- 53 00 00 00 05 91 9c c1 28 00 00 Error: UNC at LBA = 0x5919cc128 = 23917805864 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 05 40 00 05 91 9c d0 20 40 00 37d+11:51:46.947 READ FPDMA QUEUED 60 00 00 05 40 00 05 91 9c ca e0 40 00 37d+11:51:46.947 READ FPDMA QUEUED 60 00 00 01 38 00 05 91 9c c4 68 40 00 37d+11:51:46.947 READ FPDMA QUEUED 60 00 00 04 08 00 05 91 9c c0 60 40 00 37d+11:51:46.947 READ FPDMA QUEUED 60 00 00 05 40 00 05 91 9c c5 a0 40 00 37d+11:51:46.946 READ FPDMA QUEUED Error 212 [11] occurred at disk power-on lifetime: 2154 hours (89 days + 18 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 -- 53 00 00 00 05 91 9c c1 28 00 00 Error: UNC at LBA = 0x5919cc128 = 23917805864 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 05 40 00 05 91 9c c5 a0 40 00 37d+11:51:41.617 READ FPDMA QUEUED 60 00 00 01 38 00 05 91 9c c4 68 40 00 37d+11:51:37.351 READ FPDMA QUEUED 60 00 00 04 08 00 05 91 9c c0 60 40 00 37d+11:51:37.351 READ FPDMA QUEUED 60 00 00 03 a0 00 05 91 9c bc c0 40 00 37d+11:51:37.351 READ FPDMA QUEUED 60 00 00 00 f8 00 05 91 9c bb c8 40 00 37d+11:51:37.351 READ FPDMA QUEUED Error 211 [10] occurred at disk power-on lifetime: 2154 hours (89 days + 18 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 -- 53 00 00 00 05 90 1e 71 90 00 00 Error: UNC at LBA = 0x5901e7190 = 23892750736 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 c0 00 05 90 1e 8a e0 40 00 37d+11:50:18.902 READ FPDMA QUEUED 60 00 00 02 48 00 05 90 1e 88 98 40 00 37d+11:50:15.058 READ FPDMA QUEUED 60 00 00 00 b8 00 05 90 1e 87 e0 40 00 37d+11:50:11.928 READ FPDMA QUEUED 60 00 00 02 c0 00 05 90 1e 85 20 40 00 37d+11:50:11.927 READ FPDMA QUEUED 60 00 00 01 10 00 05 90 1e 82 c0 40 00 37d+11:50:11.658 READ FPDMA QUEUED Error 210 [9] occurred at disk power-on lifetime: 1993 hours (83 days + 1 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 -- 53 00 00 00 07 35 63 14 28 00 00 Error: UNC at LBA = 0x735631428 = 30960456744 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 05 40 00 07 35 63 2c 50 40 00 30d+19:03:59.785 READ FPDMA QUEUED 60 00 00 05 40 00 07 35 63 27 10 40 00 30d+19:03:56.978 READ FPDMA QUEUED 60 00 00 05 40 00 07 35 63 21 d0 40 00 30d+19:03:56.978 READ FPDMA QUEUED 60 00 00 05 40 00 07 35 63 1c 90 40 00 30d+19:03:56.978 READ FPDMA QUEUED 60 00 00 00 80 00 07 35 63 1c 10 40 00 30d+19:03:56.978 READ FPDMA QUEUED Error 209 [8] occurred at disk power-on lifetime: 1991 hours (82 days + 23 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 -- 53 00 00 00 06 b1 35 a6 b0 00 00 Error: UNC at LBA = 0x6b135a6b0 = 28742887088 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 00 00 06 b1 36 67 00 40 00 30d+16:29:24.025 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 36 61 c0 40 00 30d+16:29:24.024 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 36 5c 80 40 00 30d+16:29:24.024 READ FPDMA QUEUED 60 00 00 03 70 00 06 b1 36 59 10 40 00 30d+16:29:24.024 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 36 53 d0 40 00 30d+16:29:24.024 READ FPDMA QUEUED Error 208 [7] occurred at disk power-on lifetime: 1991 hours (82 days + 23 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 -- 53 00 00 00 06 b1 35 9f f8 00 00 Error: UNC at LBA = 0x6b1359ff8 = 28742885368 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 70 00 06 b1 36 3a 80 40 00 30d+16:29:22.302 READ FPDMA QUEUED 60 00 00 01 d0 00 06 b1 36 38 b0 40 00 30d+16:29:18.508 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 36 33 70 40 00 30d+16:29:18.508 READ FPDMA QUEUED 60 00 00 01 d0 00 06 b1 36 31 a0 40 00 30d+16:29:18.495 READ FPDMA QUEUED 61 00 00 01 d0 00 06 b1 35 99 a0 40 00 30d+16:29:18.494 WRITE FPDMA QUEUED Error 207 [6] occurred at disk power-on lifetime: 1991 hours (82 days + 23 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 -- 53 00 00 00 06 b1 35 9a 28 00 00 Error: UNC at LBA = 0x6b1359a28 = 28742883880 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 05 40 00 06 b1 36 2c 60 40 00 30d+16:29:18.186 READ FPDMA QUEUED 60 00 00 00 a0 00 06 b1 36 2b c0 40 00 30d+16:29:18.186 READ FPDMA QUEUED 60 00 00 04 90 00 06 b1 36 27 30 40 00 30d+16:29:18.186 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 36 21 f0 40 00 30d+16:29:18.186 READ FPDMA QUEUED 60 00 00 00 a0 00 06 b1 35 be 20 40 00 30d+16:29:15.450 READ FPDMA QUEUED Error 206 [5] occurred at disk power-on lifetime: 1991 hours (82 days + 23 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 -- 53 00 00 00 06 b1 35 92 80 00 00 Error: UNC at LBA = 0x6b1359280 = 28742881920 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 90 00 06 b1 35 aa 90 40 00 30d+16:29:14.987 READ FPDMA QUEUED 60 00 00 00 a0 00 06 b1 35 a9 f0 40 00 30d+16:29:12.670 READ FPDMA QUEUED 60 00 00 03 10 00 06 b1 35 a6 e0 40 00 30d+16:29:11.004 READ FPDMA QUEUED 60 00 00 02 c0 00 06 b1 35 a4 20 40 00 30d+16:29:11.004 READ FPDMA QUEUED 60 00 00 05 40 00 06 b1 35 9e e0 40 00 30d+16:29:11.004 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) 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. SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) Device State: Active (0) Current Temperature: 41 Celsius Power Cycle Min/Max Temperature: 19/42 Celsius Lifetime Min/Max Temperature: 19/51 Celsius Under/Over Temperature Limit Count: 0/30 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 (21) Index Estimated Time Temperature Celsius 22 2025-01-21 10:54 25 ****** 23 2025-01-21 11:53 26 ******* 24 2025-01-21 12:52 26 ******* 25 2025-01-21 13:51 32 ************* 26 2025-01-21 14:50 27 ******** 27 2025-01-21 15:49 27 ******** 28 2025-01-21 16:48 26 ******* 29 2025-01-21 17:47 27 ******** 30 2025-01-21 18:46 26 ******* ... ..( 5 skipped). .. ******* 36 2025-01-22 00:40 26 ******* 37 2025-01-22 01:39 25 ****** 38 2025-01-22 02:38 25 ****** 39 2025-01-22 03:37 25 ****** 40 2025-01-22 04:36 24 ***** ... ..( 5 skipped). .. ***** 46 2025-01-22 10:30 24 ***** 47 2025-01-22 11:29 25 ****** 48 2025-01-22 12:28 25 ****** 49 2025-01-22 13:27 24 ***** 50 2025-01-22 14:26 25 ****** ... ..( 3 skipped). .. ****** 54 2025-01-22 18:22 25 ****** 55 2025-01-22 19:21 26 ******* ... ..( 5 skipped). .. ******* 61 2025-01-23 01:15 26 ******* 62 2025-01-23 02:14 25 ****** ... ..( 4 skipped). .. ****** 67 2025-01-23 07:09 25 ****** 68 2025-01-23 08:08 35 **************** 69 2025-01-23 09:07 27 ******** 70 2025-01-23 10:06 26 ******* 71 2025-01-23 11:05 26 ******* 72 2025-01-23 12:04 27 ******** ... ..( 3 skipped). .. ******** 76 2025-01-23 16:00 27 ******** 77 2025-01-23 16:59 26 ******* 78 2025-01-23 17:58 26 ******* 79 2025-01-23 18:57 26 ******* 80 2025-01-23 19:56 27 ******** 81 2025-01-23 20:55 27 ******** 82 2025-01-23 21:54 27 ******** 83 2025-01-23 22:53 29 ********** 84 2025-01-23 23:52 27 ******** 85 2025-01-24 00:51 26 ******* 86 2025-01-24 01:50 26 ******* 87 2025-01-24 02:49 25 ****** ... ..( 6 skipped). .. ****** 94 2025-01-24 09:42 25 ****** 95 2025-01-24 10:41 26 ******* 96 2025-01-24 11:40 26 ******* 97 2025-01-24 12:39 27 ******** ... ..( 4 skipped). .. ******** 102 2025-01-24 17:34 27 ******** 103 2025-01-24 18:33 30 *********** 104 2025-01-24 19:32 29 ********** ... ..( 2 skipped). .. ********** 107 2025-01-24 22:29 29 ********** 108 2025-01-24 23:28 27 ******** 109 2025-01-25 00:27 26 ******* ... ..( 2 skipped). .. ******* 112 2025-01-25 03:24 26 ******* 113 2025-01-25 04:23 25 ****** ... ..( 3 skipped). .. ****** 117 2025-01-25 08:19 25 ****** 118 2025-01-25 09:18 26 ******* 119 2025-01-25 10:17 26 ******* 120 2025-01-25 11:16 36 ***************** 121 2025-01-25 12:15 28 ********* 122 2025-01-25 13:14 27 ******** 123 2025-01-25 14:13 26 ******* 124 2025-01-25 15:12 26 ******* 125 2025-01-25 16:11 27 ******** 126 2025-01-25 17:10 27 ******** 127 2025-01-25 18:09 27 ******** 0 2025-01-25 19:08 26 ******* ... ..( 3 skipped). .. ******* 4 2025-01-25 23:04 26 ******* 5 2025-01-26 00:03 39 ******************** 6 2025-01-26 01:02 41 ********************** ... ..( 2 skipped). .. ********************** 9 2025-01-26 03:59 41 ********************** 10 2025-01-26 04:58 40 ********************* ... ..( 7 skipped). .. ********************* 18 2025-01-26 12:50 40 ********************* 19 2025-01-26 13:49 41 ********************** 20 2025-01-26 14:48 41 ********************** 21 2025-01-26 15:47 41 ********************** 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 4 --- Lifetime Power-On Resets 0x01 0x010 4 2155 --- Power-on Hours 0x01 0x018 6 33005937612 --- Logical Sectors Written 0x01 0x020 6 37439267 --- Number of Write Commands 0x01 0x028 6 166019836164 --- Logical Sectors Read 0x01 0x030 6 201099352 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 171 --- Spindle Motor Power-on Hours 0x03 0x010 4 171 --- Head Flying Hours 0x03 0x018 4 54 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 412 --- 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 1 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 195 --- 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 41 --- Current Temperature 0x05 0x010 1 33 --- Average Short Term Temperature 0x05 0x018 1 26 --- Average Long Term Temperature 0x05 0x020 1 43 --- Highest Temperature 0x05 0x028 1 19 --- Lowest Temperature 0x05 0x030 1 37 --- Highest Average Short Term Temperature 0x05 0x038 1 21 --- Lowest Average Short Term Temperature 0x05 0x040 1 26 --- Highest Average Long Term Temperature 0x05 0x048 1 24 --- 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 21 --- Number of Hardware Resets 0x06 0x010 4 5 --- 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 0x000a 2 18 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 Seagate FARM log (GP Log 0xa6) supported [try: -l farm] Edited January 26, 20251 yr by alturismo in Quote gefasst
January 26, 20251 yr Community Expert Solution 16 hours ago, iceball09 said: 16 hours ago, iceball09 said: Ist es normal, dass man immer bei einer Party Überprüfung Fehler Wenn diese einen Defekt hat oder es gar noch mehr werden: ja. https://de.wikipedia.org/wiki/Self-Monitoring,_Analysis_and_Reporting_Technology#Übliche_Parameter "Parameter: 187 Reported uncorrectable Error/ Gemeldete unkorrigierbare Fehler Ausfallskritisch Je niedrigerder Wert, desto besser Fehler, welche durch die integrierte Vorwärtsfehlerkorrektur (ECC) nicht korrigiert werden konnten." Falls er Dir immer wieder den selben Fehler meldet (also die gemeldete Summe nicht steigt), dann ist es akzepptabel. Wenn die Summe immer weiter steigt, verstirbt die Festplatte gerade und Du kannst zu sehen, wie sie bald hinüber ist. 16 hours ago, iceball09 said: auf der Paritätsfesplatte Solange sie noch nicht verstorben ist, kann man mit so einer beschädigten Festplatte zwar den Ausfall einer anderen Festplatte im Array noch weitgehend kompensieren (bis auf Sektoren, die eben nicht mehr korrekte Daten wieder geben), aber wenn die Zahl wächst, würde ich die Parity baldmöglichst austauschen. Auch kann es sein, daß sie bei einem Reparaturversuch (wenn sie eben den Ausfall einer anderen Platte abfängt) dann wirklich mitten drin stirbt, weil sie ja dann sehr stark belastet wird. Man kann so eine Festplatte mit mindestens einmal kontrolliertem Vollschreiben und dann auch wieder alles Verifizieren besser beurteilen. Es ist möglich, daß die sich nachdem sie eine gewisse Zahl von Fehlern 187 gefunden und bearbeitet hat (beim Beschreiben) sich beruhigt und es nicht noch mehr werden. Aber fehlerfrei ist die auch dann nicht mehr. Die defekten Sektoren werden dann eben nur auf Reserversektoren ausgemappt. Das beduetet an der Stelle ist dei Festplatte dann langsamer, weil der Kopf sich dann zu den Reservesektoren bewegen muß um dort Daten zu lesen/schreiben. 16 hours ago, iceball09 said: hat oder ist die Festplatte schon am sterben? Das ist möglich. Wie groß ist den der Wert von 187? Und wie groß ist der Wert von 005 (Reallocated Sectors Count = zugewiesene Reservesektoren) und 197 Current Pending Sector Count = aktuell fragwürdige Sektoren? EDIT: Hab gerade den Smartreport gesehen: 005 = 0 Verzeichnet = Keine neu zugewiesenen Sektoren 187 = 194 Verzeichnet = Fehlerhaft ausgelesene Sektoren 197 = 0 Verzeichnet = aktuell sind keien weiteren Sektoren als fragwürdig aufgefallen. Ich würde schon mal Dein Backup aktualisieren. Mindestens würde ich im Auge behalten, ob die 187 Werte ansteigen. Wenn ja. Ausfall kann kurz bevor stehen. Wen Du ein Backup hast: diese Platte aus dem Array abmelden und ggf. ein oder gar 2 mal komplett vollschreiben und jedesmal die dort geschrieben Daten Verifizieren. (Unter Windows nutze ich HD Tune Pro, aber h2testw macht es auch sehr gut und ist kostenlos. bei 16TB musst Du aber pro Schreib-/Lesedurchgang mit knapp um die 2 Tage rechnen). Danach oder auch zwischendurch die SMART Werte betrachten (die kostenlose Version von HD Tune 2.50 (ohne Pro) kann die Werte anzeigen, auch wenn da gerade drauf geschrieben wird. Wenn die nach den Quälereien immer noch steigen: Vertrau der Festplatte nicht mehr wichtige Daten an. Edited January 27, 20251 yr by DataCollector Typo
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.