Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Existing drive became unmountable after restarting array

Featured Replies

I had a drive fail, I stopped the array and in order to find which drive has failed I had to yank out the drives. I replaced the drive that had failed and restarted the array. while doing so, two of my drives became unmountable. I went through file system status check, but I cannot decipher what the issues are.

Can you guys help me what I need to do? when I restart the array, those drives are still unmountable...

 

Phase 1 - find and verify superblock...
        - block cache size set to 3047792 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 1653481 tail block 1653477
        - scan filesystem freespace and inode maps...
sb_fdblocks 221746390, counted 222241018
        - 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 = 2
        - agno = 1
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Tue Nov  7 20:22:57 2017

Phase		Start		End		Duration
Phase 1:	11/07 20:22:40	11/07 20:22:40
Phase 2:	11/07 20:22:40	11/07 20:22:42	2 seconds
Phase 3:	11/07 20:22:42	11/07 20:22:56	14 seconds
Phase 4:	11/07 20:22:56	11/07 20:22:56
Phase 5:	Skipped
Phase 6:	11/07 20:22:56	11/07 20:22:57	1 second
Phase 7:	11/07 20:22:57	11/07 20:22:57

Total run time: 17 seconds

 

 

Phase 1 - find and verify superblock...
        - block cache size set to 3047792 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 1368830 tail block 1368826
        - scan filesystem freespace and inode maps...
sb_fdblocks 244072797, counted 244567425
        - 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 = 1
        - agno = 2
        - agno = 3
        - agno = 0
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Tue Nov  7 20:27:19 2017

Phase		Start		End		Duration
Phase 1:	11/07 20:27:18	11/07 20:27:18
Phase 2:	11/07 20:27:18	11/07 20:27:18
Phase 3:	11/07 20:27:18	11/07 20:27:19	1 second
Phase 4:	11/07 20:27:19	11/07 20:27:19
Phase 5:	Skipped
Phase 6:	11/07 20:27:19	11/07 20:27:19
Phase 7:	11/07 20:27:19	11/07 20:27:19

Total run time: 1 second

 

 

  • Community Expert

You need to remove the no modify flag (-n) for xfs_repair to try to fix the filesystem.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.