April 26Apr 26 Hey Everyone -I had an unclean shutdown and 2 of my disks are showing "unmountable".Diagnostics are attached.How should I fix this?Thanks! rraid-diagnostics-20260426-1411.zip
April 27Apr 27 Author 1 hour ago, trurl said:Check filesystem on disk19 from the webUI and post the output.d5:Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.d19:Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.
April 27Apr 27 Author 3 hours ago, trurl said:Click the FIX button, post the outputd5:Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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.d19:Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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.
April 27Apr 27 Author 6 hours ago, JorgeB said:Click the destroy log option.Logs have been zero'ed.Is that it? Do I now stop the array and restart in normal mode?
April 27Apr 27 Author 57 minutes ago, JorgeB said:If it showed "fixed" yes.I tried stopping and restarting array but it seems to be stuck at this:"Array Stopping•Retry unmounting user share(s)..."
April 27Apr 27 Community Expert Make sure you don't have an SSH/terminal window opened to a mounted path
April 27Apr 27 Author 2 minutes ago, JorgeB said:Make sure you don't have an SSH/terminal window opened to a mounted pathi dont. what should i do to get this unstuck?
April 27Apr 27 Author I tried rebooting as it didnt seem like there were many other options.But d5 & d19 are still showing 'device disabled, contents emulated'.What should I do?
April 27Apr 27 Author d5:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - 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 - 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 - agno = 5 - agno = 6 - agno = 9 - agno = 10 - agno = 12 - agno = 13 - agno = 7 - agno = 4 - agno = 14 - agno = 15 - agno = 17 - agno = 18 - agno = 16 - agno = 8 - agno = 11 - agno = 19 - agno = 20 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... No modify flag set, skipping filesystem flush and exiting.d19:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 7 - agno = 4 - agno = 5 - agno = 0 - agno = 6 - agno = 14 - agno = 8 - agno = 9 - agno = 13 - agno = 10 - agno = 2 - agno = 15 - agno = 11 - agno = 12 - agno = 16 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... No modify flag set, skipping filesystem flush and exiting.
April 28Apr 28 Author 59 minutes ago, trurl said:Click the FIX buttonThere is no "fix" option, just a "check" option since there doesn't seem to be any corruption:
April 28Apr 28 Community Expert 5 hours ago, JorgeB said:Post new diags after array start.Start in normal not maintenance mode
April 28Apr 28 Community Expert Emulated disks are mounting; check if the contents look correct. Also, look for a lost+found folder.
April 28Apr 28 Author Sorry, I'm not sure I know how do to that.Could you provide more in-depth instructions?Thanks!
April 28Apr 28 Community Expert Don't see any lost+found in user shares.Fortunately the disks needing repair had plenty of free space for repair to work in. A few of your disks are very full and repair might not have been as successful with those.Unrelated, your domains and system shares are on the array.Ideally, Docker/VM related shares - appdata, domains, system - would have all files on a pool with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.Both of those shares are configured to put new files on cache_ssd, but those shares existing files on the array will not be moved because they have no Mover action because they have no Secondary.And nothing can move open files. You have to disable Docker and VM Manager in Settings before those shares can be moved.
April 28Apr 28 Author Thanks again.What are the next steps I should take from here to get back up-and-running?Thanks!
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.