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.

Fix File System

Featured Replies

Hi,

 

I recently swapped a harddrive that died with a new drive.

 

The contents were emulated and a disk rebuild was done. The drive was showing as unmountable and asking for a format.

 

I was advised to not format under any circumstances, and let the rebuild complete.

 

The rebuild is complete but Disk 3 (the new disk) is still unmountable. I did the check file system and got the following:

 

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero 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
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - 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 = 4
        - agno = 3
        - agno = 5
        - agno = 6
        - agno = 2
        - agno = 7
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...
Maximum metadata LSN (1:463638) is ahead of log (1:2).
Would format log to cycle 4.
No modify flag set, skipping filesystem flush and exiting.

 

The documentation say if I am not sure what this means, I should ask before doing a fix.

 

Am I safe to click Fix?

 

Thank you, and sorry if I am being overly cautious on this!

Solved by itimpi

  • Community Expert
  • Solution

a rebuild never clears the unmountable status.   If that was the status of the emulated drive then it will also be the status of the rebuilt drive.   Normally we recommend doing the check filesystem before the rebuild.
 

So yes you need to do the fix.    After doing that it should mount when the array is restarted in Normal mode.

  • Author

Thank you, appreciate it. I will do the fix and see how I go.

 

I thought I had done things in an odd order! Learned for next time though.

  • Community Expert
17 minutes ago, serhan said:

I thought I had done things in an odd order! Learned for next time though

If the old drive really died then the order was probably not important.   The reason for starting with trying to repair the emulated disk first is that if that does not work well then the old disk is often usable for data recovery purposes.

  • Author

I believe we are all up and running now, looks like smooth sailing.

 

Thanks for the help. This community is always great.

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.

Guest
Reply to this topic...

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.