danioj

I didn't think so either. I can reproduce it, so will do so and then grab diags.

No, SMB. Enhanced macOS interoperability enabled. No extra configuration.

Good Evening (or whatever it is wherever you are in the world), Before I go through the effort of raising a bug report does anyone know if there is an active / known bug related to shares mounted in Linux and becoming stale following the execution of Mover? In short, I have an unraid share mounted in Proxmox and a Proxmox backup job set to run nightly at 12:01. All initial runs of this job run successfully. However, as soon as Mover runs, the share becomes stale (in that it is not accessible but the mount point is still there but is 'busy') and any subsequent runs of the job fail. My bandaid has been to turn off Cache in the short term but that's not my preference. I can't imagine I am the only one with this problem. I run things pretty Vanilla on the unraid side of things. My Google / Forum Fu seems to have failed me on this one - certainly recently. Any links to an open bug or discussion thread etc would be helpful. Thanks Dan

I just wanted to share my recent upgrade journey and give a big shoutout to the Unraid team, the plugin developers, and this amazing community. I’ve gone from a very dependable but aging setup to a modern powerhouse, and the whole transition was incredibly smooth thanks to how well Unraid handles hardware changes. The driver of the upgrade was aging hardware, noise, high power consumption and heat (worsening issue with high ambient temperatures in Australian summers). My trigger to do this was the sale of my old CPU, Motherboard and RAM for $300 AUD and ability to get new parts for only an extra $150 out of pocket. Old setup CPU: Intel Xeon E3-1241v3 Motherboard: Supermicro X10SL7-F RAM: 32GB DDR3 (ECC) Drives: 12 Drives Notes: This build served me well for years. Stable, reliable, and efficient. OS: 7.1.3 Pro New setup CPU: Intel Core i5-14500 (14th Gen, using iGPU for Plex HW transcoding) using stock cooler Motherboard: Gigabyte Z690 AORUS PRO DDR4 RAM: 64GB DDR4 (Non ECC) GPU: GTX 1050 Ti (currently idle, may repurpose or remove) HBAs: LSI 9300-16i + LSI 9300-8i Drives: 24 Drives NVMe: High-speed SSD in M2A_CPU slot for appdata/cache duties OS: 7.1.4 Pro What specifically went well Booted straight into Unraid USB after the hardware swap — no reactivation or surprises All hardware detected out of the box — including GPU, iGPU, NVMe, and HBAs and sensors Unraid config, Docker containers, and plugins just worked — like nothing changed and no license reactivation needed Parity check ran clean, no hiccups with array or shares Modern Z690 platform support is superb — no driver hacks or kernel tweaks needed Build notes I relocated my LSI 9300-16i to a different PCIe slot after getting sporadic PCIe errors on the PCIEX16_1 gen 5 slot — resolved instantly I did this so I put a GPU there instead Added a silent Noctua Fan to provide I’m using the CPU-attached M.2 slot (M2A_CPU) for best NVMe performance Thermal pad on the M.2 heatsink was pre-installed and perfect — no extra paste needed Cable tie rescue for a minor GPU mounting mishap — works great in a pinch 😅 Fan and temp sensors all reported accurately out of the box Added active cooling for the 16i LSI HBA — the sucker runs hot Special thanks Some of the best parts of my Unraid experience are thanks to the incredible plugin devs who make the product and life easier: bonienl (Dynamix plugins — essential tools and UI improvements) dlandon (great plugins like Unassigned Devices and more) ich777 (for Intel related plugins - essential) Squid (Community Apps plugin — makes installing anything a breeze) SimonFair (for his GPU Statistics addition - excellent) These folks make Unraid more powerful and flexible every day — massive thanks to all of you. Final thoughts This upgrade was honestly fun — and that’s not something you can say about every OS. Unraid’s flexibility and resilience made it easy, and the fact that I can scale up to 22 drives, hardware swap with confidence, and keep all my services running and complete the upgrade in 1 Day!! just proves what a great platform Unraid is. Server now quietly humming along (I can only assume as I cannot hear it) rebuilding a drive @ 210MB/s with drive temps at no higher than 40'C and CPU temp no higher than 35'C. Big thanks again to the Unraid team, the devs, and all the folks here on the forum who write posts I have used in researching etc. You all rock. — Daniel

I run this container. For years I have had it on my unRAID server with an Nvidia card doing HW transcoding as the CPU in the server is an Xeon. Recently I put it on my Proxmox machine passing in the iGPU of the Intel i5. My experience across both is just fine up to very large UHD files across an array of clients not too dissimilar to yours both over 1Gbit Cat6 and 5ghz wireless. So as was suggested above I don't think is the container more your configuration. Assuming your physical networking is fine I wonder if you could be fallen fowl of Plex' bandwidth limiting settings. Essentially if your device is on a different network to the server it could be considered "remote" and therefore be artificially limiting the bandwidth. I fell foul to this when I had Plex communicating with clients across VLANS and I hadn't added the net mask of the Client VLAN to the Plex setting which makes it consider the VLAN to be local instead or remote thus negating the limiting. Just a thought.

Hi All, Just upgraded to the new UniFi-network app with the standalone MongoDB instance. I thought it might be a good time to put my wildcard domain cert on the controller. Honestly, I’ve spent twice as much time looking for a solution to do that than it took me to setup Mongo and migrate to the new UniFi application. There is so much aged content out there on hacks to do this. Also there seems to be a different process dependant on what UniFi device you use. Hopefully one day soon they will integrate cert management into the application itself. Has anyone managed to do this that can explain or can link me to a guide? Thanks D

Nice Plugin, thank you. Dead link on the settings page: Tab Position (see HERE)

Bump. Any forum or web links to some possibly relevant information would be helpful.

Hi All, I have been using the Linuxserver.io swag container for many years now. I use this to generate a wildcard certificate for my custom domain via LetsEncrypt (LE) and it works great. Since Apple have recently amended the Safari autofill feature on IOS to only do so if you are accessing a website via HTTPS it is forcing me to enable this on my LAN services. Basically I use unbound within pfsense to hostoveride access to my app.domain.etc (within my LAN) and take me to the internal IP of my LAN services. Anyway, I digress. I have been able to get this working and install my wildcard certifate for every LAN service except unRAID. That's because what unraid is asking for is slightly different to everyone else. unRAID is asking for a bundle file. Swag only produces these files (I believe it used to create a bundle file but it doesn't seem to anymore): cert.pem chain.pem fullchain.pem privkey.pem README None of these appear to be the bundle file that unRAID is looking for. When I open the file that unRAID has there there are more cert's in there than any single file generated above. My Google Fu seems to suggest that a bundle file is some combination of these files but there is so much LE information out there Im finding it hard to figure it out. It also doesn't help that there so many different names for the same thing, things changing over time and even file names don't seem to be named what they are commonly referred to. So I turn to you good community, can you help me figure out how I generate the bundle file that unRAID is after from the files that LE certbot generates when producing / renewing keys? Thank you! D

Well, I think I will call this thread a wrap. There has been no material change since upgrading to v6.12.4. I obviously jumped the gun and "fixed" the issues myself prior to the unraid "fix" for macvlan issues. All that said, my server is back to its usual rock solid self. All of the other things that were playing me have also gone. Starting fresh really did help and I am glad I did it. I can go back to forgetting that the server is there and just using it when needed.

I know what you’re saying but honestly the reset happened in a matter of seconds ie the timeouts for unmounting / shutting down services that drive an unclean shutdown were not exceeded. I’m not aware of a scenario where services shutdown and drives are unmounted so quickly that still causes a unraid to think a parity check is still required on reboot? Happy to be educated though.

Upgraded without major issue. Not a big deal as I don’t use bonds or bridges anymore and all my dockers are on my secondary network interface and unraid on primary. I moved as things were unstable and now they are I CBF reverting back. Don’t really notice the speed loss due bond. My only gripe is that the upgrade caused a Parity Check. Shutdown wasn’t unclean as I was observing it. Shame, as my scheduled monthly only finished yesterday.

Im now at the beginning of September and things are still rock solid. Re my previous issue, the author of UAD confirmed that there are no components of that plugin installed into the OS by default. He also stated that the UAD error could only occur IF UAD was installed, which it is not. Unresolved but hasn't caused any problems so I have moved on. I see the .4 release of v6.12 has been released. I am going to go for it. I have no wish to give up my stability but it's a personal decision to keep with the stable branch for security fixes and upgrades etc. Tune in next week! LOL!

Welcome. It’s a shame someone didn’t see your OP earlier and save you the journey many of us have already taken. I’ve been asking for the “feature” to start virtualisation services independently of the array for years now. It doesn’t appear to be something LT want to do. The answers from LT has long just been, they can’t.

I can assure you Dan it’s not installed. I did a usb wipe just a couple of weeks ago and a clean install and only installed 5 plugins - UAD was not one of them.

In this version or a previous version(s) was a decision taken to install the third party plugin Unassigned Devices (or components of it) by default? I ask as I got this in the syslog this week: Aug 17 07:02:38 unraid nginx: 2023/08/17 07:02:38 [error] 5368#5368: *1417305 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: X.X.X.X, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "host.local" Note the "/plugins/unassigned.devices/UnassignedDevices.php" bit. I do not have this plugin installed nor have I installed it since installing unraid clean a couple of weeks ago.I had a look in /boot/config/plugins/ and its not there, as I would expect having not installed it.

Another week goes by the the server is still solid as a rock. Only one odd message to speak of in the syslog this week: Aug 17 07:02:38 unraid nginx: 2023/08/17 07:02:38 [error] 5368#5368: *1417305 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: X.X.X.X, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "host.local" Seems to be something to do with Unassigned Devices. The only weird thing there is, I don't have the plugin installed? So a bit of a WTAF there. It didn't seem to impact stability though. Also noticing that by reverting to the new build defaults vs whatever my settings where that had evolved over so many years - my server is drawing less power. I can only imagine it being down to the default spin down settings. Can't remember what I had my old setup was set to.

Almost a week on since my start from scratch "rebuild". I am now so glad I did this. Not a single entry in the log except the nightly trim and backup entries. Outside of that just the smart events as the array spins up and down as it is accessed throughout the day. 1 user driven restart mid week following installation of the latest Nvidia driver. Solid as a rock.

.... my journey to unraid stability! I am a long time user of unraid. Since v5 actually. I have always purchased half decent server hardware (drives aside) and my use case for the os has never been that far outside the box. For my main server, I have always followed the recommended upgrade pathway without a need to rebuild (sans a usb failure which was an easy restore from backup). In recent times, I have been having stability issues. For a number of reasons. I used bonded dual nic's, vlans, macvlan, btrfs errors, host access, many plugins and of course whatever was left over from my years of tinkering and learning as I upgraded. Here is what I have done to try and regain stability. - started fresh - maintained parity and drive assignments - redesigned my network configuration and switched from bonded dual nics to a single (non bridged) eht1 for unraid and a single (non bridged) eht2 for docker (4 vlans including the vlan for the same network unraid is on so I don't use br0 for eth1) - as a result of above, switched to ipvlan from macvlan - uploaded (via the file manger plugin) docker templates from my old usb backup and reinstalled docker containers - switched docker image to xfs - assigned dockers to the network I wanted and started them - sorted out my shares (which had been auto discovered) as their config was not there - created users again - installed only "what I need" plugins (9 from 21) - disabled VM service (don't use them) - checked parity Now I am on my way. Everything is working as I need it to. 29 hours down and not a single event in the log to bat an eye lid over. Server is as idle as I have seen it for a long time. No network issues. gui is snappy. Just the drives spinning up and down. A nice clean fresh install. I have this feeling that this is going to work and it only took me 90 minutes (tops) to go from where I was to where I am now. I intend on checking in to this post regularly (ie monthly) with my stability notes and uptime.

I just wanted to say thank you for forking and maintaining this app. I much prefer this to the options offered by unraid.

Your post made me check my instance and the result was the same as yours. Swag not working. I don’t run anything fancy with mine, just host a basic text landing page. Anyway, immediately disabled my port forwarding and firewall rules while I investigated. Turns out, my custom network “proxynet” (we must have followed the same guide) has disappeared. Now, like you, I have had a docker config issue in the last few weeks which caused me to delete and recreate my docker image and subsequently reinstall on my containers. Figured all would be ok as config was intact. All I can think of is that this process has resulted in that custom network (done via command line if I remember) did not survive the docker image getting recreated. I’m pretty sure that once I recreate the custom proxynet network again and re-enable the port forwarding and firewall rules I’ll be back up and running. Will try that tomorrow and report back.

DNS issue? Try pinging an external IP address you know will give a response. If you get a response I’d say it’s DNS.

I’m getting a little frustrated with the company and community conversation regarding the macvlan issues. I see so many posts where users are taken through the same set of questions as others, post your logs, switch to ipvlan (when things don’t work for the user as they did with macvlan), why do you need this, try that etc etc. This seems like a waste of time and or a diversionary tactic as either the outcome ends up being the same or the answers from those providing advice imply they know the issue. Therefore why keep repeating. I run docker containers, all through a dedicated interface seperate to the main unraid interface, many with their own ip address on various vlans on my network. I have all unifi networking equipment except pfsense as my edge device. Host access to guest networks enabled. I get hit by kernel panics very regularly. Switching to ipvlan does not deliver the same outcome as macvlan in my case so is therefore not the answer. I’d really like a comprehensive explanation as to what can be expected to be achieved and what can not with either macvlan and or ipvlan. An honest warts and all answer would be nice as I can see my use case (which is my own) is not unique. My ask: Create a honest comprehensive post containing the issue and current explanation, what can be expected to be achieved from each option and don’t leave anything you know (ie even that which relates to why you might consider the “edge” use cases) out, even add what you “think” might be happening or the answer and then make the post a sticky. When a support request gets asked that fits the issue, link to it. Let people discuss it in that thread. Provide updates on progress of a fix or accept limitations of the product. Please.

A very uneventful release for me as none of the new features are going to change how I use unRAID. That being said, upgrade was just as uneventful, which is always excellent. No issues so far here.

Registered my option as “other”. Ability to start virtualisation services (Docker and KVM) irrespective of array status.