johnzimm Posted June 2 Posted June 2 (edited) Before I make things worse... my disk number one is showing this... "unmountable: unsupported or no file system". Do I click on the box "yes I want to do this" under "Format will create a file system in all Unmountable disks"? Will this allow the parity to re-populate drive one? Thank you tower-diagnostics-20240602-1802.zip Edited June 2 by johnzimm Added diagnostics file Quote
Kilrah Posted June 2 Posted June 2 NO, this would erase the drive AND its parity representation. You need to check filesystem Quote
johnzimm Posted June 2 Author Posted June 2 48 minutes ago, Kilrah said: You need to check filesystem Thank you... I get the following... see below. What would I do next? 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... - 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 - 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 = 2 - agno = 1 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 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... Maximum metadata LSN (58:2620057) is ahead of log (58:2619677). Would format log to cycle 61. No modify flag set, skipping filesystem flush and exiting. Quote
Solution johnzimm Posted June 3 Author Solution Posted June 3 I ended up doing another check but this time with a -L in the field below and it fixed it. Thank you Kilrah Quote
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.