treywarren Posted September 28, 2017 Share Posted September 28, 2017 (edited) I feel like I'm chasing gremlins. The first problem I noticed was when trying to update docker programs there would be an error and I could no longer open or update them. Now I can only get the UI to load for safe mode. Drives look ok on the dashboard. Attached are log files and a bad picture of what is displayed when I mount the drives. Not sure if it is being picked up in the logs. tower-diagnostics-20170928-1058.zip Edited September 28, 2017 by treywarren Quote Link to comment
Squid Posted September 28, 2017 Share Posted September 28, 2017 From the diagnostics, it looks like you started the array in maintenance mode.. Can you start it normally, then grab another diagnostics from the command line. Based upon the pics though, it would appear that disk3 has corruption on it though, and you'll need to Check Disk Filesystem Quote Link to comment
treywarren Posted September 28, 2017 Author Share Posted September 28, 2017 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x575428d9/0x200 flfirst 118 in agf 1 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_fdblocks 51463847, counted 52201682 - 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 - 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 = 3 - agno = 2 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. Thanks, that definitely seems to be the case. This was done before mounting then I pulled this log after mounting (cannot access webUI now). Any suggestions from here? tower-diagnostics-20170928-1326.zip Quote Link to comment
Squid Posted September 28, 2017 Share Posted September 28, 2017 Rerun it with the modify flag (remove the -n from the options) Quote Link to comment
treywarren Posted September 28, 2017 Author Share Posted September 28, 2017 I can’t seem to mount it so is -L my only option? Quote Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Quote Link to comment
Squid Posted September 28, 2017 Share Posted September 28, 2017 Usually no loss in data by using -L Quote Link to comment
treywarren Posted September 28, 2017 Author Share Posted September 28, 2017 Thanks for all the help, that seems to have worked without any issues! 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.