nraygun Posted February 17, 2023 Share Posted February 17, 2023 Crapola! I saw this morning that the appdata backup plugin didn't complete. Looks like it couldnt stop the docker containers. I tried to stop them but they wouldn't. I then tried to kill off any zombie processes. I could not kill them nor their parents. I then decided to reboot the server. I can't tell at what stage the errors started, but it's stuck at a "Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0f42f168 dinode". It then says to run xfs_repair and shows the first 128 bytes of corrupted metadata buffer. Looks like it's sdb1 that has the problem. The situation looks similar to what's going on in the link below. Just want to confirm the right steps to recover. 1. Power cycle the server 2. If it comes up, then do the test and repair here: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui (not sure what to do if it doesn't come back up) Is this correct or should I do something else? Am I have a major server problem here or are XFS corruptions fairly common? PS - I can't provide logs with the server in this state. I Quote Link to comment
Solution JorgeB Posted February 17, 2023 Solution Share Posted February 17, 2023 Yes, just run xfs_repair using the GUI, without -n or nothing will be done and if it asks for -L use it. Quote Link to comment
nraygun Posted February 17, 2023 Author Share Posted February 17, 2023 Thanks @JorgeB! Looks like drive in question was the cache drive. I ran the repair and it completed. See below. It mentions something about lost+found but I don't see that in my Cache drive. Am I good to go? Also, I've never seen this before. Is this a common thing? 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 and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - 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 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Quote Link to comment
JorgeB Posted February 18, 2023 Share Posted February 18, 2023 12 hours ago, nraygun said: It mentions something about lost+found but I don't see that in my Cache drive. That's good new, you should be all set. 1 Quote Link to comment
Recommended Posts
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.