Unraid 7.3.0-rc.2 is out. This build targets fixes from rc.1 testing across internal boot, storage, virtualization, Docker, WebGUI, and security. Full rc.1 changelog is included below for reference.

This is release candidate software. Please use on test servers only.

---

Changes from rc.1

Security

• Add WebGUI security hardening for authenticated-session request handling

• The included 7.3 kernel contains the fix for CVE-2026-31431, the Copy Fail local privilege escalation vulnerability

Storage

• Add mvsas and smartpqi as built-in storage drivers for internal boot

• Fix: Address an md/unraid driver crash

• Fix: Correct ZFS pool replacement handling when a dropped device is marked REMOVED, so replacement workflows no longer leave the pool degraded with a stale new-device state or repeated overwrite warning

• Fix: Improve dedicated and split boot-pool detection after boot-pool devices are replaced with larger devices

• Fix: Allow adding a device to a formatted split boot pool when the data partition is formatted as ZFS or BTRFS

• Fix: Prevent creation of ZFS pools whose names start with reserved ZFS name prefixes: mirror, raidz, draid, and spare

Containers / Docker

• Update Docker to 29.4.1

WebGUI / System

• New: Show chassis serial number in System Info when a valid chassis serial is available

• Fix: Keep the WebGUI responsive while adding Docker containers from the Add Container page

• Fix: Correct stale status display after affected storage replacement workflows

• Fix: Use online / offline instead of on-line / off-line in various text

Virtualization

• Fix: Update deprecated VM machine types during startup so older VMs do not fail with unsupported QEMU machine-type errors after upgrading

• Fix: Restore the Unraid UEFI logo for VMs

• Fix: Show the assigned RenderGPU for the first VM in the VM list when using Virtio 3D

Licensing

• Fix: Improve TPM-based license replacement blacklist handling so a transferred TPM-based key is blocked without permanently blocking the underlying motherboard GUID from future valid activation

---

Known Issues

• During internal boot setup, the WebGUI may show Array Offline while internal boot configures. DO NOT manually restart or remove your flash drive during this process.

• Internal boot requires boot storage accessible by built-in Linux drivers during startup. rc.2 expands coverage to mvsas and smartpqi, but devices requiring third-party drivers or post-boot configuration are not supported.

• Some invalid ZFS pool names that begin with reserved ZFS prefixes may fail without a clear WebGUI error. Choose a different pool name if creation does not complete.

• If a split boot-pool device is removed and another device is added immediately afterward, the slot count may not always update until the server is rebooted.

See the Unraid OS Pre-release (Bugs & Feedback) board for issues reported by other testers.

---

Rolling Back

• You can roll back to 7.3.0-rc.1 without issue if you have already enabled internal boot or switched to TPM-based licensing.

• Do not roll back to 7.2.5 or earlier after enabling internal boot or TPM-based licensing.

• If you upgrade ZFS pool features, earlier Unraid releases may not be able to import those pools.

• Follow the normal pre-release rollback process before moving between builds.

• If you are considering any rollback path below 7.3.0-rc.1, see the 7.2.4 release notes.

---

Upgrading

For step-by-step instructions, see Updating Unraid.

Links

• Release Notes -- Full 7.3.0-rc.2 release notes

• Blog Post -- rc.2 announcement

• Bug Reports -- Report issues here

• Internal Boot FAQ

• TPM Licensing FAQ

Updated from 7.2.5 ---> 7.3.0-rc.2 booted back up no issues & system seems OK. Updated early to get the 7.3 kernel contains the fix for CVE-2026-31431, the Copy Fail local privilege escalation vulnerability for peace of mind security.

Will report back if any issues arise. Thank you

I wasn't expecting another update to Docker at this point, but 29.4.2 has some additional hardening against CVE-2026-31431 (a.k.a. CopyFail)

EDIT: 29.4.3 was released a few hours ago with some compatibility fixes due to the hardening against CopyFail: https://github.com/moby/moby/releases/tag/docker-v29.4.3

Edited May 7May 7 by andrebrait

Current Version: Unraid 7.3.0-rc.1 ->> New Version: Unraid 7.3.0-rc.2

Everything looks fine!

Did anyone have troubles with the Tailscale Plugin? I tried RC1 and it flat out would not work. I didnt see any others talk about that.

Also, couldnt get my intel B50 working on RC1, not sure if I was missing anything, but I thought from research that the newer kernel would enable Plex to use it.

52 minutes ago, DirtyDan said:

Did anyone have troubles with the Tailscale Plugin? I tried RC1 and it flat out would not work. I didnt see any others talk about that.

Also, couldnt get my intel B50 working on RC1, not sure if I was missing anything, but I thought from research that the newer kernel would enable Plex to use it.

Not sure if this is still the case but I think you need to run the beta version of Plex to get arc battlemage support.

4 hours ago, DirtyDan said:

Did anyone have troubles with the Tailscale Plugin? I tried RC1 and it flat out would not work. I didnt see any others talk about that.

Also, couldnt get my intel B50 working on RC1, not sure if I was missing anything, but I thought from research that the newer kernel would enable Plex to use it.

My Intel Arc B70 is working, your B50 should as well.

i update the lateast 7.3RC2,but the intel SR-IOV did not work ,even the from the system device i can see 4 Virtual GPU i set , but it did not work ,and i also installed the plug for my 12400. when i downgraded to 7.2.4,everything good.i can see unraid want to intergated the sr-iov, but if the plug not install ,the sr-iov is useless , why not do the both thing.

1 hour ago, Zachwang said:

i update the lateast 7.3RC2,but the intel SR-IOV did not work ,even the from the system device i can see 4 Virtual GPU i set , but it did not work ,and i also installed the plug for my 12400. when i downgraded to 7.2.4,everything good.i can see unraid want to intergated the sr-iov, but if the plug not install ,the sr-iov is useless , why not do the both thing.

Intel do not support SR-IOV on igpus. The plugin creates a modified driver which is not part of the main kernel hence why it is not included. SR-IOV support was added to the gui to support device that support it natively like ARC B pro GPUs and network adapters.

If you need SR-IOV suppurt for igpus you still need the plugin for the modified driver.

9 hours ago, JustOverride said:

My Intel Arc B70 is working, your B50 should as well.

Also confirming I am using a B50, and it's working fine as of RC1 (and now also on RC2). At least for VM rendering using VirtIO(3D) as well as transcoding against docker containers.

I am guessing user is assuming it will just work. You still need to do the basics of passing /dev/dri through as a device to your containers.

Edited May 7May 7 by cybrnook

14 hours ago, SimonF said:

Intel do not support SR-IOV on igpus. The plugin creates a modified driver which is not part of the main kernel hence why it is not included. SR-IOV support was added to the gui to support device that support it natively like ARC B pro GPUs and network adapters.

If you need SR-IOV suppurt for igpus you still need the plugin for the modified driver.

i understand this, but even now 7.3 ,i install the plug , SR-IOV still now working, i am looking forward the 7.3 next version getting better on this.Have you heard about FNOS ,it's a chinese nas os, it's working much better about the SR-IOV.

7.3.0-rc.1 & 7.3.0-rc.2 "Pool Status" observation.

I have an all flash (SSD) Array (WITHOUT Parity) configured within 7.3.0-rc.2, when I view the status of any Array Device (e.g. "Disk 1") the status display shows "pool status: UNKNOWN" (see attached screen shot).

Should 'Pool Status' & 'Pool Device Status' details be displayed for Array devices?

Thanks.

57 minutes ago, PPH said:

7.3.0-rc.1 & 7.3.0-rc.2 "Pool Status" observation.

I have an all flash (SSD) Array (WITHOUT Parity) configured within 7.3.0-rc.2, when I view the status of any Array Device (e.g. "Disk 1") the status display shows "pool status: UNKNOWN" (see attached screen shot).

Should 'Pool Status' & 'Pool Device Status' details be displayed for Array devices?

Thanks.

No they should not be and dont show on my system. Could you raise a bug on product.unraid.net in the prerelease section and include diagnostics?

I have found the error it is related the the file system of btrfs and zfs. I missed a check to see if it was a pool or array device.

1 hour ago, SimonF said:

No they should not be and dont show on my system. Could you raise a bug on product.unraid.net in the prerelease section and include diagnostics?

I have found the error it is related the the file system of btrfs and zfs. I missed a check to see if it was a pool or array device.

Bug report raised.

I configured the Array disks as BTRFS as the overhead of this File System is low and I want to maximise the available storage space within my SSD Disks. 😊

Just now, SimonF said:

No they should not be and dont show on my system.

15 minutes ago, PPH said:

Bug report raised.

I configured the Array disks as BTRFS as the overhead of this File System is low and I want to maximise the available storage space within my SSD Disks. 😊

Thanks I have fixed this in https://github.com/unraid/webgui/pull/2632

I am too stupid to make it work. I downloaded the USB Creator and installed the latest RC on it. It is booting and I want to set up internal boot. No matter which way I am doing it (boot pool or dedicated install) it just won't work. After I finished the process during installation and restarted the whole thing I am welcomed by this screen (I did it like it was shown in this video: https://www.youtube.com/watch?v=NMHaMaa8iV0&lc=Ugx2Olu8WOcI6ZooXMx4AaABAg.AWYEM1qqg2wAWYnKRSSwqn):

You can see that I tried to create a bootable pool with the two SSDs, but it didn't work. When I try to do the wizard again, I get the same result.

Background information: I just bought a used DXP4800 Plus. It has 4 HDDs and 2 m2 SSDs in it.

It is my first try to install unRAID anywhere, so be patient with me :D I am total noob to this topic.

Is this my usb flash drive "spinning down"?

emhttpd: spinning down /dev/sdk

emhttpd: sdspin /dev/sdk down: 1

Does it save power/wear? 😁

Using USB for license (my hardware is too old to have or add TPM). sdk = usb drive, old boot.

Edited May 8May 8 by Niklas

4 minutes ago, Niklas said:

Is this my usb flash drive "spinning down"?

emhttpd: spinning down /dev/sdk

emhttpd: sdspin /dev/sdk down: 1

Does it save power/wear? 😁

Using USB for license (my hardware too old to have or add TPM). sdk = usb drive, old boot.

The 1 means it does not spin down and will not be tried again.

1 hour ago, zeus22 said:

It is booting and I want to set up internal boot. No matter which way I am doing it (boot pool or dedicated install) it just won't work.

This is not really the best thread for this, please create a new thread in the general support forum.

Uptime 2 days 17 hours 40 minutes, no issues at all. Everything working as it should.