jjooee Posted September 9, 2022 Share Posted September 9, 2022 Hello - I noticed a few days ago that one of the data disks in my array was forced offline I believe due to too many UDMA CRC error's. I replaced the cables going to that drive as a precaution. I followed the instructions noted here to rebuild the drive onto itself as it appeared the disk was fine just out of sync with the array. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself I did the rebuild process in maintenance mode and it completed successfully. I then stopped the array and started it again in normal mode. After the array started successfully I'm seeing the rebuilt disk show "Unmountable: No file system" Under these circumstances I should I choose to allow the disk to format or not? I just want to make double sure I'm not going to mess up the data on that disk or array since I thought it already rebuilt the disk from parity by following the steps above. Thank you for the help! Quote Link to comment
JorgeB Posted September 9, 2022 Share Posted September 9, 2022 1 minute ago, jjooee said: I should I choose to allow the disk to format or not? Don't format, check filesystem, post the diagnostics if that doesn't fix it. Quote Link to comment
jjooee Posted September 9, 2022 Author Share Posted September 9, 2022 After running the check filesystem with -nv I got the attached results. When running the check again with no options I get the following: 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. Considering the disk is showing unmountable, I believe my only option is to run the check with the -vL flag, correct? Thanks again for the help! xfsrepair-nv.txt Quote Link to comment
jjooee Posted September 9, 2022 Author Share Posted September 9, 2022 @JorgeB Here are the attributes for the disk if it helps Quote Link to comment
jjooee Posted September 9, 2022 Author Share Posted September 9, 2022 Diagnostics attached titan-diagnostics-20220909-1303.zip Quote Link to comment
trurl Posted September 9, 2022 Share Posted September 9, 2022 48 minutes ago, jjooee said: run the check with the -vL flag, correct? correct Quote Link to comment
jjooee Posted September 9, 2022 Author Share Posted September 9, 2022 These are the results I get when running -vL against the disk. The disk status is now showing "Unmountable: wrong or no file system" Quote Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes - block cache size set to 6054232 entries Phase 2 - using internal log - zero log... zero_log: head block 2210880 tail block 2210864 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - 13:34:26: zeroing log - 521728 of 521728 blocks done - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata agf_freeblks 891167, counted 891254 in ag 0 inode chunk claims used block, inobt block - agno 0, bno 3024376, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16560, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16561, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16562, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16563, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16564, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16565, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16566, inopb 8 inode chunk claims untracked block, finobt block - agno 0, bno 16567, inopb 8 undiscovered finobt record, ino 132480 (0/132480) finobt ir_freecount/free mismatch, inode chunk 0/132480, freecount 8 nfree 14 undiscovered finobt record, ino 26250368 (0/26250368) finobt ir_freecount/free mismatch, inode chunk 0/26250368, freecount 6 nfree 10 out-of-order fino btree record 2 (24096000) block 0/4 undiscovered finobt record, ino 24096000 (0/24096000) finobt ir_freecount/free mismatch, inode chunk 0/24096000, freecount 56 nfree 42 out-of-order fino btree record 3 (24035840) block 0/4 undiscovered finobt record, ino 24035840 (0/24035840) finobt ir_freecount/free mismatch, inode chunk 0/24035840, freecount 34 nfree 30 out-of-order fino btree record 4 (23669696) block 0/4 undiscovered finobt record, ino 23669696 (0/23669696) finobt ir_freecount/free mismatch, inode chunk 0/23669696, freecount 19 nfree 15 out-of-order fino btree record 5 (24077120) block 0/4 undiscovered finobt record, ino 24077120 (0/24077120) finobt ir_freecount/free mismatch, inode chunk 0/24077120, freecount 5 nfree 29 out-of-order fino btree record 6 (23120576) block 0/4 undiscovered finobt record, ino 23120576 (0/23120576) finobt ir_freecount/free mismatch, inode chunk 0/23120576, freecount 63 nfree 35 out-of-order fino btree record 7 (23830208) block 0/4 undiscovered finobt record, ino 23830208 (0/23830208) out-of-order fino btree record 8 (23863040) block 0/4 undiscovered finobt record, ino 23863040 (0/23863040) finobt ir_freecount/free mismatch, inode chunk 0/23863040, freecount 41 nfree 37 out-of-order fino btree record 9 (24615808) block 0/4 undiscovered finobt record, ino 24615808 (0/24615808) finobt ir_freecount/free mismatch, inode chunk 0/24615808, freecount 11 nfree 25 out-of-order fino btree record 10 (23141440) block 0/4 undiscovered finobt record, ino 23141440 (0/23141440) finobt ir_freecount/free mismatch, inode chunk 0/23141440, freecount 39 nfree 53 undiscovered finobt record, ino 380800640 (0/380800640) finobt ir_freecount/free mismatch, inode chunk 0/380800640, freecount 55 nfree 53 bad starting inode # (1345164544 (0x0 0x502d9500)) in finobt rec, skipping rec out-of-order fino btree record 13 (24110912) block 0/4 out-of-order fino btree record 14 (24111616) block 0/4 out-of-order fino btree record 15 (24112576) block 0/4 out-of-order fino btree record 16 (24113152) block 0/4 out-of-order fino btree record 17 (24114496) block 0/4 out-of-order fino btree record 18 (24114624) block 0/4 out-of-order fino btree record 19 (24115328) block 0/4 out-of-order fino btree record 20 (24116096) block 0/4 out-of-order fino btree record 21 (24116544) block 0/4 out-of-order fino btree record 22 (24118336) block 0/4 out-of-order fino btree record 23 (24126464) block 0/4 out-of-order fino btree record 24 (24128064) block 0/4 out-of-order fino btree record 25 (24131392) block 0/4 out-of-order fino btree record 26 (24133568) block 0/4 out-of-order fino btree record 27 (24148352) block 0/4 out-of-order fino btree record 28 (24172608) block 0/4 out-of-order fino btree record 29 (24183232) block 0/4 out-of-order fino btree record 30 (24195008) block 0/4 undiscovered finobt record, ino 24195008 (0/24195008) out-of-order fino btree record 31 (24196864) block 0/4 undiscovered finobt record, ino 24196864 (0/24196864) out-of-order fino btree record 32 (24196928) block 0/4 undiscovered finobt record, ino 24196928 (0/24196928) out-of-order fino btree record 33 (24198592) block 0/4 undiscovered finobt record, ino 24198592 (0/24198592) out-of-order fino btree record 34 (24205888) block 0/4 undiscovered finobt record, ino 24205888 (0/24205888) out-of-order fino btree record 35 (26078272) block 0/4 undiscovered finobt record, ino 26078272 (0/26078272) out-of-order fino btree record 36 (26980736) block 0/4 undiscovered finobt record, ino 26980736 (0/26980736) out-of-order fino btree record 37 (26078272) block 0/4 undiscovered finobt record, ino 26078272 (0/26078272) agi_freecount 1830, counted 1831 in ag 0 agi_freecount 1830, counted 1792 in ag 0 finobt sb_ifree 53672, counted 53822 sb_fdblocks 72593062, counted 118052438 - 13:34:26: scanning filesystem freespace - 32 of 32 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree - 13:34:27: scanning agi unlinked lists - 32 of 32 allocation groups done - process known inodes and perform inode discovery... - agno = 15 - agno = 0 - agno = 30 no . entry for directory 132 no .. entry for directory 132 problem with directory contents in inode 132 cleared inode 132 data fork in ino 24098954 claims free block 3012367 data fork in inode 24099559 claims metadata block 16560 correcting nextents for inode 24099559 bad data fork in inode 24099559 cleared inode 24099559 - agno = 1 - agno = 16 - agno = 2 - agno = 17 - agno = 31 - agno = 3 - agno = 4 - agno = 5 - agno = 18 - agno = 6 - agno = 19 - agno = 20 - agno = 21 - agno = 7 - agno = 22 - agno = 8 - agno = 9 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - 13:34:34: process known inodes and inode discovery - 75200 of 75584 inodes done - process newly discovered inodes... - 13:34:34: process newly discovered inodes - 64 of 32 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - 13:34:34: setting up duplicate extent list - 32 of 32 allocation groups done - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 7 - agno = 2 - agno = 16 - agno = 19 entry "appdata" in shortform directory 128 references free inode 132 - agno = 24 junking entry "appdata" in directory inode 128 - agno = 4 - agno = 9 - agno = 29 - agno = 12 - agno = 15 - agno = 17 - agno = 8 - agno = 14 - agno = 20 - agno = 6 - agno = 5 - agno = 21 - agno = 22 - agno = 23 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 30 - agno = 31 - agno = 13 - agno = 3 - agno = 11 - agno = 18 - agno = 10 entry "_FAILED_Cops.S24E14.720p.HDTV.x264-2HD" at block 2 offset 136 in directory inode 18253611137 references non-existent inode 24195009 clearing inode number in entry at offset 136... entry "_FAILED_SpongeBob.SquarePants.S07E33A.DVDRip.XviD-OSiTV" at block 7 offset 3544 in directory inode 18253611137 references non-existent inode 24198644 clearing inode number in entry at offset 3544... entry "Frontline - S2022E05 - The Power of Big Oil (Part 1 - Denial) WEBDL-1080p.mkv" in shortform directory 24099558 references free inode 24099559 junking entry "Frontline - S2022E05 - The Power of Big Oil (Part 1 - Denial) WEBDL-1080p.mkv" in directory inode 24099558 entry "G3TVhmBtyJWc2jYn1F9mCE" in shortform directory 24112609 references non-existent inode 24196894 junking entry "G3TVhmBtyJWc2jYn1F9mCE" in directory inode 24112609 entry "Season 4" in shortform directory 33286526875 references non-existent inode 24196864 junking entry "Season 4" in directory inode 33286526875 entry "Season 6" in shortform directory 19327353921 references non-existent inode 26980788 junking entry "Season 6" in directory inode 19327353921 entry "Season 30" at block 0 offset 744 in directory inode 22548609161 references non-existent inode 24205941 clearing inode number in entry at offset 744... - 13:34:34: check for inodes claiming duplicate blocks - 75200 of 75584 inodes done Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - 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 - 13:34:36: rebuild AG headers and trees - 32 of 32 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 15 - agno = 30 - agno = 0 - agno = 31 - agno = 1 - agno = 2 - agno = 16 - agno = 3 - agno = 17 - agno = 4 rebuilding directory inode 18253611137 - agno = 5 - agno = 18 - agno = 19 - agno = 20 - agno = 6 - agno = 7 - agno = 21 bad hash table for directory inode 22548609161 (no data entry): rebuilding rebuilding directory inode 22548609161 - agno = 8 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 9 - agno = 27 - agno = 28 - agno = 10 - agno = 29 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 24126487, moving to lost+found disconnected inode 24128089, moving to lost+found disconnected dir inode 1073741992, moving to lost+found disconnected dir inode 5381947568, moving to lost+found disconnected dir inode 8589935755, moving to lost+found disconnected dir inode 9663851839, moving to lost+found disconnected dir inode 9663852755, moving to lost+found disconnected dir inode 10774420895, moving to lost+found disconnected dir inode 11811160276, moving to lost+found disconnected dir inode 12884902229, moving to lost+found disconnected dir inode 13958644114, moving to lost+found disconnected dir inode 16106128102, moving to lost+found disconnected dir inode 17184045731, moving to lost+found disconnected dir inode 19327354431, moving to lost+found disconnected dir inode 20401096825, moving to lost+found disconnected dir inode 22548579690, moving to lost+found disconnected dir inode 22548580327, moving to lost+found disconnected dir inode 23622320355, moving to lost+found disconnected dir inode 24696062143, moving to lost+found disconnected dir inode 27917287671, moving to lost+found disconnected dir inode 27917290437, moving to lost+found disconnected dir inode 28991030585, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 128 nlinks from 14 to 13 resetting inode 132 nlinks from 2 to 22 resetting inode 19327353921 nlinks from 8 to 7 resetting inode 18253611137 nlinks from 594 to 592 resetting inode 22548609161 nlinks from 35 to 34 resetting inode 33286526875 nlinks from 14 to 13 - 13:34:40: verify and correct link counts - 32 of 32 allocation groups done Maximum metadata LSN (4:2520548) is ahead of log (1:8). Format log to cycle 7. XFS_REPAIR Summary Fri Sep 9 13:36:32 2022 Phase Start End Duration Phase 1: 09/09 13:33:59 09/09 13:33:59 Phase 2: 09/09 13:33:59 09/09 13:34:26 27 seconds Phase 3: 09/09 13:34:26 09/09 13:34:34 8 seconds Phase 4: 09/09 13:34:34 09/09 13:34:34 Phase 5: 09/09 13:34:34 09/09 13:34:36 2 seconds Phase 6: 09/09 13:34:36 09/09 13:34:40 4 seconds Phase 7: 09/09 13:34:40 09/09 13:34:40 Total run time: 41 seconds done Quote Link to comment
trurl Posted September 9, 2022 Share Posted September 9, 2022 Start the array in normal mode and post new diagnostics Quote Link to comment
JorgeB Posted September 10, 2022 Share Posted September 10, 2022 Disk should mount now after startingin normal mode, check for a lost+found folder. P.S. for the future before rebuilding on top repair the emulated disk first, this way you have more options in case the file system repair causes some data loss. Quote Link to comment
jjooee Posted October 8, 2022 Author Share Posted October 8, 2022 On 9/10/2022 at 12:13 AM, JorgeB said: Disk should mount now after startingin normal mode, check for a lost+found folder. P.S. for the future before rebuilding on top repair the emulated disk first, this way you have more options in case the file system repair causes some data loss. By this you mean before removing the disk, start in maint. mode and go to the disk and run the XFS repair? Quote Link to comment
trurl Posted October 8, 2022 Share Posted October 8, 2022 4 hours ago, jjooee said: By this you mean before removing the disk, start in maint. mode and go to the disk and run the XFS repair? No Before reassigning the disk, start in normal mode. The disk will be missing, but it will be emulated, and if the emulated disk is mountable, you should be able to see it contents. If the emulated disk is unmountable, you can repair the emulated disk. The emulated disk is exactly what will be rebuilt. If rebuilding on top of the same disk, you may want to consider whether the contents of the physical disk are better than the repaired emulated disk. So, you have another option. 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.