jul9000 Posted April 20 Share Posted April 20 (edited) Few days ago (last Sunday, to be specific) I got this email alert from my Unraid server: Quote Event: Unraid Parity disk error Subject: Alert [VALIS] - Parity disk in error state (disk dsbl) Description: WDC_WD120EDBZ-11B1HA0_5QHPW06B (sdc) Importance: alert And a second one right after: Quote Event: Unraid array errors Subject: Warning [VALIS] - array has errors Description: Array has 1 disk with read errors Importance: warning Parity disk - WDC_WD120EDBZ-11B1HA0_5QHPW06B (sdc) (errors 900) I was busy with my kids being sick last week, so I couldn’t take immediate action, so I ran a parity check on Wednesday, which resulted in these emails: Quote Event: Unraid Parity disk message Subject: Notice [VALIS] - Parity disk returned to normal operation Description: No device identification () Importance: normal followed by this: Quote Event: Unraid array errors Subject: Notice [VALIS] - array turned good Description: Array has 0 disks with read errors Importance: normal WTF?! Where are the Sunday's errors gone...? Thursday evening, since the parity drive icon was a red cross ("Device is disabled, contents emulated", whatever that means...) and I had some time and a spare hard drive, I removed the faulty (?) parity drive, installed a fresh one and started rebuilding the parity. I got these emails at 8:27 PM: Quote Event: Unraid Parity disk message Subject: Notice [VALIS] - Parity disk, parity-sync in progress Description: WDC_WD120EDBZ-11B1HA0_5QH0DNZF (sdc) Importance: normal Quote Event: Unraid Parity-Sync Subject: Notice [VALIS] - Parity-Sync started Description: Size: 12.0 TB Importance: warning But at 8:58 shit started happening: Quote Event: Unraid array errors Subject: Warning [VALIS] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 7 - WDC_WD80EDBZ-11B0ZA0_VGKYJ0SG (sdi) (errors 230016) Parity rebuild ended after some 26 hours with these: Quote Event: Unraid Parity disk message Subject: Notice [VALIS] - Parity disk returned to normal operation Description: WDC_WD120EDBZ-11B1HA0_5QH0DNZF (sdc) Importance: normal Quote Event: Unraid Parity-Sync Subject: Notice [VALIS] - Parity-Sync finished (463701 errors) Description: Duration: 1 day, 2 hours, 51 minutes, 9 seconds. Average speed: 124.1 MB/s Importance: warning What do I do now…? My understanding is that, my current parity drive may be “incorrect” because of the errors on one of the data/array drive (Disk 7 - WDC_WD80EDBZ-11B0ZA0_VGKYJ0SG). Am I right? Should I try and put back my previous parity drive (WDC_WD120EDBZ-11B1HA0_5QHPW06B), the one which reported some errors on Sunday, but turned out to be fine on Wednesday/Thursday? If the parity data is fine there after all, maybe I will be able to rebuild the faulty data/array drive (Disk 7 - WDC_WD80EDBZ-11B0ZA0_VGKYJ0SG)? What do you guys recommend? Let me know if you need any diagnostic data! Edited April 20 by jul9000 Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 (edited) I found some screenshots I made in the process “old” parity drive error log, taken on Sunday: data drive error log, taken on Thursday evening: are those serious? is there anything to be done? Edited April 20 by jul9000 Quote Link to comment
itimpi Posted April 20 Share Posted April 20 You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 Here's my diagnostic file valis-diagnostics-20240420-0704.zip Quote Link to comment
Solution JorgeB Posted April 20 Solution Share Posted April 20 Diags show errors with disk7, don't see any with parity, disk7 errors look more like a power connection problem, replace cables (also do it for parity) and run a parity check. 1 Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 25 minutes ago, JorgeB said: Diags show errors with disk7, don't see any with parity, disk7 errors look more like a power connection problem, replace cables (also do it for parity) and run a parity check. Thanks for tour input! I’m currently running a SMART extended self-test on disk7, just to make sure. I guess you won’t see any issues with the “old” parity drive, because it was removed and replaced by a fresh one. How do you know disk7 errors look more like a power connection problem? Is this based on the screenshots I provided, or do you see any indications in logs? The reason why I’m asking, is that I would like to know, if the “old” parity drive can still be used as future replacement. Errors on both old parity drive and disk7 looks very similar on my screenshots, so maybe the old parity drive also only had power connection problems? Quote Link to comment
itimpi Posted April 20 Share Posted April 20 7 minutes ago, jul9000 said: so maybe the old parity drive also only had power connection problems Continual resets on a drive showing up in the syslog are typical symptoms of power/connection problems. The simplest check is to run the Extended SMART test on the drive. That test is completely internal to the drive so If that passes then then the drive is normally OK. The only other likely cause would be insufficient power reaching the drive. 1 Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 both these drives were shucked from respectively a WD Elements and WD MyBook, so I suspect the power connection issue may come from the faulty covered 3 power pin. Instead of covering the pin, I will now use a Molex-to-SATA adapter. I want to learn something from all of this, can you guys point me to specific syslog entries showing these "continual resets"? Are you talking about these? Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367032 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367040 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367048 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367864 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367056 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367064 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367072 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367080 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367872 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367088 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367096 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367104 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367112 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367880 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367120 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367128 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367136 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585367144 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367888 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367896 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367904 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367912 Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2964 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367920 Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2964 Sense Key : 0x2 [current] Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2964 ASC=0x4 ASCQ=0x0 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367928 Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2964 CDB: opcode=0x88 88 00 00 00 00 00 22 e3 f6 b8 00 00 04 00 00 00 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367936 Apr 18 20:57:30 VALIS kernel: I/O error, dev sdi, sector 585365176 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 2 Apr 18 20:57:30 VALIS kernel: md: recovery thread: multiple disk errors, sector=585367944 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365112 Apr 18 20:57:30 VALIS kernel: md: recovery thread: stopped logging Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365120 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365128 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365136 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365144 Apr 18 20:57:30 VALIS kernel: md: disk7 read error, sector=585365152 Quote Link to comment
JorgeB Posted April 20 Share Posted April 20 Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2963 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2963 Sense Key : 0x2 [current] Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2963 ASC=0x4 ASCQ=0x0 Apr 18 20:57:30 VALIS kernel: sd 1:0:6:0: [sdi] tag#2963 CDB: opcode=0x88 88 00 00 00 00 00 22 e3 fa b8 00 00 03 f8 00 00 Apr 18 20:57:30 VALIS kernel: I/O error, dev sdi, sector 585366200 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 2 This part specifically, it's not logged as a disk problem, it's also not logged on the disk SMART report, and the attributes look OK, so both point to not being a disk problem. 1 Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 looks good, right? smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.79-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD80EDBZ-11B0ZA0 Serial Number: VGKYJ0SG LU WWN Device Id: 5 000cca 0bef7b16d Firmware Version: 85.00A85 User Capacity: 8,001,563,222,016 bytes [8.00 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/5601 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: Sat Apr 20 19:25:55 2024 CEST 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, NOT FROZEN [SEC1], Master PW ID: 0xbbbb 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: ( 17) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 87) 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: ( 922) 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 016 - 0 2 Throughput_Performance --S--- 127 127 054 - 112 3 Spin_Up_Time POS--- 145 145 024 - 561 (Average 558) 4 Start_Stop_Count -O--C- 100 100 000 - 474 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate -O-R-- 100 100 067 - 0 8 Seek_Time_Performance --S--- 128 128 020 - 18 9 Power_On_Hours -O--C- 100 100 000 - 5228 10 Spin_Retry_Count -O--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 11 192 Power-Off_Retract_Count -O--CK 099 099 000 - 2044 193 Load_Cycle_Count -O--C- 099 099 000 - 2044 194 Temperature_Celsius -O---- 203 203 000 - 32 (Min/Max 25/55) 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-- 200 200 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 Extended offline Aborted by host 10% 5226 - 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: 32 Celsius Power Cycle Min/Max Temperature: 32/51 Celsius Lifetime Min/Max Temperature: 25/55 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/65 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (77) Index Estimated Time Temperature Celsius 78 2024-04-20 17:19 44 ************************* ... ..( 45 skipped). .. ************************* 124 2024-04-20 18:05 44 ************************* 125 2024-04-20 18:06 43 ************************ 126 2024-04-20 18:07 42 *********************** 127 2024-04-20 18:08 42 *********************** 0 2024-04-20 18:09 41 ********************** 1 2024-04-20 18:10 40 ********************* 2 2024-04-20 18:11 40 ********************* 3 2024-04-20 18:12 39 ******************** 4 2024-04-20 18:13 39 ******************** 5 2024-04-20 18:14 39 ******************** 6 2024-04-20 18:15 38 ******************* 7 2024-04-20 18:16 38 ******************* 8 2024-04-20 18:17 37 ****************** 9 2024-04-20 18:18 37 ****************** 10 2024-04-20 18:19 37 ****************** 11 2024-04-20 18:20 36 ***************** ... ..( 2 skipped). .. ***************** 14 2024-04-20 18:23 36 ***************** 15 2024-04-20 18:24 35 **************** ... ..( 3 skipped). .. **************** 19 2024-04-20 18:28 35 **************** 20 2024-04-20 18:29 34 *************** ... ..( 5 skipped). .. *************** 26 2024-04-20 18:35 34 *************** 27 2024-04-20 18:36 33 ************** ... ..( 10 skipped). .. ************** 38 2024-04-20 18:47 33 ************** 39 2024-04-20 18:48 32 ************* ... ..( 36 skipped). .. ************* 76 2024-04-20 19:25 32 ************* 77 2024-04-20 19:26 44 ************************* 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 11 --- Lifetime Power-On Resets 0x01 0x010 4 5228 --- Power-on Hours 0x01 0x018 6 15628218278 --- Logical Sectors Written 0x01 0x020 6 21928626 --- Number of Write Commands 0x01 0x028 6 97376930598 --- Logical Sectors Read 0x01 0x030 6 110101906 --- Number of Read Commands 0x01 0x038 6 18822002400 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 1191 --- Spindle Motor Power-on Hours 0x03 0x010 4 1191 --- Head Flying Hours 0x03 0x018 4 2044 --- 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 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 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 32 --- Current Temperature 0x05 0x010 1 46 N-- Average Short Term Temperature 0x05 0x018 1 35 N-- Average Long Term Temperature 0x05 0x020 1 55 --- Highest Temperature 0x05 0x028 1 25 --- Lowest Temperature 0x05 0x030 1 51 N-- Highest Average Short Term Temperature 0x05 0x038 1 25 N-- Lowest Average Short Term Temperature 0x05 0x040 1 50 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 65 --- 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 26 --- Number of Hardware Resets 0x06 0x010 4 8 --- 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 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 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 Quote Link to comment
jul9000 Posted April 20 Author Share Posted April 20 how do I get rid of these tho? Quote Link to comment
JonathanM Posted April 20 Share Posted April 20 2 minutes ago, jul9000 said: how do I get rid of these tho? Stop and start the array, or shutdown and reboot. Can't remember if just stopping and starting clears the error column, but I think it does. 1 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.