AnarkZ

Right, but how do you make that decision w/o understanding what the log is telling you. If the corruption is minor then running xfs repair seems sensible, if it is going to nuke a bunch of files then maybe trying another recovery method is preferable. I'm looking to understand what the log is reporting so I can make the best decision. Maybe there are some resources I could be pointed to? For example, the log reports the following: entry "592b2244-d37c-4dfc-b733-d9e625fea3fc.vhdx" in shortform directory 6442553041 references free inode 6442553043 would have junked entry "592b2244-d37c-4dfc-b733-d9e625fea3fc.vhdx" in directory inode 6442553041 Is this a file it had identified as corrupt, and is it the only one? Is the log telling me that when I run the repair that it will attempt to repair the file or nuke it? I mentioned I've done this once before w/o knowing what was going to happen. Some files ended up in lost&found and some where just outright gone. Is it possible to identify what will happen to corrupted files when the repair is attempted? Any insights would be appreciated.

So I'm looking for some help deciphering what this XFS repair log is telling me. While moving some files between drives with Krusader I got an error saying it couldn't find the file I was moving and went to check the array and found that Drive 3 was Unmountable. I then stopped the array, restarted in maintenance mode, and ran XFS repair -nv. Below you will find the output as well as the diagnostics.zip pre-reboot. This has happened to me once before, and I blindly attempted to repair the drive using XFS repair w/o understanding what it was going to do and lost a bunch of files. Would someone be able to help me to understand what the log is telling me and how to identify what files are corrupt and what XFS repair will do with them when run w/o the -nv flag. Unraid Version 6.9.2 2021-04-07 Thanks in advance, AnarkZ brimstone-diagnostics-20221213-1145.zip Unraid Disk3 XFS Repair Log.txt