rutherford Posted January 27 Share Posted January 27 (edited) Had a the server hard crash, and I just wanted to make sure I was on the right track here: https://forums.unraid.net/bug-reports/stable-releases/691-metadata-corruption-detected-at-xfs_dinode_verify-r1369/ just wanna make sure I'm on the right track here. thanks! https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui - Settings -> Docker -> Host access to custom networks: Disabled - Use custom network "proxynet" for ALL docker instances (before: host + bridge + proxynet) - might be unrelated mayorgoodway-diagnostics-20240127-1116.zip Edited January 27 by rutherford Quote Link to comment
JorgeB Posted January 28 Share Posted January 28 Check filesystem on disk6, run it without -n. 1 Quote Link to comment
rutherford Posted January 28 Author Share Posted January 28 thanks for getting back JorgeB. Ran that, didn't see any smoking guns: Spoiler 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 - 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 = 1 - agno = 4 - agno = 5 - agno = 7 - agno = 8 - agno = 6 - agno = 9 - agno = 11 - agno = 10 - agno = 2 - agno = 12 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
itimpi Posted January 28 Share Posted January 28 That should have cleared the corrupt metadata on disk6 that was mentioned at the end of your screenshot. When you start the array in normal mode does the drive mount OK. 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.