December 28, 20169 yr it is not mounting the disk 2 in my array. what do i need to do? also "fix Common Problems says that the files system has error(no file system(32)) thanks for any help i can get. i tried to run the xfs_repair - -n "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 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_ifree 87141, counted 87198 sb_fdblocks 126402629, counted 126476744 - 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 - 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 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 425664282, would move to lost+found Phase 7 - verify link counts... would have reset inode 425664282 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting." blank "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." tower-diagnostics-20161227-2159.zip tower-smart-20161227-2201.zip tower-smart-20161227-2202.zip tower-smart-20161227-22021.zip
January 6, 20179 yr Community Expert No, but file system corruption is mostly caused by power cuts/unclean shutdowns.
Archived
This topic is now archived and is closed to further replies.