Unraid 7.2.0-beta.1 is now available with a responsive webGUI, built-in Unraid API, RAIDZ expansion, Ext2/3/4 and NTFS support, and the (optional) ability to login to the webgui via SSO, and more! See all the details in the release notes.
 

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.

 

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.

 

Upgrade steps for this release

1. Read the release notes

2. As always, prior to upgrading, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

3. Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular.

4. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type:

   umount /var/lib/docker

   The array should now stop successfully.

5. If you have a recent release or Unraid Connect installed:

   • Open the dropdown in the top-right of the Unraid webgui and click Check for Update, then press More options and switch to the Next branch. You may be prompted to sign in to access the Next branch. Select the appropriate version and choose "View changelog to Start Update". More details in this blog post

6. If you don't have the Check for Update option in the upper right corner:

   • Either install the Unraid Connect plugin or upgrade to 6.12.10 first. Then check for updates as described above.

7. Wait for the update to download and install

8. If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. 

9. Reboot

 

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.

1 hour ago, ljm42 said:

plugins may have visual issues

As a note, Updates to UD Preclear, recycle bin and cache dirs to fix some minor display issues on 7.2 will be issued later on today. They do all operate though as is. Another update to CA will happen in the next day or two to further refine the responsiveness and fix a couple of issues if the font-size wasn't set to "normal" in Settings - Display Settings.

For CA, if you do upgrade the OS without running the latest version of CA (2025.07.22a) , you will see a completely blank page with only a "Upgrade Available to CA" banner. Hit the update link and all will be good.

Login to the WebGUI via SSO

To enable this optional feature, visit Settings → Management Access → Unraid Connect and add your Unraid.net Account ID to the list of authorized API SSO Users. Once configured, a Login with Unraid.net button will be added to the login page.

Can we use our own identity provider or is this restricted to Unraid.net? It would be useful to have this built on top of a standard protocol like OpenID Connect (OIDC) to make it easy to use with our own IdP (like Authentik, Keycloak, Microsoft Entra, etc) - in theory just swapping out the Unraid.net auth URLs with our own.

Edited August 1, 2025Aug 1 by Daniel15

26 minutes ago, Daniel15 said:

Can we use our own identity provider or is this restricted to Unraid.net? It would be useful to have this built on top of a standard protocol like OpenID Connect (OIDC) to make it easy to use with our own IdP (like Authentik, Keycloak, Microsoft Entra, etc) - in theory just swapping out the Unraid.net auth URLs with our own.

Right now it’s just Unraid.net BUT we are planning on having this system extensible for other OIDC controllers. This is built with oAuth2 so the token validation endpoint in the API needs updating and the button component will need to be aware of other providers.

The API is open source as well if you’d like to see how it works:

GitHub

GitHub - unraid/api: Unraid API / Connect / UI Monorepo

Unraid API / Connect / UI Monorepo. Contribute to unraid/api development by creating an account on GitHub.

Tailscale broken...

1 hour ago, pdawg1717 said:

Tailscale broken...

Can you elaborate a bit on that? TS integration into a docker container? TS Plugin?

1 hour ago, Squid said:

Can you elaborate a bit on that? TS integration into a docker container? TS Plugin?

So sorry...for me it's the plugin...

To be more specific, my docker containers that had tailscale enabled would not start and when trying to start them, gave a "execution error - bad parameter" error. Once I disabled tailscale for those, they started up fine.

Edited August 2, 2025Aug 2 by pdawg1717

"You can create an array or single device pool with existing drives formatted in Ext2/3/4 or NTFS"

What does "array" in combination with "existing drives formatted" mean? I could add all kind of formatted drives to an array up until now because they all become formatted before using the array. Can I now create an (additional?) array with already formatted drives without the need to format them?

Just curious.

Edited August 2, 2025Aug 2 by hawihoney

22 minutes ago, hawihoney said:

Can I now create an (additional?) array with already formatted drives without the need to format them?

You cannot create an additional array until multiple arrays are supported, but you could import or or more disks using any of the supported filesystem with a new install, or a new config for an existing array.

6 minutes ago, JorgeB said:

but you could import or or more disks using any of the supported filesystem with a new install, or a new config for an existing array.

Thanks for your fast answer.

There's no requirement to clear disks that become added to a new or existing array? No Unraid signature that becomes patched to Unraid array disks as of today?

2 minutes ago, hawihoney said:

There's no requirement to clear disks that become added to a new or existing array?

There still is, you can only import disks with data into the array with a new install or after a new config, like mentioned.

2 minutes ago, JorgeB said:

There's no requirement to clear disks that become added to a new or existing array?

There still is

Assuming there's parity, of course; if there's no parity, you could add disks with data, and they would be imported.

5 minutes ago, JorgeB said:

you can only import disks with data into the array with a new install

7 minutes ago, JorgeB said:

"There's no requirement to clear disks that become added to a new or existing array?"

There still is

Isn't that contradictory? On a new install the array disks become cleared as well - isn't it? If they become cleared, the format and the data is gone. Still confused, sorry.

***EDIT*** Got it. With parity data disks become cleared, wthout parity you can build an array without clearing the data disks. Please add that "array, no array" to the changelog. It's confusing without that - at least for me.

Edited August 2, 2025Aug 2 by hawihoney

1 hour ago, hawihoney said:

Got it. With parity data disks become cleared, wthout parity you can build an array without clearing the data disks.

Correct, if you have an existing array with parity, you could add disks with data only by doing a new config (Tools - New Config) and then resyncing parity.

3 minutes ago, JorgeB said:

Correct, if you have an existing array with parity, you could add disks with data only by doing a new config (Tools - New Config) and then resyncing parity.

The answers given recently here suggest that there is no longer an 'Unraid' type signature on the driven for the new file system types? If so are we liable to get some support issues when disks that have previously been used elsewhere are used in Unraid either as a new install or via New Config?

I need to set up a Unraid 7.2 test environment so I can answer such questions for myself if the answer is not already known 😊

9 minutes ago, itimpi said:

The answers given recently here suggest that there is no longer an 'Unraid' type signature on the driven for the new file system types?

Since 7.1.0, Unraid will import the filesystem that exists on the device's largest partition, as long as it's supported by that Unraid version, signature or specific partition layout are no longer required since then.

Just now, JorgeB said:

Since 7.1.0, Unraid will import the filesystem that exists on the device's largest partition, as long as it's supported by that Unraid version, signature or specific partition layout are no longer required since then.

Thanks - that clears that up. I had not noticed that change had happened in the 7.1 release because I never had a scenario where it was relevant.

58 minutes ago, JorgeB said:

Since 7.1.0, Unraid will import the filesystem that exists on the device's largest partition, as long as it's supported by that Unraid version, signature or specific partition layout are no longer required since then.

I must be really stupid that I need to ask further:

I add a NTFS drive to my array that has 2 parity disks and some XFS data disks. I use New Config and let the parity disks to be rebuild. The data on my XFS drives and the NTFS drive are untouched after successful run. That will work? Cool!

3 minutes ago, hawihoney said:

I add a NTFS drive to my array that has 2 parity disks and some XFS data disks. I use New Config and let the parity disks to be rebuild. The data on my XFS drives and the NTFS drive are untouched after successful run. That will work? Cool!

Correct, but just to be clear, the new config must be done before adding a drive with existing data to the array.

1 hour ago, JorgeB said:

Correct, but just to be clear, the new config must be done before adding a drive with existing data to the array.

An existing array with 2x parity disks and some XFS disks. Why should I do a New Config on that running array, before adding the NTFS disk that has existing data on it?

Now I'm out. I don't get that. Way to complicated for me. Good luck explaining that to new Unraid customers ;-)

5 minutes ago, hawihoney said:

Why should I do a New Config on that running array, before adding the NTFS disk that has existing data on it?

Because if you add a disk to a parity-protected array and just start it, that disk will be cleared. It's not that complicated, but if you still have doubts, please start a new thread in the general support forum, I can post some screenshots showing how it works.

13 minutes ago, hawihoney said:

Now I'm out. I don't get that. Way to complicated for me.

That's literally how it was before, nothing new but the ability for the disk to be ntfs-formatted (or ext4,..) in addition to the previously supported formats.

Not something a beginner would do anyway.

Edited August 2, 2025Aug 2 by Kilrah

23 hours ago, ljm42 said:

Unraid 7.2.0-beta.1 is now available with a responsive webGUI, built-in Unraid API, RAIDZ expansion, Ext2/3/4 and NTFS support, and the (optional) ability to login to the webgui via SSO, and more! See all the details in the release notes.
 

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.

 

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.

 

Upgrade steps for this release

1. Read the release notes

2. As always, prior to upgrading, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

3. Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular.

4. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type:

   umount /var/lib/docker

   The array should now stop successfully.

5. If you have a recent release or Unraid Connect installed:

   • Open the dropdown in the top-right of the Unraid webgui and click Check for Update, then press More options and switch to the Next branch. You may be prompted to sign in to access the Next branch. Select the appropriate version and choose "View changelog to Start Update". More details in this blog post

6. If you don't have the Check for Update option in the upper right corner:

   • Either install the Unraid Connect plugin or upgrade to 6.12.10 first. Then check for updates as described above.

7. Wait for the update to download and install

8. If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. 

9. Reboot

 

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.

Flash backups should be a part of the standard update process itself by default, IMO. Reasonable defaults like that are something that I hope to see more of in Unraid. Likewise, up to 7.2 and 20 years of Unraid, but still no backup facility in the OOBE. Absolutely not a sexy or fun project, but perhaps one of the most important for a distro aimed at file storage. Not knocking anything here, but I'm always perplexed when a new version brings plenty of new features, but zero progress on a backup facility.

Even if it was just a way of easily assigning internal, external and remote targets for ZFS replication then throwing in a cron schedule per backup task, it's absolutely better than how it currently is. At least then users could repair a ZFS dataset if they redundantly replicate it elsewhere.

EDIT: found a workaround solution, and it seems unraid is already aware and working on this. Link to the temporary fix: https://forums.unraid.net/bug-reports/prereleases/tailscale_container_hook-keeps-changing-to-a-folder-r3999/

regarding the tailscale, experimenting the same since i upgraded, for the tailscale feature for docker-specific tailscale nodes. Since unraid os upgrade to 7.2.0 (beta), my only container configured to use a specific tailscale host (container-specific tailscale usage), which is Jellyfin (linuxserver image), fails to run with the following message at the end of the docker run command, which is reproduced below. I also attach diagnostics from tailscale plugin. I am running latest versdion of the tailscale plugin. Didn't change anything to my config or tailscale settings between the update or in the past months. Many thanks in advance.

error message:

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/opt/unraid/tailscale": is a directory: unknown: permission denied.

The command failed.

full docker run command:

docker run

-d

--name='jellyfin'

--entrypoint='/opt/unraid/tailscale'

--net='bridge'

--pids-limit 2048

--privileged=true

-e TZ="America/New_York"

-e HOST_OS="Unraid"

-e HOST_HOSTNAME="Beelink"

-e HOST_CONTAINERNAME="jellyfin"

-e 'JELLYFIN_PublishedServerUrl'='http://XXX'

-e 'DOCKER_MODS'='lizardbyte/themerr-jellyfin:latest|linuxserver/mods:jellyfin-opencl-intel'

-e 'PUID'='99'

-e 'PGID'='100'

-e 'UMASK'='022'

-e TAILSCALE_ALLOW_LAN_ACCESS='false'

-e TAILSCALE_USE_SSH='false'

-e TAILSCALE_USERSPACE_NETWORKING='false'

-e TAILSCALE_SERVE_PORT='XXXX'

-e ORG_ENTRYPOINT="/init"

-l net.unraid.docker.managed=dockerman

-l net.unraid.docker.webui='http://[IP]:[PORT:8096]'

-l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/jellyfin-logo.png'

-l net.unraid.docker.tailscale.webui='https://[hostname][magicdns]'

-p 'xx:xx/tcp'

-p 'xx:xx/tcp'

-p 'xx;xx/udp'

-v '/host path/':'/data/':'rw,slave'

-v '/host path':'/config':'rw'

-v '/usr/local/share/docker/tailscale_container_hook':'/opt/unraid/tailscale'

--cap-add=NET_ADMIN

--device='/dev/net/tun'

--device='/dev/dri/' 'lscr.io/linuxserver/jellyfin:latest'

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/opt/unraid/tailscale": is a directory: unknown: permission denied.

The command failed.

Beelink-tailscale-diag-20250802-161823.zip

Edited August 2, 2025Aug 2 by wildenrou

Feedback: when changing UI elements, e.g. the new notification management section. Please could you share screenshots of the changes :)