wayner

More hard data from Backblaze https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2025/

Is anyone moving to the new Unifi OS server? It isn't clear to me what has changed now, and how this is different from the previous way that Unifi worked. Is this something that would be useful for the prosumer market, like many of us in this thread?

Hi @Xoron - I am in the same boat as you. I am running the old unifi controller docker version 7.2.95. Is everything still looking good with your system? I might be a little more cautious than you and upgrade to an interim version - the lowest version supported by unifi-reborn, which is 7.5.187(I think) and see how it goes before moving to the more recent versions like 9.5 or whatever.

I deleted the json file, and I try to move things but they keep snapping back to the previous location.

Thanks - that's helpful. I have cable internet that is supposed to be 500/30 but I get speed tests of 900/32. And I think that the USG may even be limiting my WAN speed. I would like WAN speeds faster than 1G to futureproof. Any pros/cons vs having Unifi host the controller in the cloud vs self-hosting? And do you know what controller version you were running in the docker when you switched to the cloud docker? Was there a gap or were you on pretty much the same version? And with step 4 - what does doing an offline setup entail? It seems like you plugged the CGU into your network before actually restoring the backup.

I am still running the "old" docker controller on version 7.2.95 with a USG3 as my gateway and I want to go to reborn and new hardware, but I have a bunch of things to deal with. I posted about a year ago here but I haven't done anything in the last year. (Of course, depending on my hardware I may not need to self-host controller if I went to a cloud gateway). Has anything changed in the last year? There seem to be some new hardware models from Unifi, especially the "fiber" units like the UXG-Fiber and UCG-Fiber. Anything else happen in the last year to change my plan from last year, which was to install the reborn docker and try to restore from 7.2.95 to 7.5.187, which I think is the earliest version that works with the reborn docker? One other option, although I don't know if this is possible, is to upgrade the old Linuxserver.io-Unifi-Controller to 7.5.187, or the closest version possible, before switching to the new docker. But I don't know if the repositories are available to do that.

I was watching the videos when it was first released and the UI looks quite a bit different than today. Has it changed or is that configuration option that I have wrong.

Good questions, I don't know the answer, but I have a related question. What advantages does using Tailscale Funnel have vs opening up a port on your router? Many of us have done this in the past for stuff like Plex or Jellyfin - does it make sense to keep doing things that way or is Funnel more secure.

I just upgraded to 7.2.2. I watched the 1.5 hr long Uncast video on how to use Tailscale. I want to use my Unraid server as an exit node and also have access to the LAN that the Unraid server is on via Tailscale. My settings are pasted below. Under the Use Exit Node dropdown box there are no options. The second and third screenshots are from the Tailscale web UI. Under Routing Settings I am able to set up and approve the exit node. But under the Subnet settings it says waiting approval and when I go into approve the Save button is not active it is grayed out. Note I am not using a docker as an exit node - I only have one docker using Tailscale right now and that is Jellyfin and it is not set up as an exit node. Here is my Tailscale settings screen: Here is the Subnet and Routing Settings for my Unraid server in the Tailscale Web UI Here is what I see when I click the Edit under Awaiting Approval for Subnets Here is the setting for my Unraid server - maybe it is setup properly but then why can't I save?

Just to update this - I had other problems with my system so I upgraded to 7.2.2. Parity check ran this weekend and it looks good for now. I will keep an eye on it.

I created by Linux Mint VM a year or so ago and it is running version 21.2. I want o upgrade it so I installed mintupgrade and when I run it, it wants to "upgrade" me to vanessa 21.0 which is acutally a downgrade as I am on Victoria 21.2. Why won't mintupgrade go to the current vrsion zara which is version 22.2?

I upgraded this morning and all looks well. My SageTV docker is able to tune channels from OTA and HD-PVR tuners/encoders.

Thanks, I have it working now. First I switched to IPVLAN. That didn't fix it. I kept it on that setting and switched the dockers to Bridge, and then to br0 without actually saving. When I then applied the change they started working. Should I keep going on IPVLAN, assuming that it doesn't cause any other issues? Or switch back to MACVLAN? Anything to keep an eye out for with a different network type?

I have upgraded to 7.2.2 with an interim momentary upgrade to 7.0.1. But I still seem to be having the same error - although it is giving a different name for the network device that isn't foundportrush-diagnostics-20251128-1122.zip. In the settings for the dockers that are failing the network type is currently shown as Custom: br0. I want these two dockers to get their own IP addresses. Should I now let docker rebuild the network with the commands shown above in my OP? Is that deprecated (it was from 2018). Is there another way to give those dockers their own IPs these days? This is from my log: Nov 28 11:20:39 Portrush rc.docker: pihole: Error response from daemon: network 5d38b8bd42b3d46eb1e75824772666a658bfd1c7b8f1d89e03a5981c9dee4212 not found Nov 28 11:20:39 Portrush rc.docker: Error: failed to start containers: pihole Nov 28 11:20:39 Portrush rc.docker: sagetv-opendct-java11: Error response from daemon: network 5d38b8bd42b3d46eb1e75824772666a658bfd1c7b8f1d89e03a5981c9dee4212 not found Nov 28 11:20:39 Portrush rc.docker: Error: failed to start containers: sagetv-opendct-java11Attach a new diagnostics file

When I go into Update OS it shows updating to 7.0.1. Do I have to update to that version first, and then go to 7.2.2?

Thanks @ich777 . I will upgrade when I get a chance in the next few days.

Ok - is there anything to be aware of if I am going to upgrade to 7.2.2? I haven't upgraded recently as I haven't sent much time playing around with this system. I have no reason to want to be on 6.12 or any other release.

Thank you very much. When I go to that Git site it says "for Unraid Kernel v6.17.9". How do we know which Unraid Kernel matches up with Unraid version 7.2.2. Can I suggest that someone update or delete Post #2 of this thread, or at least put warnings that it has been deprecated.

Is DVB-Driver available for Unraid version 7.2.2? Post 2 of this thread links to a Github site that shows the versions of this driver, but it seems to be deprecated as it ends at 6.8.12 I am currently running Unraid 6.12.4. I plan to upgrade soon to a more recent version, like 7.2.2. Are there any issues doing that, or do I just upgrade Unraid and then upgrade the DVB-Driver plugin?

I am running Unraid 6.12.4. I appear to have a networking issue - network br0 not found. A couple of dockers that use Custom IP addresses won't start. The either give "Execution Error - No Such Container" or "Execution Error - Bad paramater". Here is a snippet from my log file: Nov 27 19:31:29 Portrush rc.docker: sagetv-opendct-java11: Error response from daemon: network br0 not found How do I fix this? I found a post from 2018 - https://forums.unraid.net/topic/68468-solved-missing-br0-interface-in-gui/ where @bonienl says: rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restartWould that still work? In order to do that command do I have to stop the docker service, or can I do it with the docker service running? portrush-diagnostics-20251127-1832.zip

Thanks, does it make sense to run a parity check and see how it goes? I normally run them overnight on the weekend.

My daily report shows array health report [FAIL] I am getting errors reported for my Parity drive - I believe these happened over the weekend when I have my parity check run. . Yesterday I ran an extended SMART test and in the Web UI under Self Test for that drive it says "Completed with No Errors" My log shows a bunch of errors like this: Nov 23 07:06:59 Portrush kernel: md: disk0 read error, sector=14783168184 Nov 23 07:06:59 Portrush kernel: md: disk0 read error, sector=14783168192 Nov 23 07:06:59 Portrush kernel: md: disk0 read error, sector=14783168200 Nov 23 07:06:59 Portrush kernel: md: disk0 read error, sector=14783168208 Nov 23 07:06:59 Portrush kernel: md: disk0 read error, sector=14783168216 Why would the SMART report say no errors? Does this mean that my drive is dying? It isn't that old, just coming up on four years. Is it time to replace it? portrush-smart-20251126-2247.zip

Awesome, thanks. For now I have avoided having to directly deal with this issue as when I restored the backup to my original USB drive all was well. But this is the original USB key from 2017 on this server - or at least I am pretty sure that it is the original. So it may not last too much longer and the issue that I had where it wouldn't boot may reoccur.

Not necessarily a fix, but I restored an old flash drive backup and now it is working, with the new drive being rebuilt.

Thanks for the response, but my understanding is that when you click on Replace Key in the Unraid GUI it asks for you to enter your email address. So does it know that this license is for usb drive with a GUID of, for example ABC123, and you are using a different drive at the current time. And it won't try to send you a replacement for your other license that was for a USB drive, say with GUID XYZ789? Therefore it knows that the replacement is for that particular drive, as opposed to any other licenses that you may have that are tied to that email account.