Unraid 7.2.0-beta.2 was installed on nearly 4000 systems in the last month! Thanks to everyone who tested and provided feedback.

Unraid 7.2.0-beta.3 is now available! See all the details in the release notes (search the page for -beta.3)

Note that some plugins may have visual issues in this release, please give plugin authors time to make adjustments. Plugin authors, please see this post describing how to update your plugins to make them responsive.

This is BETA software. Please use on test servers only.

Upgrade instructions are available in the docs.

 

This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic in the Prereleases board. Be sure to include your diagnostics.zip.

Up and running. Thanks.

Just want to mention this. Maybe not something that needs a separate bug report. Seen in beta.2 too. Brave browser. Shields down.
Tooltips get misaligned if I scroll down on the page. No scrolling, they show correcly.

Edited September 20, 2025Sep 20 by Niklas

Any info about this item in the changelog? Resolved some issues with existing 1MiB aligned partitions

My emmc storage didnt show up, is there something I am supposed to be doing something like downloading a plugin?

Also worth noting with the Kernel version update, this is likely a useful improvement/fix from Beta 3 for folks having issues with NVMe drives dropping:

3 hours ago, sittingmongoose said:

My emmc storage didnt show up, is there something I am supposed to be doing something like downloading a plugin?

Could you create a new thread and post diagnostics so it can be review to see If additional parts are needed.

all's right for my set-up !

7 hours ago, Hammy Havoc said:

Any info about this item in the changelog? Resolved some issues with existing 1MiB aligned partitions

There's a long-standing issue caused by Unraid accepting disks partitioned on sector 2048 (1MiB MiB aligned) for some time now; the default for Unraid with HDDs is sector 64. This was introduced several years ago when SSDs started being partitioned on sector 2048 to improve performance. This has been causing issues for users since then, because if you have, for example, an 8TB parity partitioned on sector 2048, and then try to replace a 4TB array disk with another 8TB, Unraid would complain that the new disk is larger than parity, because it would partition it on sector 64, so the partition would be slightly larger than parity's. It's a corner case but could be an issue for those users, especially if the disk was disabled, requiring a parity swap to replace it.

Before Unraid 7.1.x, there was a workaround, if you manually partitioned the disk 1MiB aligned before using it as a replacement, Unraid would accept and use that partition, but that no longer works due to other changes.

With this change, if the smallest parity drive (or one/both of them if they are the same size) is partitioned on sector 2048, and you add a new or replacement disk with the same number of sectors as the smallest parity, Unraid will also partition it on sector 2048, hopefully from now on avoiding the issue for the affected users and without requiring any user intervention.

4 hours ago, sittingmongoose said:

My emmc storage didnt show up, is there something I am supposed to be doing something like downloading a plugin?

Note that for now, eMMC devices should be detected and enumerated, but there's still no GUI support for them, but like mentioned, please create a new bug report and post the diags, mostly to see if it is being correctly detected and also if it has a unique serial.

1 hour ago, JorgeB said:

There's a long-standing issue caused by Unraid accepting disks partitioned on sector 2048 (1MiB MiB aligned) for some time now; the default for Unraid with HDDs is sector 64. This was introduced several years ago when SSDs started being partitioned on sector 2048 to improve performance. This has been causing issues for users since then, because if you have, for example, an 8TB parity partitioned on sector 2048, and then try to replace a 4TB array disk with another 8TB, Unraid would complain that the new disk is larger than parity, because it would partition it on sector 64, so the partition would be slightly larger than parity's. It's a corner case but could be an issue for those users, especially if the disk was disabled, requiring a parity swap to replace it.

Before Unraid 7.1.x, there was a workaround, if you manually partitioned the disk 1MiB MiB aligned before using it as a replacement, Unraid would accept and use that partition, but that no longer works due to other changes.

With this change, if one of the parity drives is formatted on sector 2048, and you add a new or replacement disk with the same number of sectors as the smallest parity, Unraid will also partition it on sector 2048, hopefully from now on avoiding the issue for the affected users and without requiring any user intervention.

I wonder if this is something that fix common problems should flag, along with an explanation similar to what you've written above.

16 minutes ago, warpspeed said:

I wonder if this is something that fix common problems should flag

It could be added, but hopefully with this change it will no longer be an issue going forward; the users won't even notice.

4 minutes ago, JorgeB said:

It could be added, but hopefully with this change it will no longer be an issue going forward; the users won't even notice.

I just figure it might be something some might want to know about as they might want to correct it properly.

Just want to say that I really appreciate you guys taking the advice and putting the beta releases back in Announcements. Participation appears to have increased and hopefully it will make the official releases less surprise prone.

With that said I'm decommissioning some services from my secondary server and will hopefully get it to a good place as a test lab soon. Excited to participate again!

Question about "old XFS version"

How can i see, if the used XFS is "old" or an old version?

And is it possible to move all the data to an unasigned device if needed to convert the arry disk to a "new" XFS version?

Thanks for your help

3 minutes ago, Zonediver said:

How can i see, if the used XFS is "old" or an old version?

With -beta.3 or newer, it will show in the GUI, e.g.:

With previous releases, you can check the log after mounting filesystem:

Aug 11 11:05:03 Tower7 kernel: XFS (sda1): Mounting V5 Filesystem ca49c894-b011-4d91-9cf1-63304abf8374
Aug 11 11:05:03 Tower7 kernel: XFS (sda1): Ending clean mount

V5 is the new one, if it shows V4, it's the old one.

7 minutes ago, Zonediver said:

And is it possible to move all the data to an unasigned device if needed to convert the arry disk to a "new" XFS version?

Yes, disk needs to be reformatted to XFS again, and it will use v5.

P.S.: only XFS filesystems formatted before Unraid 6.0.0 stable , that is, all v6.0.0 betas and possibly also the release candidates, will use XFS V4, any disk formatted with 6.0.0 stable (released June 16, 2015) or newer should be on V5.

22 minutes ago, JorgeB said:

V5 is the new one, if it shows V4, it's the old one.

Thanks for your help JorgeB - its already v5 - Lucky 😅

Related, and I know we've plenty of time for this, but is there any work in unraid happening on guidance to convert V5 filesystem timestamps to last beyond 2038 or whenever it is.

3 hours ago, warpspeed said:

Related, and I know we've plenty of time for this, but is there any work in unraid happening on guidance to convert V5 filesystem timestamps to last beyond 2038 or whenever it is.

If there is anything being done for this it would be at the underlying Linux level which is where Unraid inherits its XFS support from, not specifically at the Unraid level.

4 hours ago, warpspeed said:

is there any work in unraid happening on guidance to convert V5 filesystem timestamps to last beyond 2038 or whenever it is.

I would expect Unraid to start warning about those when we are closer to 2038, like 4 or 5 years before that.

Hello, I would like to report an issue. After upgrading from 7.1.4 to 7.2.0 beta3, the intel-i915-sriov feature has become non-functional, as shown in the image. Thank you for your efforts.

18 hours ago, HDLynx said:

Hello, I would like to report an issue. After upgrading from 7.1.4 to 7.2.0 beta3, the intel-i915-sriov feature has become non-functional, as shown in the image.

It would be helpful if you could create a bug report with this information and your diagnostics.

https://forums.unraid.net/bug-reports/prereleases/

36 minutes ago, ChatNoir said:

如果可以使用此信息和诊断创建错误报告，将会很有帮助。

https://forums.unraid.net/bug-reports/prereleases/

Ok, thanks. I have created a bug report with diagnostic information

Update complete, no issues on my side

RC1: https://forums.unraid.net/topic/193916-unraid-os-version-720-rc1-available/

On 9/20/2025 at 12:24 AM, Niklas said:

Tooltips get misaligned if I scroll down on the page. No scrolling, they show correcly.

Since there's no bug report, just to let you know that this should be fixed since -rc.1