September 27, 20241 yr Hi, there was an outage and after restart unraid in my Data DISK (I have an array with a 6tb Disk Data and a 6tb Disk Parity) shows the following message: "unmountable unsupported or no file system. ". After testing with the -nv parameterss hows the following: Phase 1 - find and verify superblock... - block cache size set to 1096048 entries Phase 2 - using internal log - zero log... zero_log: head block 1767711 tail block 1767707 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... sb_fdblocks 718652496, counted 728872128 - 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 - 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 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:1767755) is ahead of log (1:1767711). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Fri Sep 27 11:12:12 2024 Phase Start End Duration Phase 1: 09/27 11:11:46 09/27 11:11:46 Phase 2: 09/27 11:11:46 09/27 11:11:46 Phase 3: 09/27 11:11:46 09/27 11:12:00 14 seconds Phase 4: 09/27 11:12:00 09/27 11:12:00 Phase 5: Skipped Phase 6: 09/27 11:12:00 09/27 11:12:12 12 seconds Phase 7: 09/27 11:12:12 09/27 11:12:12 Total run time: 26 seconds What can I do now?
September 27, 20241 yr Community Expert Run it again without -n or nothing will be done, and if it asks for -L use it.
September 27, 20241 yr Author 37 minutes ago, JorgeB said: Run it again without -n or nothing will be done, and if it asks for -L use it. without -n : Phase 1 - find and verify superblock... - block cache size set to 1096048 entries Phase 2 - using internal log - zero log... zero_log: head block 1767711 tail block 1767707 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.
September 27, 20241 yr Author 7 hours ago, JorgeB said: With -L ..... 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 718652496, counted 728872128 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 2 - agno = 0 - agno = 3 - agno = 4 - agno = 5 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... Maximum metadata LSN (1:1767795) is ahead of log (1:2). Format log to cycle 4. done And now?
September 27, 20241 yr Community Expert Solution Start in normal mode and the disk should mount again.
September 27, 20241 yr Author 2 hours ago, JorgeB said: Start in normal mode and the disk should mount again. Thank you very much!!! Everything seems to be correct now and it appears that I have not lost any data. Why could this happen? Can I trust in this Disk? The smart say "healthy"....
September 28, 20241 yr Community Expert 11 hours ago, bmwjavier said: Can I trust in this Disk? You didn't post a SMART report, but this is usually just a filesystem problem, most often caused by an unclean shutdown.
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.