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.

Replaced disk shows Unmountable: Unsupported partition layout

Featured Replies

Hi,

 

I replaced a non-parity 1TB disk in my server with a 4TB one (Disk 2 in diagnostics). Now the disk is showing up as "Unmountable: Unsupported partition layout".

 

When I remove the disk from the array and leave the Disk 2 slot empty and start the array, all the data is there, but when I add the disk again and start the array, none of the data that is supposed to be on Disk 2 shows up. (Parity data should be valid with previous drive since parity check finished 6 days ago with 0 errors)

 

I've already let the data rebuild happen twice now and after the data rebuild is done, still none of the data shows up.

 

I've just replaced the sata cable to the new disk (since it was under slight tention before), with a brand new cable and also used a different sata port on motherboard but that didn't make a difference.

 

Before all of this went down, I upgraded Unraid from version 6.9.2 directly to 6.11.2. I do have a backup from the flashdrive right before I did that.

 

The server is running an GitLab instance. I do not have a full proper backup. I still have the previous drive and none of the data regarding GitLab has been changed since replacing the drive, so grabbing data from the previous drive and manually adding it back could be an option?

 

I am uncertain what to do next.

 

Screenshots

 

With Disk 2 assigned

chrome_2022-11-06_14-26-24.thumb.png.a74b198007e7c70c6cedb87456f844ac.png

 

Without Disk 2 assigned

chrome_2022-11-06_14-22-05.thumb.png.2e888536faa399d7b97c44c45222efe9.png

 

with_disk2_neon-diagnostics-20221106-1419.zip without_disk2_neon-diagnostics-20221106-1420.zip

Edited by Zandor300

Solved by JorgeB

  • Community Expert
  • Solution

It's a bug with the latest release, for now suggest downgrading to v6.11.1 to partition the disk, you can then upgrade back if you want.

  • Author

@JorgeB How do I downgrade to 6.11.1? Update OS tool only shows previous OS as 6.9.2 since that is what I upgraded from.

  • Community Expert

Downgrading to v6.9.2 will also work, but you can download the v6.11.1 zip and extract all the bz* files to the flash drive replacing existing ones, then reboot.

  • Author

I simply downgraded back to 6.9.2 and everything seems to be back to normal. Data rebuilding to Disk 2 as we speak while data is available and GitLab has started.

 

@JorgeB Thank you for you insights!

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.