M1L4 Posted March 27 Share Posted March 27 (edited) Hey Folks, (I´m following the "Need help? Read me First!" post. I hope it's matching adequatly) 1) Try the Fix Common Problems plugin! - was already installed & signaled issues and recommended steps. Since I couldn't follow them at the time, I shut the system down to prevent any changes to the situation 2) Syslog before shutdown - is lost as touched upon in my previous statement - the later retrieved one is attached 3) Smart Report - attached 4) System specifics - 4.1) Unraid Version: 6.12.8 - 4.2) plugins: - unbalanced 2024.01.26 - Unraid Connect 2024.03.06.0724 - AMD Vendor Reset 2022.07.21 - CA Auto Update Applications 2024.03.17 - CA Cleanup Appdata 2022.10.21 - Community Applications 2024.03.17 - Dynamix Cache Directories 2023.02.19 - Dynamix File Manager 2023.06.01 - Dynamix S3 Sleep 2023.03.23 - Dynamix Stop Shell 2023.02.05 - Dynamix System Buttons 2023.02.11 - Dynamix System Information 2023.02.05 - Dynamix System Statistics 2024.01.05 - Dynamix System Temperature 2023.02.04b - Fix Common Problems 2024.03.09 - FolderView 2024.01.22 - GUI Search 2023.08.31 - Intel GPU TOP 2023.09.13 - NerdTools 2024.02.17 - Network Statistics 2022.08.25 - Nuvoton NCT6687 Driver 2022.07.22 - Parity Check Tuning 2024.02.15 - Radeon TOP 2023.02.22 - Recycle Bin 2023.12.31 - Tasmota Power Monitor 2023.06.17 - Theme Engine 2023.01.17 - Tips and Tweaks 2024.01.26a - Unassigned Devices 2024.03.19 - Unassigned Devices Plus 2023.11.30 - Unassigned Devices Preclear 2024.02.22 - 4.3) Hardware - Motherboard: ASUSTeK COMPUTER INC. PRIME A520M-K , Version Rev X.0x | American Megatrends Inc., Version 3001 | BIOS dated: Wednesday, 2023-02-01 - CPU: AMD Ryzen 5 PRO 4650G with Radeon Graphics @ 3700 MHz - Disks: 3x Toshiba MG09ACA18TE (1x Parity, 1x Data, 1x intended Backup) 5) I recently configured some Shelly Plug S Devices to measure power consumption. For it's installation I shut down my server, but since my unraid System was still running a few hours later I just powered it down forcefully. After restart I noticed all my data missing. Apparently the disk had no filesystem or was ummountable. After panicking and recollecting myself, I powered the system down again to prevent furter detoriation. I think parity check was running as well and since I was unsure how the system would handle no disk vs parity data, I stopped the system again, while giving it all the time it wanted to. In one of the topics it was mentioned to start in maintainance mode, which triggered todays repair try session. I started it in maintainance, now no errors are shown neither on disk or parity, no writes no errors, as if its a complete never used before disk. The no error state frightened much more than the one with errors, which is why I started this thread. All logs are of the same session than this. Easy to follow steps would be appreciated. I feel a little alienated on unraid. 30y of windows usage, with many forceful shutdowns, but never had I any trouble regarding data corruption/preservation. Never did I imagine the trouble I would be inviting myself... Kind regards m1l4 megamind-diagnostics-20240327-2322.zip megamind-smart-20240327-2318.zip Edited March 27 by M1L4 Quote Link to comment
JorgeB Posted March 28 Share Posted March 28 Check filesystem on disk1, run it without -n Quote Link to comment
M1L4 Posted March 31 Author Share Posted March 31 (edited) Beeing unsure i made following steps: - gone to "main page/array devices" - selected unmountable disk - went to "Disk 1 Settings/Check Filesystem Status" - removed -n option and hit "check" produced following notification Quote Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes 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. Beeing scared of using the -L option, but not wanting to be a nuisiance I eventually started it regardless like mentioned in (one of multiple topics regarding that issue) - replaced newly set -n modifier with -L and hit start again produced following promt and initiated another parity Check on whole System Quote Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - 19:20:54: zeroing log - 59617 of 59617 blocks done - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_ifree 55919, counted 55932 sb_fdblocks 1977490349, counted 2008137809 - 19:20:59: scanning filesystem freespace - 144 of 144 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - 19:20:59: scanning agi unlinked lists - 144 of 144 allocation groups done - process known inodes and perform inode discovery... - agno = 45 - agno = 0 - agno = 90 - agno = 120 - agno = 60 - agno = 30 - agno = 75 - agno = 15 - agno = 105 - agno = 135 - agno = 31 - agno = 46 - agno = 61 - agno = 121 - agno = 76 - agno = 91 - agno = 136 - agno = 106 - agno = 16 - agno = 1 - agno = 47 - agno = 77 - agno = 62 - agno = 92 - agno = 122 - agno = 17 - agno = 107 - agno = 137 bad CRC for inode 20670414934 bad CRC for inode 20670414934, will rewrite cleared inode 20670414934 - agno = 78 - agno = 48 - agno = 93 - agno = 63 - agno = 2 - agno = 108 - agno = 18 - agno = 123 - agno = 79 - agno = 32 - agno = 138 - agno = 94 - agno = 49 - agno = 64 - agno = 33 - agno = 80 - agno = 109 - agno = 124 - agno = 19 - agno = 20 - agno = 139 - agno = 95 - agno = 50 - agno = 3 - agno = 65 - agno = 34 - agno = 21 - agno = 81 - agno = 110 - agno = 125 - agno = 96 - agno = 66 - agno = 51 - agno = 35 - agno = 22 - agno = 140 - agno = 82 - agno = 111 - agno = 97 - agno = 67 - agno = 4 - agno = 36 - agno = 126 - agno = 23 - agno = 52 - agno = 37 - agno = 83 - agno = 98 - agno = 141 - agno = 24 - agno = 112 - agno = 68 - agno = 53 - agno = 38 - agno = 127 - agno = 84 - agno = 25 - agno = 5 - agno = 113 - agno = 99 - agno = 69 - agno = 39 - agno = 142 - agno = 26 - agno = 114 - agno = 54 - agno = 85 bad CRC for inode 34093097295 inode identifier 8113420097374715903 mismatch on inode 34093097295 bad CRC for inode 34093097295, will rewrite inode identifier 8113420097374715903 mismatch on inode 34093097295 cleared inode 34093097295 - agno = 128 - agno = 100 - agno = 115 - agno = 27 - agno = 6 - agno = 70 - agno = 143 - agno = 116 - agno = 55 - agno = 86 - agno = 28 - agno = 101 - agno = 129 inode 14764458008 - bad extent starting block number 4503567551010003, offset 0 correcting nextents for inode 14764458008 bad data fork in inode 14764458008 cleared inode 14764458008 - agno = 71 - agno = 40 - agno = 117 - agno = 29 - agno = 87 - agno = 56 - agno = 102 - agno = 7 - agno = 41 - agno = 130 - agno = 72 bad CRC for inode 23356842238 inode identifier 12142920215042785279 mismatch on inode 23356842238 bad CRC for inode 23356842238, will rewrite inode identifier 12142920215042785279 mismatch on inode 23356842238 cleared inode 23356842238 - agno = 88 - agno = 42 - agno = 57 - agno = 103 - agno = 131 - agno = 8 - agno = 73 - agno = 89 - agno = 43 - agno = 118 - agno = 104 - agno = 58 - agno = 74 - agno = 9 - agno = 132 - agno = 119 - agno = 59 - agno = 44 - agno = 10 - agno = 133 - agno = 11 - agno = 12 - agno = 134 - agno = 13 - agno = 14 - 19:24:47: process known inodes and inode discovery - 1399552 of 1398080 inodes done - process newly discovered inodes... - 19:24:47: process newly discovered inodes - 144 of 144 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - 19:24:47: setting up duplicate extent list - 144 of 144 allocation groups done - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 6 - agno = 2 - agno = 5 - agno = 7 - agno = 8 - agno = 9 - agno = 1 - agno = 11 - agno = 10 - agno = 4 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 30 - agno = 31 - agno = 32 - agno = 33 - agno = 34 - agno = 35 - agno = 36 - agno = 37 - agno = 38 - agno = 39 - agno = 40 - agno = 41 - agno = 42 - agno = 43 - agno = 44 - agno = 45 - agno = 46 - agno = 47 - agno = 48 - agno = 49 - agno = 50 - agno = 51 - agno = 52 - agno = 53 - agno = 54 - agno = 55 - agno = 56 - agno = 57 - agno = 58 entry "installed" in shortform directory 14764458007 references free inode 14764458008 junking entry "installed" in directory inode 14764458007 corrected i8 count in directory 14764458007, was 5, now 4 - agno = 59 - agno = 60 - agno = 61 - agno = 62 - agno = 63 - agno = 64 - agno = 65 - agno = 66 - agno = 67 - agno = 68 - agno = 69 - agno = 70 - agno = 71 - agno = 72 - agno = 73 - agno = 74 - agno = 75 - agno = 76 - agno = 77 - agno = 78 - agno = 79 - agno = 80 - agno = 81 - agno = 82 - agno = 83 - agno = 84 - agno = 85 - agno = 86 - agno = 87 - agno = 88 - agno = 89 - agno = 90 - agno = 91 entry "gb2312-raw.enc" at block 0 offset 1008 in directory inode 23356835646 references free inode 23356842238 clearing inode number in entry at offset 1008... - agno = 92 - agno = 93 - agno = 94 - agno = 95 - agno = 96 - agno = 97 - agno = 98 - agno = 99 - agno = 100 - agno = 101 - agno = 102 - agno = 103 - agno = 104 - agno = 105 - agno = 106 - agno = 107 - agno = 108 - agno = 109 - agno = 110 - agno = 111 - agno = 112 - agno = 113 - agno = 114 - agno = 115 - agno = 116 - agno = 117 - agno = 118 - agno = 119 - agno = 120 - agno = 121 - agno = 122 - agno = 123 - agno = 124 - agno = 125 - agno = 126 - agno = 127 - agno = 128 - agno = 129 - agno = 130 entry "Technique$19.class" at block 0 offset 472 in directory inode 34093097282 references free inode 34093097295 clearing inode number in entry at offset 472... - agno = 131 - agno = 132 - agno = 133 - agno = 134 - agno = 135 - agno = 136 - agno = 137 - agno = 138 - agno = 139 - agno = 140 - agno = 141 - agno = 142 - agno = 143 clearing reflink flag on inodes when possible - 19:24:47: check for inodes claiming duplicate blocks - 1399552 of 1398080 inodes done Phase 5 - rebuild AG headers and trees... - 19:24:47: rebuild AG headers and trees - 144 of 144 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 34093097282 (no data entry): rebuilding rebuilding directory inode 34093097282 bad hash table for directory inode 23356835646 (no data entry): rebuilding rebuilding directory inode 23356835646 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... - 19:28:37: verify and correct link counts - 144 of 144 allocation groups done Maximum metadata LSN (127:414324) is ahead of log (1:2). Format log to cycle 130. done - I`m unsure if the "parity override" option was set as the parity check was triggered automatically after xfs-repair check - thus unsure if I should let it continue - since Parity Check is in progress and I decided against stopping it for now, I can#T check File Recovery as we are still in Maintainence Mode - currently no Data present, not sure that is already an indication of possible success/failure Edited March 31 by M1L4 Quote Link to comment
JorgeB Posted April 1 Share Posted April 1 Do you mean you ran the filesystem check with the array running normally? If yes you will need to re-start it, disk1 should then mount. 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.