r/unRAID • • 1d ago

Unraid OS 7.3.6 | Security Fixes, Docker Update Checks & Internal Boot

Thumbnail
unraid.net
76 Upvotes

Unraid OS 7.3.6 is a maintenance release for users running 7.3.5. Changes vs. 7.3.5:

  • Security: CVE fixes in Git, Kerberos (krb5), NGINX, rclone, rsync, and graphics libraries, plus security fixes for OpenSSH and libarchive

  • Fix: Docker update checks no longer show “not available” for lscr.io images when the registry redirects the request (thanks to rkozyak for the fix, and to the community members who reported it)

  • Improvement: internal boot from more storage controllers, including MegaRAID SAS, HPSA, 3ware, AACRAID, MPI3MR, and PM8001

  • New: the time-zone list includes all standard time zones and is searchable

  • Kernel updated to 6.18.64-Unraid, among 59 package updates

We recommend this update for everyone running 7.3.5 and below.

Blog | Release Notes | Updating Unraid | Bug Reports


r/unRAID • • 1d ago

Unraid OS 7.4.1 | Security Fixes, File Manager Fix & Internal Boot

Thumbnail
unraid.net
249 Upvotes

Unraid OS 7.4.1 is a maintenance release for users running 7.4.0. Changes vs. 7.4.0:

  • Fix: File Manager actions from a disk in the LOCATION column now apply only to the selected file or folder.

  • Security: CVE fixes in Git, Kerberos (krb5), NGINX, rclone, rsync, and graphics libraries, plus security fixes for OpenSSH and libarchive

  • Fix: Docker update checks no longer show “not available” for lscr.io images when the registry redirects the request (thanks to rkozyak for the fix, and to the community members who reported it)

  • Improvement: internal boot from more storage controllers, including MegaRAID SAS, HPSA, 3ware, AACRAID, MPI3MR, and PM8001

  • New: the time-zone list includes all standard time zones and is searchable

  • Kernel updated to 6.18.64-Unraid, among 59 package updates

We recommend this update for everyone running 7.4.0.

Blog | Release Notes | Updating Unraid | Bug Reports


r/unRAID • • 6h ago

Is the Mover hogging all IO resources theoretically a fixable problem?

4 Upvotes

There is a long running issue that when the mover runs, it has highest IO priority and makes other disk read/write operations slow and unstable:
- https://forums.unraid.net/topic/186560-mover-consumes-all-disk-iousage-causing-plex-to-buffer/
- https://www.reddit.com/r/unRAID/comments/1jfufjj/mover_hogs_100_of_disk_io_preventing_all_other/

- https://www.reddit.com/r/unRAID/comments/1jjf3zn/mover_consumes_all_disk_bandwidth_causing_issues/

- https://forums.unraid.net/topic/147815-mover-crash-smb/

I know that there are some suggestions to use mover tuning to change priority, but if I recall, that changes it to using a form of rsync to move files which can cause stale file handles and other problems.

Is this issue just inherent to FUSE with no solution, or can it theoretically be solved by the Unraid team?


r/unRAID • • 11h ago

Is it possible to someone build an All-In-one ARR stack as single download from community apps?

0 Upvotes

That would help the community out a lot. Just curious if it could be a possibility?


r/unRAID • • 14h ago

Removing Community Applications plugin

0 Upvotes

I recently started moving up the stack and just using docker for everything and I kinda realized I do not need the Community Applications plugin any more.

I removed it - Am I missing out on anything?


r/unRAID • • 15h ago

PWM Fan Control Plugin

51 Upvotes

For years I’ve maintained a fan control script for User Scripts that sets PWM fan speeds based on disk temperatures. Quite a few people have started using it, and it has served me well, but it had some shortcomings:

  1. Configuring fans meant using the terminal, which could be tedious.

  2. The “Airflow” dashboard widget (Dynamix System Temperature) only showed “Fan 1”, “Fan 2”, “Fan 3”…, so it was hard to remember which fan was which.

  3. Keeping the script updated across multiple servers was a hassle.

  4. It only used disk temperatures, not other sensors such as GPUs.

  5. It sent no Unraid notification when a fan stopped working or something else went wrong.

I’ve now retired the script in favour of a dedicated PWM Fan Control plugin, which fixes all of these issues and adds more. If you need to control your fans, you can find it here:

https://github.com/IDmedia/pwm-fan-control

Note: As for GPU only Nvidia is supported as I don't have anything else to test with :)

I run this plugin on both of my Unraid servers. If you find it useful, please star the repo, and open an issue if you run into any bugs. :)


r/unRAID • • 19h ago

Unraid Disk notification review help

4 Upvotes

I got the following warning in Unraid, is my SSD done? How can I re-test or re-verify it?

Unraid Cache disk SMART Health [187]
Warning [Tower] - uncorrectable error count it 27


r/unRAID • • 20h ago

Does Unraid prevent drive re-writes on file move between sub-folders if root folder in the same?

2 Upvotes

If I have a “download” sub-folder and “media”sub-folder under one parent folder “Main”.

Then I got the ARR stack download files and move files from download to media.

Will Unraid re-write the whole file or just point to it in media file without re-writing file? The goal is to prevent drive wear and tear.


r/unRAID • • 1d ago

Static route to a 10Gb PC only works on shim-br0, not br0. Is this expected with “Host access to custom networks”?

2 Upvotes

Setup

  • Server at 192.168.50.70 on br0 (bridging enabled)

  • Docker custom networks: br0, br0.60, br0.100 (ipvlan), with Host access to custom networks enabled

  • A container (reverse proxy) runs on br0 (192.168.50.15)

  • The PC is on a different subnet, 192.168.10.69. The server and PC talk directly over 10Gb through an L3 switch that has an interface on each subnet (192.168.10.2 and 192.168.50.2). Everything else goes through my OPNsense router.

  • On Unraid, I add a host route at array start through User Scripts: 192.168.10.69/32 via 192.168.50.2. Routes added in the Network Settings routing table don’t survive a reboot for me.

Problem 1: br0 Docker network missing after reboot
When my script added the route early (dev br0), Docker never created the br0 network, so my br0 container couldn’t start. br0.60 and br0.100 came up fine. It looks like Unraid detects br0’s Docker subnets from the routes on br0 (DOCKER_AUTO_BR0="4", no DOCKER_SUBNET_BR0), picked up my host route as an extra subnet, and the network creation failed. Removing the route before Docker started fixed it.

Problem 2: route on br0 works, then dies
With the route on dev br0, an iperf3 test ran at about 9.4 Gbit/s for about 8 seconds and then the connection reset. After that, nothing from the PC could reach the server, while other devices (going through the router) were fine. On the server:

192.168.50.2 dev shim-br0 lladdr 6c:4c:bc:45:26:fa STALE
192.168.50.2 dev br0 FAILED

My understanding: shim-br0 is ipvlan, so it shares br0’s IP and MAC. The ipvlan driver hands frames addressed to .70, including ARP replies, to shim-br0. br0’s ARP entry for the switch is never confirmed, expires, and goes to FAILED.

What fixed it

ip route replace 192.168.10.69/32 via 192.168.50.2 dev shim-br0

Unraid’s own default and LAN routes are already on shim-br0 (metric 0) with br0 as a fallback (metric 1009), so this seems to match the design. My scripts now:

  • At array start of array, wait for shim-br0 to exist, then add the route.

Questions

  1. Is routing host traffic through shim-br0 the intended or supported approach when host access is on, or is there a better way to add a static route in this setup?

  2. Is my explanation of the br0 ARP FAILED / shim-br0 STALE behavior correct?

  3. Is there a supported way to make a static route persist and survive Docker restarts, instead of using User Scripts?

  4. Is the br0 Docker network failing because of a host route on br0 a known issue? Should I set the br0 subnet manually somewhere to avoid it?

Basically, do you guys who use custom networks use shim-br0 for everything or do you use br0? It seems like once I added br0 in order to give my reverse proxy it's own IP address, everything switched to shim-br0. Just trying to verify that is normal.


r/unRAID • • 1d ago

[7.4.1] Containers with "Use Tailscale" enabled are unreachable from LAN on published ports

35 Upvotes

After updating to 7.4.1, every container with the built-in "Use Tailscale" option enabled became unreachable from my LAN. Containers without Tailscale work normally. Turning Tailscale off on a container restores LAN access immediately.

Affected: sonarr (binhex), radarr (binhex), Seerr (hotio), backrest (garethgeorge). They are on two different networks (custom bridge "easyflow" and default "bridge"), so it doesn't depend on the network or the image.

Tailscale settings on the affected containers:

- Exit node: not used (neither being one nor using one)

- Userspace networking: Disabled

- Tailscale SSH: No

- Tailscale Serve: Serve (e.g. port 8989)

- TAILSCALE_ALLOW_LAN_ACCESS=false (set automatically, no option shown in the template since no exit node is set)

What I tested (sonarr, port 8989, server 192.168.1.40):

- The app runs normally and outbound connections work (it talks to Prowlarr and NZBGet).

- From the Unraid host: curl http://localhost:8989 and http://192.168.1.40:8989 both return HTTP 401 (expected, so the app responds).

- Port mapping and DNAT rule are present (0.0.0.0:8989 -> 172.19.0.19:8989), DOCKER-USER is empty.

- From another PC on the same subnet (192.168.1.28): connection to 192.168.1.40:8989 times out. Port 80 on the same server works.

- Inside the container, table 52 contains only /32 routes to tailnet peers (no default route), and iptables only has the standard ts-input/ts-forward chains.

- Setting "Use Tailscale" to OFF and applying: LAN access works immediately.

This all worked before the update. Workaround for now is disabling Tailscale per container and running Tailscale on the host instead.


r/unRAID • • 1d ago

Getting an Error when looking for new Apps

4 Upvotes

I am on version 6.11.5 and when I go to the Apps tab to search for new apps I get the following error come up.

<br /> <b>Fatal error</b>: Allowed memory size of 268435456 bytes exhausted (tried to allocate 35655680 bytes) in <b>/usr/local/emhttp/plugins/community.applications/include/helpers.php</b> on line <b>63</b><br />

Any idea what I can do to resolve this?


r/unRAID • • 1d ago

What License to get, with or without lifetime updates?

8 Upvotes

What license is everybody on?
The one for 250 with lifetime updates?
Assuming they font do Black Friday deals in those Licenses?


r/unRAID • • 2d ago

Camera recording advice please

0 Upvotes

Hey guys, I’m new into the camera doorbell/ camera world and have been wanting some for a while. Amazon are running a blink outdoor camera and doorbell for £25. Could this be hooked up to my Unraid server to record?

Worth it or stay away?

If so what containers are best to try?

Thanks.


r/unRAID • • 2d ago

Synology DS925+ nach wenigen Monaten kaputt – UGREEN DXP4800 Pro oder Dell OptiPlex 7000 Micro mit Unraid?

Thumbnail
reddit.com
0 Upvotes

pls help me🙏


r/unRAID • • 3d ago

Power consumption 7.3.5

2 Upvotes

My N100 uses about 5W more with 7.3.5 than with 7.3.4.

Is this just an isolated case, or has anyone else experienced this?


r/unRAID • • 3d ago

Backup server, how to transfer data?

7 Upvotes

Hi everyone,

I currently have a main server running Unraid, which is backed up to a Synology NAS using rsync scripts scheduled through cron once a week. I also use Synology Snapshot Replication after each weekly transfer to keep historical versions of the data.

Long story short, I'd like to get rid of the Synology NAS and replace it with a second Unraid server dedicated to backups.

I'm wondering what would be the best way to implement this weekly backup setup. I've already looked into Kopia and Restic + Backrest, both of which seem quite interesting. I could keep using my existing rsync scripts, but I suspect there might be a cleaner and more robust way to do this.

What would you recommend?


r/unRAID • • 3d ago

Is the UGREEN NASync DXP6800 Pro a viable option for a Jellyfin ARR Stack Unraid NAS

2 Upvotes

Jellyfin will have up to 6 concurrent users.

I'm a complete noob to Unraid and Jellyfin but I want to host my own media Server.

I'm overwhelmed by options right now, from building my own NAS out of an old PC to repurposing an old mini PC with a NAS (involves soldering according to a post I found on reddit.) I can solder just worried I dont know the reason for what im soldering.

Is there anything proprietary about UGreen I will regret further down the journey?


r/unRAID • • 3d ago

GMKTec Nucbox Unraid Issues

Thumbnail
gallery
2 Upvotes

Hi, can someone please help me figure out why I can't turn off fast boot in my GMKtec Nucbox? Been trying to install Unraid on it for weeks but it keeps stalling at the boot screen. I've looked everywhere online and I'm hoping disabling fast boot fixes it. (I've already disabled fast startup in windows, yet bios still shows fast boot enabled. Any assistance would be greatly appreciated.

Edit: The USB boots on my 10yr old Dell laptop but stalls on my GMKTec.


r/unRAID • • 3d ago

unraid won't boot to UEFI USB but I can manually boot the USB UEFI partition in the boot menu. What gives?

3 Upvotes

I had to switch from BIOS-CSM to UEFI to get resizable bar working, but now unraid doesn't boot automatically into UEFI, even though the USB is selected in the boot order in BIOS. I can only boot into unraid if I manually go into the boot menu and select the USB UEFI boot option.

CSM is disabled, Secure-Boot is set to other OS.

I'm all out of options and the only other things I have left to do is try another USB.

Anyone else ever ran into this?

SOLVED: Disabled fast mode and everything booted up fine.


r/unRAID • • 3d ago

If your unraid is internet facing be aware unraid is running an exploitable version - nginx2root.com

184 Upvotes

This new RCE dropped today - https://nginx2root.com

Unraid 7.4.0 is running nginx 1.30.6 which is impacted.


r/unRAID • • 3d ago

Brand-new 8TB WD Red Plus not detected in Unraid OR motherboard BIOS — am I missing something?

4 Upvotes

I'm hoping someone here might have an idea before I conclude I've received a defective hard drive.

I'm adding a brand-new 8TB WD Red Plus NAS drive to my Unraid server. The plan was to preclear it and add it to my existing array, but I cannot get the drive to be recognized at all.

System specs:

- Unraid: 7.3.3

- Motherboard: MSI PRO Z790-P WIFI (MS-7E06)

- CPU: Intel Core i5-13600K

- RAM: 64GB DDR5

- PSU: Gigabyte UD1000GM, 1000W

- Storage controller: LSI SAS controller with SATA breakout cables

- BIOS: MSI Click BIOS 5, E7E06IMS.AC0 (April 16, 2024)

Existing storage:

- Parity: 10TB WD Red

- Disk 1: 8TB WD

- Disk 2: 6TB Seagate

- Disk 3: 4TB WD

- Disk 4: 4TB WD

- Cache: 1TB Crucial P3 Plus NVMe and 1TB SATA SSD

All existing drives are detected and functioning normally.

The problem:

I installed the new 8TB WD Red Plus in an available drive bay and connected it to the LSI controller using an available SATA breakout connection.

The drive does not appear under Unraid's Unassigned Devices or Tools → System Devices.

I can feel a continuous, gentle vibration from the drive, suggesting that it is spinning.

What I've tried:

  1. Reseated the SATA connections.

  2. Tried two different breakout connectors (P2 and P4) on the LSI controller cable. Other drives connected through that breakout cable are working.

  3. Connected the new drive directly to an available motherboard SATA port using a standard SATA data cable, bypassing the LSI controller entirely.

  4. Checked the MSI BIOS under Settings → System Status. The BIOS detects an existing WD drive on SATA Port 5 and the NVMe SSD, but the new drive is not detected on any SATA port.

  5. Checked BIOS settings. Intel VMD is disabled, and nothing obvious appears incorrectly configured.

  6. Tried a different SATA power connector on the same PSU cable chain. That cable also powers a functioning cache SSD.

  7. Rebooted multiple times with no change.

The new drive has never appeared in either Unraid or the motherboard BIOS.

Current thinking:

I'm leaning toward a defective drive, but I find that surprising given that it's brand new.

I've also considered the SATA 3.3V Power Disable issue, although the drive appears to spin continuously, which makes that seem less likely.

My next planned test is to temporarily connect the new drive to the known-working SATA data and power connections from an existing drive, then boot directly into BIOS to see whether it's detected. I'll restore the original drive before starting the Unraid array.

My questions:

- Has anyone encountered a similar issue with a WD Red Plus?

- Is there anything specific to this MSI motherboard, LSI controller, or SATA power configuration that I might be overlooking?

- Is there another diagnostic step worth trying before I return the drive?

I'd appreciate any suggestions. I'm trying to rule out everything reasonable before declaring a brand-new drive DOA.

Thanks!


r/unRAID • • 4d ago

Unraid 7.4.0 and the Mover question

Post image
17 Upvotes

Mover is taking 105% CPU, I have turned on logging and mover progress.
From you patch notes said it should be able to see mover % in the shared task tray but there's nothing.

I got a Netdata alert about this then had to SSH into my server and do various checks.
eventually i could do "cat /tmp/mover-files.oYae2F" to find the files mover was moving but it a massive list and no idea if its getting shorter or just listing all the files 

Am I missing something.

The only Info Unraid webui show's about mover is mover is running with no other info at all.

apart from write activity on my cache drive.


r/unRAID • • 4d ago

Appdata Backup Plugin now works with Unraid 7.4

141 Upvotes

Hi all,

Just wanted to post here because I'm not sure many people read the support forums but Appdata Backup Plugin is now compatible with Unraid 7.4 and contains a handful of QoL improvements and some improved functionality.

https://forums.unraid.net/topic/137710-plugin-appdatabackup/page/90/#findComment-1642180

EDIT: Just to be clear, the release from March did work for Appdata backing up but the flash backup was what was broken.


r/unRAID • • 5d ago

Server shut itself down after waking up from sleep

1 Upvotes

Hello there,

I have been using the S3 plugin to manually put my NAS to sleep everynight and wake it up the next morning with a keyboard/power button for years with no issues on actual hardware. After I installed a new 10gbe PCIe nic a few days ago (ASUS XG-C100C), the server turn itself off after waking up from sleep, everytime. It doesn't happens randomly, but always. Also, it's a normal shutdown. So the array stops, and the regular safe shutdown happens. By the time I access the webgui, nothing can be done to halt the graceful shutdown process, it shows the array stopping, but I can still see the log, access the terminal...etc.

 

This is my actual setup:

  • Unraid Version: 7.3.4

  • CPU: AMD Ryzen 7 PRO 4750G

  • Motherboard: ASUS Strix B550-XE

  • Memory: 1x32GB 3200 DDR4 ECC

  • PCIe Slot 1 (CPU): ASUS NVME card (come with the mobo)

  • PCIe Slot 2 (CPU): HBA

  • PCIe Slot 3 (Chipset): ASUS XG-C100C

Like i said before, the issue only started after adding the new NIC. More info on the actual situation:

  • To be sure, I booted on the baremetal Windows install on the computer, tested everything, and put it to sleep. Resuming from sleep on Windows 10 doesn't do anything special, it works as expected. The card is also working perfectly on both Windows10 and Unraid.

  • The 10gbe is directly connected to my desktop one (ASUS X570 ProArt), and both machines are connected to the switch via their 2.5Gbe nics for internet.

  • WOL is disabled since I don't use it.

  • CPU PCIE ASPM Mode Control is set to Auto on BIOS, never changed this setting.

This id driving me crazy, I spent hours using Ai chatbots and checking the forum here and the Unraid Reddit, but haven't found anything. I may buy a used x540 nic (x550 are too expensive used, their price increased in the last year) to test and compare, but I am affraid it will cause the same issue.

If anyone can help me get to the bottom of this I'd greatly appreciate it. Thanks in advance!

EDIT: Diagnostics and Syslog added.

- Diagnostics: https://drive.google.com/file/d/1bhFTO8bAZKxHu5QHzlV4eXL-lUXHzp4z/view?usp=sharing

- Log: https://drive.google.com/file/d/1H3oNKQ-J6FV-Dk7KVVaV323DqFz3VOTd/view?usp=sharing

EDIT: Solved, thanks to someone on Unraid forum nailing it!

The issue was somehting I would have never excpected, S3 sleep after wake-up commands, which is related to fans speed! you can find the post here: https://forums.unraid.net/topic/201322-server-shut-itself-down-after-waking-up-from-sleep/

The plugin was trying to run a command with hwmon5, which changed to 6 after installing the new nic. Original answer from the forum moderator:

Why it started with the new NIC: the Aquantia driver registers its own temperature sensor. It loads before nct6775, which your go file loads, so the nct6775 sensor most likely isn't hwmon5 anymore. Your commands now write to a path that doesn't exist, the echo fails, and the plugin shuts the server down. To confirm, please run:

ls -d /sys/devices/platform/nct6775.656/hwmon/hwmon*

If it shows anything other than hwmon5, that's the problem. To fix it, replace the custom commands after wake-up with these. They don't depend on the hwmon number, and the final true means a failing command can never cause a shutdown again:

for d in /sys/devices/platform/nct6775.656/hwmon/hwmon*; do
echo 1 > $d/pwm4_enable
echo 35 > $d/pwm4
done
true
Then test sleep and wake again.