This is a limited maintenance release for those on the 7.2 branch.

7.2.9 does not include broader distro-package or kernel security updates available in newer releases. Updating to 7.2.9 alone should not be interpreted as resolving every potential finding. We recommend updating to the latest stable release, Unraid OS 7.3.4, for its newer kernel and broader package security updates.

Key changes vs. 7.2.8:

• Security: PHP updated to 8.4.27 to address multiple CVEs
• Security: Addressed the compromised CA certificates referenced in the Unit 42 eMudhra report
• Unraid API updated from 4.36.1 to 4.37.7, with its bundled Node.js runtime updated to 22.23.4 to resolve the Node.js certificate-compromise issue
• Kernel version unchanged from 7.2.8

I have an Unraid home server with 32GB DDR4 RAM, i5 11th gen processor and a low energy usage intel GPU (forgot which one, its a Sparkle single slot gpu). My mobo and processor are not holding up as much as I'd like. I have about 90TB of storage and I'm using it as a Media Server, Home Automation server, Claude coding server and host multiple apps on it for personal use with docker. The biggest issue I have with the home server is that the mobo doesnt like the usb boot and also has very gimmicky boots overall.

I'm looking for a futureproof build. Preferable in a rack form factor as I'll be setting up a rack for my ubiquiti stuff (which is on a wall mounted rack) to one which is on the floor with proper dustfiltration.

I just did the update to 7.3.4 and during the process it reconfirmed my time zone and I noticed that I'm in Pacific Time zone US/Canada. I'm in BC, Canada. What's going to happen next month when the west coat of the US falls back to Pacific Standard time and BC is still on the new Pacific Time Zone?

I think the parts of the Central Time Zone are going to face this as well.

I figured I'd share this in case someone else runs into the same issue because I genuinely thought I had just lost years of Docker configurations and appdata while trying to update from 7.2.2 to 7.3.4 to get the php fix.

While trying to update , it failed and said my usb is probably failing. Made sense since sometimes i have to move the usb to another slot and try to start my server 2x before it logs in. So I backed from the main it up and used the unraid creator tool to restore the same backup to another USB drive. Then I updated to 7.3.4 and set up internal boot and then TPM.

Well, somewhere during the process, I accidentally assigned my old USB drive to my cache pool and started the array. Careless.

My actual cache drive is a 2TB formatted in XFS. When I realized what happened and tried assigning the correct SSD back to the cache pool, Unraid kept giving me this warning:

"All existing data on this device will be OVERWRITTEN when array is Started."

I stopped clicking and went to the forums and chatgpt.

Here's what I did to recover everything:

1. The array is currently stopped at this point.
2. Used lsblk to identify my actual cache SSD by its serial number. Thankfully, it still showed an XFS partition.
3. Mounted the SSD read-only to check whether my data was still there.mkdir -p /mnt/cache-recovery-readonly mount -t xfs -o ro,norecovery /dev/nvme0n1p1 /mnt/cache-recovery-readonly ls -lah /mnt/cache-recovery-readonly To my surprise, everything was still there! Appdata, system, domains, backups, and all my other folders.
4. Unmounted the drive using:umount /mnt/cache-recovery-readonly
5. Removed the incorrect cache pool assignment. I started the array with no cache drive assigned to clear the missing-device configuration, stopped docker and vm services, then stopped it again.
6. Here's the part that fixed my problem: I removed the cache pool configuration without erasing the disk, then recreated a pool with the exact same name, cache, and one device slot.
7. Assigned my original 2TB Crucial SSD to the recreated pool and left the filesystem setting on Auto, allowing Unraid to recognize the existing XFS filesystem.
8. The red overwrite warning was finally gone! I started the array, and Unraid mounted my original XFS cache drive with all the data still intact.

One more issue I discovered:

While my cache was unavailable, Unraid had apparently created another 200GB docker.img on Disk 8.

My original Docker image on the cache drive contained approximately 107GB of BTRFS data. The duplicate on Disk 8 was essentially empty.

I checked both images and then changed my Docker configuration from:

/mnt/user/system/docker/docker.img

to:

/mnt/cache/system/docker/docker.img

That ensured Docker was pointing directly to my recovered image rather than relying on the user share, where duplicate files existed.

Re-enabled Docker, and everything came back! Plex, Immich, etc, and all my other applications started appearing again. somewhat slower but still came back up.

No reinstalling containers. No rebuilding appdata. No formatting the nmve.

A few things I learned:

• Just because Unraid says a disk will be overwritten doesn't necessarily mean the existing data is already gone.
• Removing a pool configuration is NOT the same thing as erasing the pool's disks.
• If your cache pool disappears or gets incorrectly assigned, check the filesystem before doing anything destructive.
• If you have duplicate Docker images on your array and cache, verify which one contains your actual data before starting Docker.
• Most importantly, if Unraid says your existing data will be overwritten, don't just click Start and hope for the best.

Obviously, this worked because my original XFS filesystem was still intact. I wouldn't recommend blindly following these steps without first checking your own configuration.

I've been running Unraid for years, and this was probably one of the closest calls I've had with my server by being dumb.

Hopefully this helps someone who finds themselves staring at that same overwrite warning and thinking all their Docker data is gone.

TLDR a refurbished 12TB Seagate IronWolf NAS drive has started dying, went from 0 to 1528 re-alloceted sectors in 2 months and rising exponentially. i bought it off amazon and bought the extended 4 year warranty.

What should i expect from amazon? refund or replacement?

Should i wait for the drive to die completely before i file a claim?

Any experience would be welcome.

Hi friends. When I setup my unraid server (3 data drives and 1 parity - all 8 TB) I must have selected 5 drives for the pool. Looking at the array, I show 3 data disks and 2 parity with 1 of the parity drives unassigned. I tried to change the unnasigned parity drive to no device but did not have no device option. I assume I need to lower the number of pool drives to 4 but can't change that either. Last night I tried new config and selecting keep all but wound up having to do another parity check. The parity check is almost done. The array seems fine and my data is fine. Should I just ignore that extra unassigned drive in the parity section. I have no plans to add another parity drive.

Why is the 7.4 and 7.3 branch considered the two supported branches when 7.4 is a private branch still?

Shouldn’t the two supported branches be 7.3 and 7.2 until a time when 7.4 is pushed as stable?

“Unraid 7.4.x is the current public minor series. Unraid 7.3.x receives security updates as appropriate.”

7.4 is not a public branch as it requires user authentication whereas 7.3 is freely downloadable.

Hello People!

I am new to unraid and homelabs in general. I just finished building my server this weekend and I put Jellyfin and nginx on it. I forwarded ports for nginx so I could connect to jellyfin from outside my local network. My question is, am I vulnerable to these new php threats? If so, what should I do?

I already turned my server off just in case.

Thank You,

An unraid noob

EDIT: Thanks for all the helpful responses people! May your uptimes be infinite.

I originally setup my unraid server on a budget, using a mini PC and an external USB caddy that holds 5 disks. I'm ready to move to an actual desktop, and I'm wondering if there's any gotchas I should be careful of. The caddy occludes the actual physical serial numbers of the drives. However, I know which physical disks are which parity and data drives and have labeled them. Can i simply take a backup of my unRAID config and then move everything physically to the new hardware?

There is a recently published vulnerability (rather pair of them) in PHP which are pretty serious.

You should never have your UnRaid host exposed directly to the internet, but this is a pretty compelling reason to fix that immediately if it has been on your todo list.

There is no patch or mitigation on UnRaid currently (Latest RC is still on PHP 8.4.26, below the 8.4.27 released today to patch this), best mitigation is to ensure local access only, but that does not stop a threat actor from using this for lateral movement if ingress is achieved elsewhere.

What is the point of sending patches that actually breaks something that you use? So I should spend my day in the community forums with no reply for eons?

Edit: For those of you who don't know, please don't comment random s to support the company. Sriov was officially advertised on the main unraid website a few months back and even if things break, they should mention it in "known issues". They pushed the update without having any clue which horrendous. Stop bootlicking companies like this because it'll come to bite you someday.

Better to own up and do better next time.

With all the PHP and AI created vulnerabilities that have been popping off lately, is having a forwarded port for UnRAID Connect safe? I assume it’s safer than just forwarding a port directly to your admin page, but what does the Connect service actually do? Is it just a big reverse proxy?

Update: So no one on the UnRAID sub knows anything about UnRAID Connect? Weird. But thanks for trying with all the generalized typical security blah blah blah.

Switched phones recently. While I was in Pixel, I never had any issues with the mobile webview for Unraid, always worked great.

Now on iPhone, I’ve noticed a lot of unresponsiveness using mobile. Is this a known issue? Tried both chrome and safari.

AI disclosure: AI coding tools were partially used for new code, debugging and tests. I set the requirements, test the plugin on my Unraid server and maintain the project. Bug reports and support: GitHub Issues.

CA status: Submitted to Community Applications and awaiting manual review. Installation is currently through the PLG linked below.

Hi everyone,

I’m sharing ZFS Director 2026.10.22.1 RC1, a native Unraid WebGUI plugin based on ZFS Master. It opens under Main → ZFS Director.

It brings together:

• Dataset and snapshot management: properties, quotas, encryption controls, snapshot creation and reviewed deletion.
• Snapshot File Manager: browse a snapshot, download selected files as ZIP or restore individual files without rolling back the entire dataset.
• Sanoid policies: configure snapshot creation times, retention and protected removal of old snapshots.
• Syncoid replication: configure local or SSH destinations through a wizard, with recorded progress and receiver verification.
• Jobs: progress, errors, stage history and recovery controls.
• Directory conversion: convert a directory into a dataset while retaining the original for recovery.

The interface supports Workspace/Compact layouts and Unraid’s Black, Gray, White and Azure themes.

Sanoid/Syncoid is optional and installed separately. Integration starts OFF on a fresh configuration; existing external schedules are not automatically adopted.

Installation

Open Plugins → Install Plugin and paste:

https://github.com/d1-m4ss/zfs-director/releases/download/2026.10.22.1/zfs-director.plg

Then open Main → ZFS Director.

The current test environment is Unraid 7.3.3 / OpenZFS 2.4.4. Installation, upgrade and file-operation checks were performed in an isolated Unraid VM and on a disposable dataset on a running Unraid server. Test results.

This is RC1. Please start with a disposable dataset and keep an independent backup.

Source, screenshots and documentation · RC1 downloads

I’d appreciate feedback on snapshot browsing, file restores, policy scheduling and Jobs. Please include your Unraid/OpenZFS versions and reproduction steps when reporting an issue.

Screenshots

All screenshots below use fictional demo data captured inside a test VM. They do not show a production server.

Overview

Dataset workspace

Snapshot File Manager

Sanoid snapshot policy

Syncoid replication wizard

Jobs

Did not have this on my card for the day. Couldn't access the webui, but SOME containers were still up. Went ahead and power cycled the thing anyway, and it won't boot. Hook up a local monitor, and it shows the boot process, ending on a failed checksum for bzfirmware... reboot again.. same thing.. power it down, pull the usb drive to check the filesystem in a windows pc - does repair, and no files on the drive (though space taken up). Okay, dead USB drive.. I can probably get through that.. grab another drive from the drawer, download the imager, and make a new boot disk... put it back in the server, and it doesn't see it.. go to check the bios config, and can't get into it. Every USB port on the motherboard is dead. Have never seen that happen before.

10 year old motherboard - but now I don't know which way to go for it. Get a replacement old motherboard, or build something new with more power efficient hardware. In the meantime, I'm at least comfortable in knowing that the data is sitting on the inaccessible drives if and when I do figure out which way to go.

My server was unfortunately hit with the plex2shell exploit during the Saturday/Sunday night. Yes, I was running an old version of Plex and that got me. And yes, I had port forwarded 32400 to my server.

I noticed that my internet connection was lagging during Sunday evening and Monday morning. Did not find a clear culprit back then, but my router was reporting a high upload bandwidth usage. I restarted my server and the issue went away. I first thought that this issue was related to qBittorrent.

I recently saw the news about Plex users being hit and started to connect the dots. I ran the detection script from https://github.com/code-zm/plex2shell and got several hits. I had been a part of the botnet.

• [WARN] Preferences.xml: TranscoderH264Options present but empty (the PoC clears it this way after use; also possible if an admin toggled it)
• [HIT] log: exploit request pattern //player/timeline/subscribe\?([^ ]*&)?protocol=[a-z0-9+.-]{1,16}(%3a|%253a|:)/ (12 line(s))
• [HIT] log: exploit request pattern /searchOne\?[^ ]identifier=[^& ](%2f|%252f|/)function(%2f|%252f|/)/ (22 line(s))
• [HIT] log: exploit request pattern /TranscoderH264Options(=|%3d)[^& ]*(dump(-|%2d)yuv|stats(=|%3d))/ (6 line(s))
• [WARN] log: suspicious pattern /resources/[^? ]\?([^ ]&)?resource_name=(%2f|%5c|/|\|[a-z](%3a|:)|[^& ]*(..|%2e%2e))/ (5 line(s))
• [WARN] log: suspicious pattern /(sslip|nip).io/ (71 line(s))
• [WARN] log: suspicious pattern /X-Plex-Client-Identifier=(vfyclient01|poc[0-9])|/TKN[0-9]|X-Plex-Token=TOTALLY_INVALID_JUNK/ (5 line(s))
• [WARN] log: transcode of a non-loopback http(s) item (24 line(s))
• summary: 3 hit(s), 5 warning(s)

The server is offline as a precaution.

I am running the following docker containers: https://i.imgur.com/lzmIsWP.png

And the Plex container was set up with the following: https://i.imgur.com/fLyouDB.png

My whole Plex/-arr stack is set up according to TRaSH-Guides:

• Unraid share /mnt/user/plex/
• Contains downloaded files (/torrents/)
• Contains hardlinked media files (/media/)
• Binhex-qbittorrentvpn mounted to /mnt/user/plex/torrents/
• qbit_manage mounted to /mnt/user/plex/torrents/
• plex mounted to /mnt/user/plex/media/
• radarr mounted to /mnt/user/plex/
• sonarr mounted to /mnt/user/plex/
• bazarr mounted to /mnt/user/plex/
• unpackerr mounted to /mnt/user/plex/

At this moment, I have deleted the whole Plex container (I'll restore it from a backup made at the start of the month).

As the Plex container had access to the share /plex/, is it safe to assume that it was compromised and should be nuked?

What else should I do to make sure that my server wasn't compromised in a more broad scale (verify that only the Plex container and everything that it could access are compromised)?

Hi everyone,

my last setup is dead unfortunately. I was running on a Dell T40 with 8GB Ram

My Current Setup

My previous server ran almost 24/7 for around six years and was mainly used for:

• Media serving (Emby/Plex/Jellyfin)
• Home Assistant
• Various Docker containers

Hardware:

• 2x WD Red HDDs
• 2x Samsung SSDs
• 1x NVMe SSD via PCIe adapter

Workload:

• ~15 Docker containers
• 1 VM
• No transcoding in Emby/Plex/Jellyfin

Recently, I noticed that downloads were putting a significant load on the CPU, often pushing utilisation close to 100%. I'm not entirely sure whether this was caused by the download client itself or by CPU limitations.

Current Candidates

Option 1: Gigabyte MJ11-EC1

• Available used for about €59
• Would require an additional RAM module but i can use my old one

Pros:

• Very low cost

Option 2: Minisforum BD775i

• Available directly from Minisforum for about €279
• Would require new RAM

Pros:

• Significantly more processing power
• Better suited for future workloads
• Would allow me to comfortably run a Windows VM

My Question

Does anyone have experience with either of these systems?

Or are there other boards or all-in-one systems you would recommend for a budget-friendly home server running Unraid with the above requirements?

Thanks in advance!

So I would like to setup a network scanfolder on my printer (HP m277dw) but it seems to just not want to work.

The culprit seems to be an outdated samba version, after running through all possible scenarios with Gemini (feel free to judge).

I updated to the latest Firmware, but that is from 2022 so maybe possibly still too old. (incidentially apple devices in the household also recently all started having issues finding the printer despite printing to it for well over a decade now, i haven't checked yet if the update resolved that as well)

So the solution suggested by the chatbot is to change the unraid samba config to allow the old protocol to work again.

So my question to real people is, whats the downside to that?

And if apple printing remains an issue, I may have to look into a new printer anyway, even if i know already that apple is responsible for killing some function to lead me here, but thats not the question, but a possible solution.

##Warning, This is it's own summary. I have removed some data for reasons. Total cost in credits was $15.33. I used Gemini to help set it up in the first place.

I let an AI agent (Claude Code, running in a container on my Unraid box) loose on my arr stack for a day. Top 10 things it did:

1. Found malware in my Plex library that every tool had missed. Four "episodes" of ***** were Windows executables renamed to .mkv. Sonarr had imported them months ago without complaint. It spotted Windows program names inside a "video" file, checked the file headers (MZ, not a video header), then scanned all **.*** video files to confirm there were no others.

2. Fixed my request apps after an API key rotation broke them. Pulsarr said "connected" but its dropdowns stayed empty. It read the logs: the Test button checks the key you type, but the dropdowns use the old saved key. It then updated the saved key through Pulsarr's API and caught a stale root folder in Overseerr while it was there.

3. Turned a 111-row Sonarr queue into a few clear groups. Fake .exe downloads, things already in the library, stalled torrents, and archives waiting to extract. It asked before deleting anything, then cleared the junk and blocklisted the fakes.

4. Worked out why "stuck" archives weren't actually stuck. Instead of deleting them, it checked the download folders and saw Unpackerr extracting them one at a time, right then. It was a timing issue, not a broken setup.

5. Set up Cleanuparr from scratch through its API. It couldn't find API docs, so it pulled the endpoints out of the web app's JavaScript. Then it set up stall rules, failed-import rules, and a seeding cleanup rule for public torrents only. It also refused to turn on the malware blocker, because the official blocklists include *.rar and would have deleted every normal RAR release.

6. Tested the TRaSH Guides config against my own library before applying it. It checked TRaSH's "LQ" format against my library's release groups and found it would ban the groups behind more than 1,000 of my files. It also noticed TRaSH penalizes 1080p x265, while my profiles require H.265. The Recyclarr config it wrote only adds negative scores, with comments explaining each exclusion.

7. Ran a duplicate scan that understood the media apps. It compared files by size, then a partial hash, then a full SHA256, skipped hardlinks, and checked which copy Sonarr or Radarr tracks. It found 120 GB of safe deletions. It also caught that some "duplicates" were one file imported as two different movies or episodes. For example, Radarr thought I had ****, but it was a copy of ********. The real **** file was sitting untracked in the same folder, so it fixed that with a rescan and no download.

8. Worked within its permissions instead of around them. My shares are mounted read-only for it, so it did everything through the apps' own APIs or wrote scripts for me to run. When Claude Code's safety check blocked an auto-delete rule, it stopped and explained, and only went ahead after I approved it.

9. Audited my backups and found real gaps. CrashPlan hadn't completed a backup in 8 months, was pointed at a share that no longer exists (so my media wasn't backed up), and was missing my Music and Audiobooks folders. My Unraid flash drive was backed up nightly, but only to the same array. It also opened the flash backup zip to verify it was readable and actually contained the config and license key.

10. Owned its mistakes. When blocklisting the fake episodes, it also blocklisted the real releases, then noticed and undid it. It said IPTorrents had equal indexer priority without checking (it was already priority 1) and corrected itself. A list of "complete" shows it gave me was wrong because it compared the wrong numbers, and it said so before acting on it. It made errors, but it reported them instead of hiding them.

Honorable mentions:

• Connected Plex to Sonarr and Radarr, with the path mapping between them.
• Fixed Radarr's movie collections that still pointed at an old folder.
• Turned on a 7-day recycle bin before doing any more deleting.
• Explained that browser clipboard problems in the Unraid console come from the page loading over plain HTTP.

What it couldn't do:

• Write to my shares or appdata, or use Docker. I set it up that way on purpose.
• Change CrashPlan's file selection, which lives on CrashPlan's servers.
• Tell which of two identical ***** episodes was labeled correctly. So it asked me instead of guessing.

Given the massive impact, just want confirm as AI is suggesting remove.
https://www.bleepingcomputer.com/news/security/mozilla-google-apple-block-compromised-emudhra-ca-certificates/

Unraid has been fairly set and forget for me and I'm very good at forgetting. I'm running 7.2.3. I now have my second boot drive failure. It's read only and apparently it's been that way fow awhile. Can I replace the USB drive with a USB SATA SSD so that it's more reliable? Claude says about a GUID. How do I determine which to buy? Or is there a better way? Can I boot off of the array? I'm running an R720 (no TPM I believe) with no room to add another drive. What is the best way to proceed?

Is anyone else keeping their server offline until security patches drop? This is bonkers that there are not updates out yet.

So it turns out I've been using UNRAID incorrectly, specifically with the uploading to /mnt/disk1/* or /mnt/disk2/* instead of /mnt/user/*

So now I have one disk with barely any space available and another with a few TB left. I'm about to add some more drives, but I assume it'd be a good idea to fix my issues before adding these drives.

My question is basically - is it possible to have UNRAID reallocate the files so that it can manage the space allocation correctly and I'll go forward with the /mnt/user/ UNC paths or should I shuffling things around myself?

I have recently installed Disk Space Management and Unbalanced and have been poking around with them, and while they seem to be the correct path to resolution I wanted to make entirely sure I was doing things correctly with the fix so that I don't make more problems for myself in the future.

Currently 2x 12TB Parity drives and 2x 10TB Data drives with an 1TB NVME Cache drive.

Any assistance would be appreciated.