April 9, 20251 yr Recently upgraded an HDD in my array to a larger capacity drive. Everything rebuilt just fine and parity is good. Then, updated to 7.0.1 Then, noticed this error on the HDD that I upgraded? Tried stopping and restarting the array but that didn't fix it. Diags attached. Any ideas how to fix? Thank you! taflix-unraid-diagnostics-20250408-2317.zip
April 10, 20251 yr Author ran check ran fix attached results ran check again: 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 (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 = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - 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. I think it's fixed now? Thank you JorgeB. check file system.txt Edited April 10, 20251 yr by taflix
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.