Shalmi Posted March 29 Share Posted March 29 I have 6 drives in my array (2 as parity) Last night I started getting multiple errors like so Quote Unraid: Warning [UNRAID] - raw read error rate (failing now) is 11131 WDC_WUH721414ALE6L4_X0GDN9ZC (sdg) This was the SMART on that drive today before replacing the drive Quote smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.74-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Ultrastar DC HC530 Device Model: WDC WUH721414ALE6L4 Serial Number: X0GDN9ZC LU WWN Device Id: 5 000cca 297c5c0bd Firmware Version: LDGNW240 User Capacity: 14,000,519,643,136 bytes [14.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/5577 ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Mar 28 19:13:54 2024 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: 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: ( 101) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: (1571) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 001 - 15 2 Throughput_Performance P-S--- 103 103 054 - 225 3 Spin_Up_Time POS--- 090 090 001 - 215 (Average 215) 4 Start_Stop_Count -O--C- 100 100 000 - 68 5 Reallocated_Sector_Ct PO--CK 100 100 001 - 0 7 Seek_Error_Rate PO-R-- 100 100 001 - 0 8 Seek_Time_Performance P-S--- 133 133 020 - 18 9 Power_On_Hours -O--C- 096 096 000 - 32336 10 Spin_Retry_Count PO--C- 100 100 001 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 67 22 Helium_Level PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 093 093 000 - 51223 193 Load_Cycle_Count -O--C- 093 093 000 - 51223 194 Temperature_Celsius -O---- 057 057 000 - 37 (Min/Max 21/50) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 100 100 000 - 0 ||||||_ 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 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 255 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 0x0c GPL R/O 5501 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x12 GPL R/O 1 SATA NCQ Non-Data log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x15 GPL R/W 1 Rebuild Assist log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 256 Current Device Internal Status Data log 0x25 GPL R/O 256 Saved 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 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 (1 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% 31855 - # 2 Short offline Completed without error 00% 20141 - # 3 Extended offline Completed without error 00% 248 - # 4 Extended offline Interrupted (host reset) 90% 219 - # 5 Extended offline Aborted by host 90% 219 - # 6 Short offline Completed without error 00% 207 - 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): 256 (0x0100) Device State: Active (0) Current Temperature: 37 Celsius Power Cycle Min/Max Temperature: 32/44 Celsius Lifetime Min/Max Temperature: 21/50 Celsius Under/Over Temperature Limit Count: 0/0 SMART Status: 0xc24f (PASSED) Minimum supported ERC Time Limit: 65 (6.5 seconds) SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (91) Index Estimated Time Temperature Celsius 92 2024-03-28 17:06 36 ***************** ... ..( 6 skipped). .. ***************** 99 2024-03-28 17:13 36 ***************** 100 2024-03-28 17:14 37 ****************** ... ..( 4 skipped). .. ****************** 105 2024-03-28 17:19 37 ****************** 106 2024-03-28 17:20 38 ******************* ... ..( 3 skipped). .. ******************* 110 2024-03-28 17:24 38 ******************* 111 2024-03-28 17:25 37 ****************** ... ..( 13 skipped). .. ****************** 125 2024-03-28 17:39 37 ****************** 126 2024-03-28 17:40 36 ***************** ... ..( 2 skipped). .. ***************** 1 2024-03-28 17:43 36 ***************** 2 2024-03-28 17:44 37 ****************** ... ..( 3 skipped). .. ****************** 6 2024-03-28 17:48 37 ****************** 7 2024-03-28 17:49 38 ******************* ... ..( 8 skipped). .. ******************* 16 2024-03-28 17:58 38 ******************* 17 2024-03-28 17:59 37 ****************** ... ..( 18 skipped). .. ****************** 36 2024-03-28 18:18 37 ****************** 37 2024-03-28 18:19 38 ******************* ... ..( 10 skipped). .. ******************* 48 2024-03-28 18:30 38 ******************* 49 2024-03-28 18:31 37 ****************** ... ..( 17 skipped). .. ****************** 67 2024-03-28 18:49 37 ****************** 68 2024-03-28 18:50 38 ******************* ... ..( 10 skipped). .. ******************* 79 2024-03-28 19:01 38 ******************* 80 2024-03-28 19:02 37 ****************** ... ..( 6 skipped). .. ****************** 87 2024-03-28 19:09 37 ****************** 88 2024-03-28 19:10 36 ***************** 89 2024-03-28 19:11 36 ***************** 90 2024-03-28 19:12 37 ****************** 91 2024-03-28 19:13 37 ****************** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 67 --- Lifetime Power-On Resets 0x01 0x010 4 32336 --- Power-on Hours 0x01 0x018 6 35228672625 --- Logical Sectors Written 0x01 0x020 6 115181205 --- Number of Write Commands 0x01 0x028 6 1727640367312 --- Logical Sectors Read 0x01 0x030 6 2240747560 --- Number of Read Commands 0x01 0x038 6 116410495500 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 18435 --- Spindle Motor Power-on Hours 0x03 0x010 4 18435 --- Head Flying Hours 0x03 0x018 4 51223 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 481484 --- Read Recovery Attempts 0x03 0x030 4 1 --- Number of Mechanical Start Failures 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 --- Physical Element Status Changed 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 37 --- Current Temperature 0x05 0x010 1 35 N-- Average Short Term Temperature 0x05 0x018 1 35 N-- Average Long Term Temperature 0x05 0x020 1 50 --- Highest Temperature 0x05 0x028 1 21 --- Lowest Temperature 0x05 0x030 1 48 N-- Highest Average Short Term Temperature 0x05 0x038 1 25 N-- Lowest Average Short Term Temperature 0x05 0x040 1 42 N-- Highest Average Long Term Temperature 0x05 0x048 1 25 N-- 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 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 338 --- Number of Hardware Resets 0x06 0x010 4 68 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == |||_ 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 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-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 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 8 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 9 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS I ordered a new Drive to replace it and it came in. I turned off the machine. Unplugged that drive, replaced it with an equivalent size and turned the machine back on. I then selected that drive to replace it in the array and hit start. Quote Disk 1, is being reconstructed and is available for normal operation WDC_WD142KFGX-68AFPN0_5MG0VBRJ (sdg) It said it would take about 2 days to repopulate the data on that drive and then I started getting these errors: Quote UnraidBot, [Mar 28, 2024 at 9:00:01 PM]: Unraid: Alert [UNRAID] - Disk 1 in error state (disk dsbl) WDC_WD142KFGX-68AFPN0_5MG0VBRJ (sdg) Unraid: Alert [UNRAID] - Disk 2 in error state (disk dsbl) WDC_WD101KRYZ-01JPDB1_2YHTGB5D (sdf) Unraid: Warning [UNRAID] - array has errors Array has 6 disks with read errors Parity disk - WDC_WUH721414ALE6L4_X0GEHD9C (sdb) (errors 263) Disk 1 - WDC_WD142KFGX-68AFPN0_5MG0VBRJ (sdg) (errors 826) Disk 2 - WDC_WD101KRYZ-01JPDB1_2YHTGB5D (sdf) (errors 1587) Disk 3 - WDC_WUH721414ALE6L4_9LG5SM2A (sde) (errors 263) Disk 4 - WDC_WD141KRYZ-01C66B0_9LJ0785G (sdc) (errors 295) Parity 2 - WDC_WUH721414ALE6L4_9JG0WHRG (sdd) (errors 263) I panicked and stopped the array. Then I saw the uploaded image attached where multiple drives are stated as missing. What do I do. I have Loads of data I do not wanna lose (hence the 2 parity drives). Someone help Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 @JorgeB Attached. I removed the vms as they have some private names and havent been on in over a year and I did a find replace for some private container names that I dont want posted publicly. the rest is left as normal @JorgeB Thank you! unraid-diagnostics-20240328-1913.zip Quote Link to comment
Solution JorgeB Posted March 29 Solution Share Posted March 29 Diags posted appear to be before the issues, there's no rebuild or missing disks. Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 New one attached. Thank you for the quick response @JorgeB 9 minutes ago, JorgeB said: Diags posted appear to be before the issues, there's no rebuild or missing disks. unraid-diagnostics-20240329-1058.zip Quote Link to comment
JorgeB Posted March 29 Share Posted March 29 The issue was cause by the onboard SATA controller problem, all connected devices were dropped: Mar 28 20:58:20 Unraid kernel: ata2: hard resetting link Mar 28 20:58:24 Unraid kernel: ata5: softreset failed (1st FIS failed) Mar 28 20:58:24 Unraid kernel: ata5: hard resetting link Mar 28 20:58:24 Unraid kernel: ata7: softreset failed (1st FIS failed) Mar 28 20:58:24 Unraid kernel: ata7: hard resetting link Mar 28 20:58:26 Unraid kernel: ata3: softreset failed (1st FIS failed) Mar 28 20:58:26 Unraid kernel: ata3: hard resetting link Mar 28 20:58:30 Unraid kernel: ata6: softreset failed (1st FIS failed) Mar 28 20:58:30 Unraid kernel: ata6: hard resetting link Mar 28 20:58:30 Unraid kernel: ata4: softreset failed (1st FIS failed) Mar 28 20:58:30 Unraid kernel: ata4: hard resetting link Mar 28 20:58:30 Unraid kernel: ata2: softreset failed (1st FIS failed) Mar 28 20:58:30 Unraid kernel: ata2: hard resetting link Mar 28 20:58:40 Unraid kernel: ata4: softreset failed (1st FIS failed) Mar 28 20:58:40 Unraid kernel: ata4: hard resetting link Mar 28 20:58:40 Unraid kernel: ata2: softreset failed (1st FIS failed) Mar 28 20:58:40 Unraid kernel: ata2: hard resetting link Mar 28 20:58:40 Unraid kernel: ata6: softreset failed (1st FIS failed) Mar 28 20:58:40 Unraid kernel: ata6: hard resetting link Mar 28 20:58:59 Unraid kernel: ata5: softreset failed (1st FIS failed) Mar 28 20:58:59 Unraid kernel: ata5: limiting SATA link speed to 3.0 Gbps Mar 28 20:58:59 Unraid kernel: ata5: hard resetting link Mar 28 20:58:59 Unraid kernel: ata7: softreset failed (1st FIS failed) Mar 28 20:58:59 Unraid kernel: ata7: limiting SATA link speed to 3.0 Gbps Mar 28 20:58:59 Unraid kernel: ata7: hard resetting link Mar 28 20:59:01 Unraid kernel: ata3: softreset failed (1st FIS failed) Mar 28 20:59:01 Unraid kernel: ata3: limiting SATA link speed to 3.0 Gbps Mar 28 20:59:01 Unraid kernel: ata3: hard resetting link Mar 28 20:59:04 Unraid kernel: ata5: softreset failed (1st FIS failed) Mar 28 20:59:04 Unraid kernel: ata5: reset failed, giving up This was a fairly common issue with Ryzen/Threadripper controllers, not so much with later kernels, but it still happens, usually under load, if it keeps happening suggest using an add-on controller. Post new diags with the array started to see if the emulated disks are mounting. Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 @JorgeB Right now 2 drives are showing as emulated (pic attached)....which is concerning cuz only one should be. 1. Should I still start the array in this state? 2. What risk do I have of losing any of this data? 3. Should I start normally or in maintenance mode? 4. Should i be concerned that it no longer says something about repairing sdg next to the start button? Sorry for all the questions Quote Link to comment
JorgeB Posted March 29 Share Posted March 29 1 minute ago, Shalmi said: which is concerning cuz only one should be. There should be two, like mentioned the controlelr dropped all disks, when disks happens Unraid usually disables as many disks as there are parity drives. 2 minutes ago, Shalmi said: Should I still start the array in this state? Yes, in normal mode, it won't make anything worse than it already is. Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 unraid-diagnostics-20240329-1137.zip @JorgeB attached Quote Link to comment
JorgeB Posted March 29 Share Posted March 29 Emulated disks are mounting, assuming contents look correct you can rebuild on top, if the disks drop again during the rebuild 43 minutes ago, JorgeB said: suggest using an add-on controller. https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself You can rebuild both at the same time. Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 @JorgeB Thank you. going to try that now in maintenance mode following those steps. Will report back if there is an issue or if all goes well Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 ps if you have the power to edit the document. I think it should say hit "sync" instead of "start" in step 8 Rebuild Started Quote Link to comment
JorgeB Posted March 29 Share Posted March 29 24 minutes ago, Shalmi said: I think it should say hit "sync" instead of "start" in step 8 That only happens in maintenance mode, and IMHO there's not much point in doing the rebuild in maintenance mode. Quote Link to comment
Shalmi Posted March 29 Author Share Posted March 29 @JorgeBa lil late now and will hopefully lead to less stress on the controller....and hopefully wont break on me again. Good to know though 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.