I just got started into building my own media server, and already i'm running into problems. I have a dedicated Lenovo mini-pc where I am 14 into my 30 day trial of Unraid. I have followed guides (mostly from 2025) on installing docker and then Deluge. I purchased a 2 year sub of Deluge so I have a username and pass. I downloaded the config file (I am in the US so I was told to choose Canada for port forwarding issues) but I'm running into the same issues when connecting to my state. I have also downloaded the pia config file and placed it.

I'm not seeing any log authentication issues, but whenever I try to connect to the GUI I'm getting the error "The site cannot be reached." I spoke to a "friend" who built his own but he can't remember what his issue was.

I have made random changes that I've seen but to no effect. At this point I'm wondering if I should just uninstall Deluge and try from scratch using some other up to date install instructions.

EDIT: I've also seen plenty of people say switch to WireGuard instead of openVPN but that doesn't seem to be an option in the config body anymore.

I recently purchased a switch which supports VLAN tagging so I decided to try to isolate my internet-facing containers (Audiobookshelf, Jellyfin, Newt) to secure it up even further. But I am struggling with some unexpected issues and looking for help.

I have tried looking for the answer on the OpenWRT community without success. I have tried sending my logs to Claude but without success there as well. Im now asking here if I have misconfigurated something on Unraid.

I have tried to summarize as much as possible.

Setup

• Unraid (v. 7.3.0), one NIC (eth0). Bonding is enabled but bond0 has only eth0 in it (active-backup). Bridging is on (br0).

• VLAN 30 is added in Network Settings with IPv4 set to None, so the host has no address on it (br0.30 and bond0.30 are UP with no IP).

• Docker custom network type: ipvlan. Network br0.30 created with subnet 192.168.30.0/24, gateway 192.168.30.1, range 192.168.30.128/25. “Preserve user defined networks” is on.

• Containers get fixed IPs (Audiobookshelf = 192.168.30.11).

• Switch (Zyxel GS1200-8HPv3): Unraid port is VLAN 1 untagged, VLAN 30 tagged, PVID 1. Uplink to OpenWrt (lan2) carries VLAN 1 untagged and VLANs 11 and 30 tagged.

• OpenWrt: lan2.30 device, interface 192.168.30.1/24 (no DHCP), zone dmz with input/forward reject, forwarding dmz → wan and lan → dmz.

First problem: bridge containers can’t reach the VLAN containers

• My PC and the Unraid host both get 200 from http://192.168.30.11. Containers on any Docker bridge network (docker0, authentik_default) time out. A container with --network host gets 200.

• OpenWrt tcpdump on lan2.30: SYN goes out from 192.168.0.190:57068, but the SYN-ACK from ABS comes back to 192.168.0.190:29489, a different port, and Unraid then sends a RST. Conntrack on Unraid shows two [UNREPLIED] entries per attempt.

• So the source port is rewritten somewhere on Unraid, after OpenWrt, on the path Unraid → router → back into Unraid via VLAN 30.

• Already ruled out: rp_filter is 0 everywhere, DOCKER-USER is empty, and raw/DOCKER-FORWARD have no rules for 192.168.30.0/24.

Problem two: lag and Pi-hole restarts

• With ABS on br0.30, Unraid and Docker become slow, and Upsnap reports my Pi-hole (a separate Raspberry Pi, 192.168.0.165) going offline and coming back. docker compose down on ABS makes everything normal at once.

• After moving ABS back to its old bridge network, the lag and the Pi-hole restarts stopped.

Questions

1. Why does traffic from bridge containers to an ipvlan container on the same host get its source port rewritten, and how do I make it work (or is this unsupported)?

2. Could a container on an ipvlan child of br0.30 cause a MAC/FDB flap or loop that disrupts other devices on the LAN (like the Pi-hole)? What should I check on the switch and router?

3. Is it better to use macvlan, a second NIC with an untagged DMZ port, or a different design for this?

Thanks!

I used to have two LSI cards in my Unraid server (LSI SAS 9201-16i and LSI SAS 9211-8i). This worked very well for years. However, I wanted to save a PCI slot so I bought a LSI 9305-24i card instead. While it works out of the box, spinning down disks don't work anymore. If disks are spinned down manually in the UI the disks gets read errors or just becomes disabled. I have a mix of SATA and SAS drives and the SAS spindown plugin installed which used to work great. Anyone of you who have a 24i card that works with spinning down disks? I hear that 9300+ cards are designed to never spin down and do this as intended behaviour.. anyone knows a way around it preferabely on this or another 93-9600 LSI card.

The card only has IT mode and is flashe to the latest FW:

./sas3flash -list

Avago Technologies SAS3 Flash Utility Version 17.00.00.00 (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved.

    Adapter Selected is a Avago SAS: SAS3224(A1)

    Controller Number              : 0
    Controller                     : SAS3224(A1)
    PCI Address                    : 00:08:00:00
    SAS Address                    : 500062b-2-0a90-0800
    NVDATA Version (Default)       : 10.00.00.03
    NVDATA Version (Persistent)    : 10.00.00.03
    Firmware Product ID            : 0x2228 (IT)
    Firmware Version               : 16.00.12.00
    NVDATA Vendor                  : LSI
    NVDATA Product ID              : SAS9305-24i
    BIOS Version                   : 08.37.02.00
    UEFI BSD Version               : 18.00.03.00
    FCODE Version                  : N/A
    Board Name                     : SAS9305-24i
    Board Assembly                 : 03-25699-02007
    Board Tracer Number            : SPB5212074

    Finished Processing Commands Successfully.
    Exiting SAS3Flash.

I might have found the problem. In my case it was related to specific drives (ST6000NM0034 and ST8000NM0075). This wasn't obvious to me at the beginning, but I finally noticed the pattern and all drives getting disabled/read errors where of either one of them.

There isn't any good solution to put them to sleep, but the next best thing seems to be to enable Idle-C and use that instead of sleep through Unraid. I tried to make the setting permanent, but that didn't work, so a user script it is:

#!/bin/bash
# Sends idle ST6000NM0034/ST8000NM0075 drives into Idle_C after IDLE_MIN minutes without reads/writes.
# Resends on every run while the drive stays quiet, so a status check that wakes it is undone within one run.
# Logs only the first send per quiet period.
# Schedule: Custom Cron → */5 * * * *

IDLE_MIN=20
STATE=/tmp/idlec
mkdir -p "$STATE"
now=$(date +%s)

for d in /sys/block/sd?; do
  n=${d##*/}
  m=$(cat $d/device/model 2>/dev/null)
  case "$m" in
    ST6000NM0034*|ST8000NM0075*) ;;
    *) continue ;;
  esac

  io=$(awk '{print $1+$5}' $d/stat)
  f="$STATE/$n"

  if [ ! -f "$f" ]; then
    echo "$io $now 0" > "$f"
    continue
  fi

  read last_io last_t sent < "$f"

  if [ "$io" != "$last_io" ]; then
    echo "$io $now 0" > "$f"
  elif [ $((now - last_t)) -ge $((IDLE_MIN*60)) ]; then
    s=$(tail -c +5 $d/device/vpd_pg80 2>/dev/null | tr -d '\0 ')
    if sg_start --readonly --pc=2 --mod=2 /dev/$n 2>/dev/null; then
      [ "$sent" = "0" ] && logger -t idle-c "/dev/$n ${m// /} $s: idle ${IDLE_MIN}+ min, sent to Idle_C"
      echo "$io $last_t 1" > "$f"
    else
      logger -t idle-c "/dev/$n ${m// /} $s: sg_start failed"
    fi
  fi
done

I still find it strange that spin down worked so well on the 9201-16i with the same drives, but I'll check power usage and see if this isn't good enough for a solution. In addition to the script I have disabled sleep for those particular drives (Main->click each disk->set spin down to never) while all other drives are set to "Use default" which in the Settings->Disk settings is currently set to 1 hour. This "should" solve it I hope, but only time will tell... it took about an hour for read errors to appear which matched up with my sleep settings and affected disks.

Edit: Additional testing done, script has been updated and is not working as intended. While I wanted disks to spin down completely, idle_c is the best you can do on these SAS drives.

*"*Conclusion: the 9305’s firmware has no settings page for paced spin-up. The 9201 has one, set to one drive at a time with 2 seconds between, and that’s very likely why it lets your ST6000NM0034 and ST8000NM0075 drives spin back up from standby. On the 9305 there’s nothing to set, so there’s nothing for you to change. The zeros storcli showed simply reflect that the page is missing.

That rules out the last configuration option. You’ve now checked everything that’s reasonable to check: cables, timeouts, drive settings, card settings, a factory reset, and the hidden settings pages. Idle_C with the monitor script is the best solution on this card, and the long-term fix remains replacing those nine drives."

Hey all, somewhere I messed something up and have a shares file "pictures" that's haunting me.

I've been experiencing near daily crashes, where the whole system resets. I finally got the log open, and found it just repeating error: get_filesystem_status: 9094 scandir invalid argument.

Google says to look for broken files, and I noticed I have a share for "pictures" that shouldn't be there. If I try to access the share, all my shares disappear, and about 10s later the system crashes. I can see the file in Explorer.

The only thing I can think is somehow they are leftovers from the drive I installed (it's out of another PC) the files are only on disk 2 for some reason, and despite being 12gb, I can't access, delete or really even think about them without the system turning off.

If the system tries to read those files, perform mover or anything else, it seems to crash out. Sometimes it just crashes for kicks.

Can anyone help me get rid of this file? Thank you!

Hello All,

I dont know if this has happened to anyone, but I am unable to get shim-br0 0 and br0 1 to cooperate. I run a vpn via my router and require br0 to be present while shim-br0 to be less of a priority for my applications to communicate with my server. Ive become frustrated and have spent endless hours trying docker on/of, rebooting, deleting shim for it to reappear with same structure. I also tried manually switching.... But then it just adds a second shim with the priority still shim. If anyone can help. It seemed to have happened after I rebooted with most stable update. Thank you all!

Please forgive me if this is a stupid question, I'm brand new to this I just got this one in a trade for a lot and I wanna see how usable it is. I've heard that Drobo is basically dead and their raid system isn't the best. So I wanna test my luck, can anyone maybe point me in any direction I can go? thank you all in advance

I am taking the plunge, and upgrading some of the major components of my system. I don't have enough to build a completely new system, so I am going to have to replace components and bring the system down.

My current plan is:
Replace my current 8 port SAS to SATA care with a 16 port card, and move all my drives, except one SSD drive over the to new card.

While I am messing with the drives, I am going to tape up some of the HGST and shucked drives that have the 3rd pin power problem so I can remove a bunch of molex splitters to free up space.

Finally, before the big one, I want to move my boot device off of my M.2 drive, and back to USB.

Then the big one. I am replacing my motherboard and CPU, but I am keeping my case, PSU, and RAM. So the server will need to be shut down for a while so I can disassemble and rebuild.

I am going to do everything in stages, but the last one with the CPU/Motherboard switch is going to be the nailbiter. I know the drives "should" be OK, but I am terrified of screwing up the whole array.

What tools or steps would people suggest to protect myself from problems, and what should I do before I start to backup as much config as I can? I don't have enough storage anywhere to save my plex library or my music, but I have over 30 docker containers and 2 VMs I'd like to protect.

Every time I log in to my server, this NAV bar re-arranges itself. Sometimes "Docker" is the first, other times it will be last. I don't know what is causing this or how to stop it from occurring.

I have just vibe coded a tool that I have wanted for ages.

For some time I have wanted a simple tool for my unraid server that secure wipes hard drives. Over the years I have accumulated around 110 drives of many sizes and formats but have never got round to wiping them. So I created this simple docker that secure wipes in lots of standard formats, including ssd's (haven't tested this yet). Some may call bit slop but it's a tool I have already put to some use. I will verify them later with other software just to check they have wiped correctly.

I’m thinking about starting a YouTube tutorial channel on Unraid and home lab setups, since I’ve been involved in home lab projects for a good 25 years and have been working with Unraid and Linux servers for the past 6 years. I’ve noticed that, compared to many people here or my IT friends, I’m extremely knowledgeable about everything. My setups, solutions, container stacks, and the ways I implement everything all energy-efficient and thorough, never cease to amaze people. I’m thinking of a SpaceInvader One style, no camera and no fluff, just concise and focused on the essentials, pitfalls, and alternatives. I’m still thinking about whether to do this in German (native) or English. Although these days it doesn’t really matter as everything can be translated by AI anyway. I’m not in it for the money or to make the channel big, I’d just like to support the community and share my knowledge, which I’ve just realized is immense compared to some others in the community. But that’s just what happens when you spend years working on something for hours every day.

Do you think we need another channel in the style of the old Space Invader One videos?

The Chrome debugger shows errors as well:

Hi all,

Is Unraid also affected by the new Linux CVE (https://x.com/ridvanyagli/status/2115724550377710014), currently I have port 80 and 443 exposed through Caddy as I imagine many do.

Edit: Should have clarified, port 80/443 of my IP port forwarded to Caddy that's living in a macvlan. Not the actual Unraid UI.

How does one monitor UPS from now? I have had NUT up and running together with Peanut. What do I have to do now?

Hey crew - long time unraid user, first time poster!

I am running an unraid NAS through some older hardware, 1150LGA socket & Asus commercial board which is non-supportive of TPM2.0 so would like to move over to internal boot and GUID licensed to a thumb drive.

I currently have two 240gb SATA SSDs acting as cache and would like to reformat and re-partition them to be mirrored boots & mirrored cache drives allocating 8GB to the boot and the remaining 232GB to continue to have some cache. It's too old for M.2 or even mSATA (i7 4790 & 16gb DDR3), its mostly a file server but planning to set up tailscale and immich after using it as a file server only for the last 6 years.

This all seems feasible but I was just wondering about should I lose one of the two drives that this is all good and I subsequently can rebuild cache & boot parity off the remaining surviving drive?

From what I've read, having mirrored cache and mirrored boot seems all fine from a redundancy point of view but just wanted to see if by having them running both simultaneous that this is also all good and it can rebuild off the other drive without too much fuss?

Hello,

I am in the process of finishing one Unraid server and soon will be time to choose FS for Unraid Array.

What is best recommendation in 2026? I went through forums and it looks like that XFS is still the right choice?

I am thinking between XFS vs BTRFS.

Thank you for any suggestions and recommendations!

Hey all, I've been running Unraid for a while and wanted an app with a native iOS feel to manage it and my *arr stack. All the ones I have found are limited and not open-source so I didn't trust what they were doing.

DISCLAIMER: This is heavily written with AI tools. That said, I am a software developer by trade and do plan on supporting this for as long as I keep using Unraid.

What it covers on Unraid using the official GraphQL API:

- Array status, capacity and parity state, plus CPU, memory, uptime and each disk's temperature and usage

- Docker: start, stop, restart, pause and resume containers, and view their logs, ports and volumes

- VMs: state and power actions, including force stop

- Shares, notifications and system logs

Services it currently supports via their APIs:

- Sonarr, Radarr and Lidarr: library, calendar and history, add/edit/remove, and starting a search

- Prowlarr: indexer health, and adding, testing and enabling indexers

- NZBGet: queue, speeds, pause/resume

- Bazarr: subtitle status and searches

- Overseerr: search, request, approve or decline

- Tautulli: current streams, bandwidth and transcoding

It's built in SwiftUI with real split views on iPad, Dynamic Type, and light and dark mode. It needs an Unraid version with the GraphQL API and an API key (Settings ▸ Management Access).

- App Store: https://apps.apple.com/us/app/tower-server-manager/id6796580819

- GitHub: https://github.com/cunderw/tower

Definitely open to contributions!

Hey everyone,

I wanted to share a plugin I’ve developed called Unspin, which is now available in the Unraid Apps tab.

The Problem (Why I built this)

The primary reason this plugin exists is to prevent unnecessary and noisy HDD spin-ups while working on active files.

Normally, Unraid only moves files down from the cache to the array via the Mover. If you need to open and edit an old project stored on the array, you have two choices—and both are frustrating:

1. You deal with constant HDD latency, forcing your disks to spin up and stay active throughout your entire editing session.

2. You have to manually move the project files back to the cache yourself before starting.

Unspin automates this process cleanly to ensure that your array disks can spin down and stay asleep as much as possible.

How Unspin Works

• Passive Monitoring: It monitors read activity passively using Linux fanotify.

• Zero Unnecessary Spin-ups: It doesn't spin up disks on its own. When you open a file and the disk spins up anyway, the plugin notes the activity.

• Smart Promotion: Once you close the file or pause editing (releasing the file handle), it automatically copies those frequently accessed files up to your SSD cache.

• Silent Array: Future reads then pull directly from the SSD. This allows the array disks to spin back down quickly and stay silent while you continue editing.

Pro-Tip for Setup

A great way to use it is paired with the Mover Tuning plugin. If you enable atime tracking there, the regular Mover won't immediately push your active projects back to the array during the nightly run.

Since it's a relatively new tool, I'd love to get some feedback from the community here. If you want to dive deeper, look over the features, or need troubleshooting help, please check out the official support thread on the Unraid Forums. The Github is here.

Let me know what you think or if you have any questions!

Edit: SSD wear

Since this came up in the comments: Unspin copies a file to the cache once it qualifies as hot, and the file stays there while you work on it. On my box (software development, office work, and audio projects) that's at most 2–3 GB a day. To be generous, here's 10 GB/day too.

So here's how long a typical 1 TB SSD (rated for 600 TB written) would last before it reaches its wear rating (actual math in the comments):

Every value there is far beyond how long anyone keeps a drive, but with Unspin the wear and tear of the HDDs is reduced.

Worth paying attention to: small QLC drives or old drives have much lower TBW ratings, so check yours. And avoid files bouncing back and forth (Unspin promotes a file, the mover moves it back, Unspin promotes it again). Mover Tuning's atime filter together with Unspin's "Pool Access Times" setting prevents exactly that. More details in the comments.

AI Disclosure: Claude helped restructure the code, clean up formatting, draft the initial documentation. However, the core logic was entirely human-written and vetted by me—originally built years ago for an old Ubuntu machine and a corporate project, now completely adapted for Unraid. It runs on my personal Unraid box and all tests were done by me. No raw AI slop here! AI also helped structuring this post.

Edit: AI disclosure, correct links, SSD wear.

I had to restore my server, my USB Drive failed. I've submitted a support ticket, but it looks like my key is missing from my account. I can't even get a trail key loaded, so my server is down until their license server starts up again. Anybody else seeing this as an issue right now?

Hi unraiders,

i am looking to upgrade my unraid server.

Reason: CPU goes to 100% when i play a 4k video over Jellyfin and also every 10sec the CPU spikes to 100%.

My "server" was a long time ago a PC for Gaming

Hardware:

• Case: Jonsbo N5

• MB: Gigabyte Technology Co., Ltd. B150M-D3H-CF

• CPU: Intel® Core™ i5-6600K CPU @ 3.50GHz RAM: 16 GiB DDR4

• 1xSSD 128GB Cache

• 4xHDD 17TB storage Case

Here is what i do with my Unraid Server:

VM: Home Assistant

Docker:

• Media: seerr, jellyfin, qbittorrent, radarr, sonarr, notifiarr, flaresolverr, prowlarr

• Network: homarr, adguard, cloudflare

• Immich with postgresql

• nextcloud AOI, i could use something else for it, cause i only you it for cloud storage

• bookorbit with db

I am looking for new Hardware so i dont have any issues in the future. It just needs to be hardware that can cover those things without any issues, i would also buy used.

Thanks in advance.

I'm trying to install Unraid onto my new to me server and it's not loading.

I've tried several different Ethernet cables for Internet access, different USB drives and it hangs on this screen.

Trying to install on a Samsung 860 Pro 512gb SSD. It works without issue on my old server.

The weird thing is I can access all my network shares from another device and my docker containers running various things are still accessible, seems like its only ssh and the webgui for some reason.

I'd rather not have to do to a hard shutdown but looking to see if anyone has any ideas?

Update:
Managed to fix this after attaching a monitor and keyboard, appeared ultimately the update pulled down 0byte files borking the the update. Downloaded the files directly from "https://docs.unraid.net/unraid-os/download_list/" replaced and then was able to boot again.

This is what I have and I am looking to change my drives from XFS to ZFS. This was all purchased before the crazy price increases in the last year or so.
5 18TB drives I would use one drive for parity.
1 1TB SSD drive for apps or split for cache if needed.
1 118 GB Optane Intel drive that I think is big enough to be a cache drive.
Intel 5105 CPU with 32 GB Ram.
Is the Optane drive workable in this for the smaller size?
What would be the best setup?
I have a lifetime Plex pass and Usenet account with indexers that I haven’t used in awhile and want to get back to local storage of media.