I'm trying to setup my first Unraid server and I've been unable to create a disk on the array that isn't listed as "unmountable" due to an "unsupported partition layout." Here is an summary of the hardware and software I'm using:

- Unraid 6.11.2

- Seagate Ironwolf 4TB HDD (used as disk one in the array)

- WD Green 120 GB SSD (used as a cache pool device)

- 32 GB USB Drive with GUID support (used for running unraid)

 

I've attempted the following methods for resolving this issue according to other forum threads and posts online:

- I've attempted to format the HDD via the "format" option on a started array (with the relevant checkbox marked)
- I've formatted the HDD using Unassigned devices (with destructive mode enabled)

- I've cleared the HDD using Preclear
- I've SSH'd into Unraid and used fdisk to clear all partitions and create an empty table using GPT

- I've SSH'd into Unraid and used fdisk to clear all existing partitions and create a single new one with GPT as the table and xfs as the partition type

Despite taking all these different steps, I'm still stuck with the aforementioned error message when I start the array. Could you please help me resolve this issue?

Here is my diagnostic information.

raider-diagnostics-20221106-2028.zip

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

Thank you.  Helped me from beating my head against the wall again.

Thank you. I have a friend that's more or less wasted the entire weekend on this bug 🤣😭

Edited November 7, 20223 yr by syrupywaffles

Thanks so much for posting this, I too spent all weekend with this trouble too,  downgrading to 6.11.1  fixed it and I was able to format newly added drive

 

Just wanted to add to the thread that i experienced the same issue and spent alot of hours trying to solve this... hope this thread gets higher up on google now

Thanks soooo much. This weekend was pure pain

thank you! downgrading now - having same issue

I have the same issue with drives not being formatted. I started fresh with 6.11.2. How can I safely install 6.11.1 without losing all settings and passwords?

And since this is a big bug, can we expect a version 6.11.3 soon?

2 minutes ago, Rivanni said:

can we expect a version 6.11.3 soon?

Should be available very soon, possibly later today, in the meantime you can safely downgrade to v6.11.1 by downloading the zip and extracting all the bz* files and changes.txt to the flash drive overwriting existing files.

Same issue; thanks for pointing out the solution.  Glad Google is still working today.

Bummer... I just upgraded to 6.11.2 last night and attempted a new disk install... same issue. Unsupported partition layout.  

 

While it's easy to say downgrade--for those of us with a mature system, it's not so easy to just shutdown  

 

I'll be waiting for 6.11.3.

I also had the same issue, but with replacing a smaller disk with a bigger one.

I ended downgrading but the issue did not go away and started the array and replaced the data in the new disk using the parity.

The only option the system gave me was formating the new disk.

Afterwards the system worked ok but I lost what I had in the disk that was replaced. I have it and I looked what was in it mounting it and it's just Linux ISOs and stuff that is easyly replaceble.

Do I have to do anything special, like run a parity check or something so the system is not inconsistent?

 

Update:

 

I tried to update to 6.11.3 and the machine would not boot, the usb was not recognized and I had to download a backup from Unraid and look for a new usb drive.

 

After this I was able to upgrade to 6.11.3

 

Running a parity check and finding out many errors.

 

Edited November 9, 20223 yr by acastellab

On 11/7/2022 at 6:06 AM, syrupywaffles said:

Thank you. I have a friend that's more or less wasted the entire weekend on this bug 🤣😭

Yikes, me too, almost lost 10Tb of data because of this bug!

6.11.3 fix my issue.

14 hours ago, TheBrian said:

6.11.3 fix my issue.

I should have been more patient and waited...

I apparently lost data because of this bug. I replaced a 2tb with a 14 tb and now the data is gone. I still have the old 2tb disk and have downgraded to 6.9. What can I do to fix this? 

 

Edit: So I thought I would just mount the old drive and write the files back to the new drive... I cannot mount the old drive via usb, I get an invalid super block error. The drive is formatted xfs. If I put the disk back into the system via a sata connection I am able to mount it via the unassigned devices plugin but cant when connected via usb. Any ideas here?

Edited November 13, 20223 yr by Syco54645

58 minutes ago, Syco54645 said:

I apparently lost data because of this bug. I replaced a 2tb with a 14 tb and now the data is gone. I still have the old 2tb disk and have downgraded to 6.9. What can I do to fix this? 

You don't lose data, just upgrade Unraid and repeat the rebuild, unassign the disk, start array, stop array, re-assign the disk, start array to rebuild.

1 minute ago, JorgeB said:

You don't lose data, just upgrade Unraid and repeat the rebuild, unassign the disk, start array, stop array, re-assign the disk, start array to rebuild.

 

That did not work for me, I had no option to rebuild, only format. The drive is completely empty. It seems the only route forward is copying the data from the old xfs drive over to the array.

6 minutes ago, Syco54645 said:

That did not work for me, I had no option to rebuild, only format.

 

6 minutes ago, Syco54645 said:

unassign the disk, start array, stop array, re-assign the disk, start array to rebuild.

 

That is what you should have done, formatting is never part of a rebuild, now and if you still have the old disk, do a new config wit the old disk (Tools -> New config), re-sync parity, then replace the disk.

1 minute ago, JorgeB said:

unassign the disk, start array, stop array, re-assign the disk, start array to rebuild.

I did exactly that and had no option to rebuild, it showed only the option to format. 

4 minutes ago, JorgeB said:

That is what you should have done, formatting is never part of a rebuild, now and if you still have the old disk, do a new config wit the old disk (Tools -> New config), re-sync parity, then replace the disk.

Why not just use the old disk and issue the following command. This would avoid having to do a parity resync and fat fingering the new config setup. Not to mention I will maintain parity protection through this process.

rsync -rav /mnt/disks/old-disk-12 /mnt/disk12

 

Edited November 13, 20223 yr by Syco54645

You can also do that, but add an end slash to the source path or it will create a folder called old-disk-12 on destination:

 

rsync -av /mnt/disks/old-disk-12/ /mnt/disk12