• Posts

  • Joined

  • Last visited

  • Days Won


danioj last won the day on November 22 2020

danioj had the most liked content!

About danioj

  • Birthday 07/25/1980


  • Member Title
    Advanced Member


  • Gender
  • URL
  • Location
    Melbourne, Australia
  • Personal Text
    Your arrogance blinds you, Master Yoda ...

Recent Profile Visitors

4862 profile views

danioj's Achievements

Community Regular

Community Regular (8/14)



  1. 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.
  2. 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.
  3. 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.
  4. 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!
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. .... 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.
  11. I just wanted to say thank you for forking and maintaining this app. I much prefer this to the options offered by unraid.
  12. 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.
  13. 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.
  14. 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.
  15. 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.