partyhat Posted October 25, 2020 Share Posted October 25, 2020 (edited) Hi, I'm running Unraid v 6.8.3. About 6 days ago I had a power outage to the house. The server came back online after the outage and the array started fine and started a parity check which usually take 18 hours. I haven't check on it until today and I noticed the parity check was still going, over 5 days later and only at 1MB/second, with 7697 errors found in the check, all on Disk 1. The usual parity check average is around 80MB/s. It's an old HP N36L Microserver, so not the fastest by any means! I have 4 disks in the server, 1x8TB parity drive, 1x8TB data drive, and two older 2TB data drives. Disk 1 is a WDC_WD20EARX. On the Main page, I clicked the folder icon to view the file structure on the disks. For Disk 1, zero files and directories were found. The other disks show the expected files/folders fine. I stopped the array, started it back in maintenance mode, and still have all green circles for each disk on the Main page. For Disk 1 with the errors I then performed the Check Filesystem Status with the -n option. The output is below. Check filesystem status with -n log: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 49658396, counted 53071622 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 data fork in ino 3223323200 claims free block 402915382 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 setting reflink flag on inode 3223323200 setting reflink flag on inode 3223323201 Missing reference count record for (3/262198) len 1 count 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:1498400) is ahead of log (1:1497691). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. I then ran it again without the -n and got this: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. The smart report output is: root@Tower:~# smartctl -a -A /dev/sde smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WCAZA7891273 LU WWN Device Id: 5 0014ee 25b44d162 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s) Local Time is: Sun Oct 25 10:54:26 2020 AEST SMART support is: Available - device has SMART capability. SMART support is: 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: (36480) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 352) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 5 3 Spin_Up_Time 0x0027 253 162 021 Pre-fail Always - 1308 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2207 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4793 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2123 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 393 193 Load_Cycle_Count 0x0032 190 190 000 Old_age Always - 32030 194 Temperature_Celsius 0x0022 115 097 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 14 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 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. After I ran that I stopped the array again and started without maintenance mode. Now I get "Unmountable disk present" in the Array Operation section with the option to format the disk. This is concerning obviously. The parity check started automatically and has only been running for 10 minutes now at 1.8MB/s. I stopped it for now as I am not sure if it could make things worse. What is my next step advised to fix this? I wasn't sure if there is something else to do other than start the parity check again, but when I initially stopped it today it was estimating 83 days remaining at 1MB/s so I figured there must be a better way. Maybe the filesystem on that disk corrupted? Please advise Edited October 25, 2020 by partyhat Quote Link to comment
itimpi Posted October 25, 2020 Share Posted October 25, 2020 2 hours ago, partyhat said: then ran it again without the -n and got this: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. This is quite normal. You need to provide the -L option for the repair to proceed. Despite the scary sounding warning message data loss does not normally occur, and when it does only a file that was actively being written at the point things went wrong is affected. Quote Link to comment
partyhat Posted October 25, 2020 Author Share Posted October 25, 2020 Thanks mate I am running that now and will report back! Quote Link to comment
partyhat Posted October 25, 2020 Author Share Posted October 25, 2020 (edited) Thanks mate I am running that now and will report back! edit: ran with the -L option and it completed the task in about 5 minutes. Stopped the maintenance mode array and bright it back online normally. I could then see the files/folders from the “main” window and a read check started. It is going slow though and the I refreshed the page and noticed the disk is now disabled (with a red x beside it), and the disk also appears in the unassigned devices section is it likely the disk is dead/nearly dead and requires replacement if this weird behaviour is occurring? Or should it come back online after the parity check is done? Edited October 25, 2020 by partyhat Quote Link to comment
itimpi Posted October 25, 2020 Share Posted October 25, 2020 No - the disk should not have become disabled unless Unraid detected a (write) failure so that is not a good sign. I suggest posting the system’s diagnostics zip file so we can see the current state and what lead up to it. Quote Link to comment
partyhat Posted October 26, 2020 Author Share Posted October 26, 2020 Yes it is getting write errors. Attached is a screenshot from the live disk log information. I will have to generate a diagnostic log when I am home again. Would I have to replace the disk to rebuild my data if the disk is dead/dying? I believe I had enough free space on other disks in the array so can the parity check just move the missing data to the other disks if I take this drive out of the server instead? I don't want to buy another disk right now if I can avoid it. Quote Link to comment
partyhat Posted October 26, 2020 Author Share Posted October 26, 2020 Attached diagnostics file, hope someone can help. I did some more reading on other forum threads and confirmed I have enough free space on the array so if I need to I can potentially use unbalance to copy the emulated data off the problem disk then run the process to remove the disk and shrink the array while keeping the current parity as is. As long as someone could please confirm that I do need to do this that would be fantastic! tower-diagnostics-20201026-2119.zip Quote Link to comment
partyhat Posted October 27, 2020 Author Share Posted October 27, 2020 (edited) I ran extended smart test and it came back with no errors. I then ran the sequence to make the drive reconstruct but it’s going at 600kb/s and the eta is 18 days. It’s still showing errors like in the above screenshot when I click show disk information. Any further advice? Edited October 27, 2020 by partyhat Quote Link to comment
JorgeB Posted October 27, 2020 Share Posted October 27, 2020 Replace/swap cables on that drive, can't see which one is ATA5 since log rotated. 1 Quote Link to comment
partyhat Posted October 28, 2020 Author Share Posted October 28, 2020 (edited) On 10/27/2020 at 11:44 PM, JorgeB said: Replace/swap cables on that drive, can't see which one is ATA5 since log rotated. Thanks I reseated the drive and the errors are gone and the drive is rebuilding much faster now. Seems odd that would fix it but oh well, looking promising! Thanks!! edit: All appears to be working now after the drive rebuild. Thanks Edited October 28, 2020 by partyhat 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.