April 20, 20242 yr Community Expert After seeing one of my two data drives listed as 'unavailable, no file system'. I shut down the server to check it later this morning. I'm going off of info from the Unraid docs for 'Checking a file system' for xfs drives. I restarted the server, saw no obvious errors, and started the array in maintenance mode, and ran the check file system status. I am not sure what I am looking for in the test log. Could someone look at this and tell me if I should try to repair or do any other operations? Thanks in advance! xfs_repair status: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_icount 3776, counted 28288 sb_ifree 52, counted 290 sb_fdblocks 3392758777, counted 1374641594 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 7 - agno = 4 - agno = 5 - agno = 6 - agno = 1 - agno = 2 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 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 20, 20242 yr Community Expert You just ran a check - not a repair. To do any repair you need to run without the -n option. If it asks for it you should add the -L option. After that the disk should mount when you restart the array in normal mode.
April 20, 20242 yr Author Community Expert I don't know what the check uncovered, if anything. I didn't want to repair if I should take some other steps or other procedures resulting info from the check logs. Is there anything suspicious in the log I don't see before I run repair? Thx. (I probably should have titled this need help understanding 'check' results) Edited April 20, 20242 yr by YaSo
April 20, 20242 yr Community Expert Solution That is a clean looking check with no errors reported so I would expect all data to reappear after running the repair.
April 20, 20242 yr Author Community Expert Thanks, had to run out before running the repair, which finished quickly. All SEEMS to be alright, videos in previously missing folders are all back and play on the PC just fine. (docs said the repair could take hours, it took only a minute or less.) Maybe a power outage caused the glitch? I saw the server was at the login screen one day when I came home from work a few days ago, wondered about it. We get power outages here every so often for a few seconds at a time, and I have my main PC and USB drives on a UPS. I'll have to plug the server into that too. Edited April 20, 20242 yr by YaSo
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.