Noticed a disk was offline. Shut it down, verified all connections and started it back up. Met with Unmountable: wrong or no file system. Nearly every reboot has caused a parity re read lately so that is not good timing.

Also unable to start in maintenance mode. Check the box, hit start and it just reloads the page.

Got it into maintenance mode after a couple reboots. Disk 7 xfs check says

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.

Clicking fix results in

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 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.

tower-diagnostics-20260702-1337 2.zip

Edited Thursday at 07:15 PM2 days by jmztaylor

You will need to zero the log, it's the only option to try and fix the filesystem, and most often it is not a problem.