March 28, 20179 yr 4 minutes ago, JGKos said: from the options box -v /dev/md3 Don't add in the /dev/md3 That's why its failing vs why it worked before: 5 minutes ago, JGKos said: from the options box -nv
March 28, 20179 yr Author ...its always something simple thanks output: Not available Phase 1 - find and verify superblock... - block cache size set to 2666096 entries Phase 2 - using internal log - zero log... zero_log: head block 513384 tail block 513014 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.
March 28, 20179 yr 1 minute ago, JGKos said: ...its always something simple thanks output: Not available Phase 1 - find and verify superblock... - block cache size set to 2666096 entries Phase 2 - using internal log - zero log... zero_log: head block 513384 tail block 513014 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. Were you adding it or did unRaid populate it like that after the first check? If the latter, then you are the proud discoverer of a bug in the system
March 28, 20179 yr Author no bug here, just over reading the guide... -n returns to options field after each try i will perform the suggestions try to mount file system to replay log: I have tried this, system hangs run the -L option to destroy log
March 28, 20179 yr 2 minutes ago, JGKos said: no bug here, just over reading the guide... -n returns to options field after each try i will perform the suggestions try to mount file system to replay log: I have tried this, system hangs run the -L option to destroy log Yeah...
March 28, 20179 yr Author -L output: Not available 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... freeblk count 5 != flcount 6 in ag 3 Metadata corruption detected at xfs_agf block 0x74704441/0x200 flfirst 118 in agf 2 too large (max = 118) agi unlinked bucket 63 is 16759103 in ag 2 (inode=2164242751) sb_icount 126528, counted 70528 sb_ifree 296, counted 5721 sb_fdblocks 41520637, counted 42557665 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 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 ... disconnected dir inode 2164242751, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 136 nlinks from 2 to 3 resetting inode 2164242751 nlinks from 0 to 2 Maximum metadata LSN (2:513380) is ahead of log (1:2). Format log to cycle 5. done -v should be my next move? Edited March 28, 20179 yr by JGKos
Archived
This topic is now archived and is closed to further replies.