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.

Unmountable Disk Present

Featured Replies

Server was working perfectly fine. Now it shows 'Unmountable disk present'. I believe 1 cache disk and 1 data disk are having issues.
Data disk 2 is showing as not installed.
Have only tried reboot till now. Didn't want to break anything by trying other stuff

unmhn-diagnostics-20231218-1645.zip

  • Community Expert

There's a missing pool device, try checking/replacing cables.

  • 2 weeks later...
  • Author

I disconnected and reconnected all the cables. Seems to have solved the cache pool ssd issue. But 1 disk is unable to mount. unmhn-diagnostics-20231228-0003.zip

  • Community Expert

Handling of unmountable array disks is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

  • Author

Thanks for the reference doc. I was following it. I successfully checked and repaired the drive. The following was the output

 

After Checking

 

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
        - agno = 8
        - agno = 9
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 5
        - agno = 1
        - agno = 6
        - agno = 2
        - agno = 7
        - agno = 4
        - agno = 3
        - agno = 8
        - agno = 9
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.

 

 

After repairing with `-L` option

 

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 and 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
        - agno = 8
        - agno = 9
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 6
        - agno = 3
        - agno = 4
        - agno = 2
        - agno = 5
        - agno = 7
        - agno = 1
        - agno = 8
        - agno = 9
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:2452269) is ahead of log (1:2).
Format log to cycle 4.
done

 

 

Since I didn't see any errors, I stopped the array, and started in normal mode.
Now its showing `Parity-Sync/Data-Rebuild in progress.` . I hope its the right thing

  • Community Expert

Looks like you successfully repaired the emulated disk2 (which was disabled), and the system is now rebuilding the contents of that emulated disk onto the physical disk2..

  • Author

Not sure what happened, but my disk 2 has gone back to being disabled and emulated.

I'm not sure whether `Parity-Sync/Data-Rebuild in progress.` got complete. But now its showing as Read-check paused.

unmhn-diagnostics-20231229-1754.zip

  • Community Expert

Disk2 dropped offline, looks more like a power/connection issue, check/replace cables and post new diags, also replace cables for the cache SSD.

  • Author

I retried after reconnecting and did a repair with '-L'.
But this time after stopping and starting the drive, no `Parity-Sync/Data-Rebuild` is shown. Drive is still disabled

 

This was the output after '-L'

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 and 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
        - agno = 8
        - agno = 9
        - 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
        - agno = 6
        - agno = 4
        - agno = 5
        - agno = 7
        - agno = 8
        - agno = 9
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 (7:0) is ahead of log (1:2).
Format log to cycle 10.
done

 

  • Community Expert
2 hours ago, mhn_10 said:

But this time after stopping and starting the drive, no `Parity-Sync/Data-Rebuild` is shown. Drive is still disabled

You must do a rebuild.

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.