SecretAgent-X9

Ok I thought I might need to run it with the -L flag. I just wanted to make sure I wasn't going to screw anything up by doing so. I just ran xfs-repair -L and after finishing, the disk is now mounting when starting the array. Thank you very much!

Hello, I am running Unraid 6.12.8 and I am getting a Unmountable: unsupported or no filesystem error on one of my disks after rebooting to install a new piece of hardware. I did a clean shutdown of my server via the WebGUI to install a 10 gig PCIe NIC in my server. The system seemed to boot fine after installing the NIC and the new hardware was recognized. I proceeded to assign the new 10 gig NIC to eth0 via settings > network-settings which prompted me to perform another reboot. I did the second reboot and was able to access the WebGUI via the new NIC. After that second reboot is when I noticed Disk 6 in my pool was not showing it's utilization on the dashboard and is saying "Unmountable: unsupported or no filesystem" when looking at Main > Array Devices. I did third reboot thinking it might just be a glitch but it did not help resolve the issue. After this I performed a SMART short test on the disk which did not return any errors and also started the array up in maintenance mode to run xfs-repair on the disk via the GUI. Here is the output of xfs-repair -w Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - 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 - agno = 21 - agno = 22 - agno = 23 - 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 = 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 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 (2:382) is ahead of log (0:0). Would format log to cycle 5. No modify flag set, skipping filesystem flush and exiting. and here is the output of xfs-repair with no flags Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. I am looking for advice on how to further troubleshoot and if possible recover this disk in my array. Would it be a good idea to run xfs-repair with the -L option? Attached is my system diagnostics. Thank you! vault42-diagnostics-20240817-1715.zip