November 25, 20241 yr Hi! I'm having very weird issues with my unraid server, the webgui will not be available to use untill after all vm-s boot which takes about 25 minutes, the server itself starts in about 6 minutes (login prompt in the console) but then i have to wait another 5 for ssh to start working and containers to come up and after that i have to wait for the webui and then i can login into the local console on the machine, the local console asks for the username and then doesnt do anything else for 60 secconds untill i get a login timeout message. I attached diagnostics. tower-diagnostics-20241125-2211.zip
November 25, 20241 yr Author one thing i just noticed is if i somehow get an shell before full boot commands like ls or getfacl dont work as in they dont give any output and stay hanging, changing directory works weirdly enough
November 26, 20241 yr Community Expert Solution Cannot find any proof in your diagnostics, but my educated guess is that your configured name servers are not reachable during UNRAID boot. They are hidden within a VLAN, which is started quite late, so many timeouts may occur. Set the UNRAID DNS Entries to 8.8.8.8 or something other public and reboot. If the delays are gone, you know what is going on. BTW, it is not needed and not wise to use local DNS servers for UNRAID, there are not many ads to be filtered out. More likely is that you block some updates.
November 26, 20241 yr Author Well i do need local dns since im AD joined and some docker containers rely on it, also noticed my routing config changed for some reason thus not making the vlan ive assigned as so called managment the default gateway, but i will try regardless and report back, im guessing on boot it hasent initialized the vlans but it has the route for that network so it tries to use the said route and fails, thanks for the help!
November 26, 20241 yr Community Expert 13 minutes ago, andreas laaniste said: Well i do need local dns since im AD joined and some docker containers rely on it Try it out and if it works, we can find a proper solution I think. Maybe you just need to swap the vlans/main lan assignment in the switch? (eg "untagged=VLAN99", "tagged=VLAN1")
November 26, 20241 yr Author yeah thats what i was thinking since i dont use anything really on vlan 1 so there is no need to have it anymore, i will test in a bit and report back
November 26, 20241 yr Author yeah it was dns, 3 min boot time including vm-s to boot lmao, somehow its always dns💀💀 Thanks for the help!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.