flip

Members
  • Posts

    12
  • Joined

  • Last visited

flip's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The array just came back online Thanks for all the help everyone
  2. xfs_repair status: 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... - 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 = 3 - agno = 1 - agno = 2 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:96) is ahead of log (1:2). Format log to cycle 4. done
  3. 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.
  4. With maintenance selected Filesystem check gave me this for and output 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 - 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 = 3 - agno = 2 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.
  5. I went ahead and booted in maintenance and ran a check on disk 7 that found no errors I replaced disk 1 with no issue I go to start the array it still claims disk 7 unmountable no file system and hangs on mounting cache drive Any help would be greatly appreciated tower-diagnostics-20191006-2049.zip
  6. OKtower-diagnostics-20191004-1200.zip let's try this again
  7. I attached the zip I also rebooted and placed a drive for device one tower-diagnostics-20191004-0225.zip
  8. I have no idea why it isn't there honestly there's a drive in there. Would that be causing the problem?
  9. Thanks I went ahead and followed the instructions I'm still at the same place
  10. Thanks for the reply I didn't remove the failed disk from the array. The drive is new the original was 2tb and the replacement is 4 array has two parity drives that are 4tb I have restarted twice now. I'm not sure where to start command line wise to check progress
  11. I had my Disk 7 fail I replaced it and upon attempting to bring the array back online it appears to freeze. It's been sitting for over an hour and the system log hasn't logged anything new in about the hour as well
  12. I'm not sure if this is possible I have a server with two separate NICs they are both on separate networks one subnet 192.168.1x and the other 10.0.0.X Is there a way to setup a share that would be for say only the 10.0.0.X subnet? Thanks for taking the time to read my question