betaman Posted September 17, 2024 Posted September 17, 2024 (edited) My array is set to not autostart. Upon a reboot, the array will no longer start and the GUI is stuck. I also can't access the log (before or after) the attempted array start (regular and maintenance mode). I also can't post a diagnostics report as the system just hangs. The system will shutdown. Should I pull the flash to try and review the log? Looking for some troubleshooting guidance. Thanks. Note: I'm using 6.12.13 Edited September 17, 2024 by betaman Quote
betaman Posted September 17, 2024 Author Posted September 17, 2024 (edited) So I think the issue had to do with Unraid.net? Seems my system got logged out and by logging in I was able to manage my server from the connect.myunraid.net website? Does that make sense? It's like my webgui wasn't really connected to the server so the commands weren't doing nothing (except shutdown worked?). Array is running now. EDIT: Upon further investigation, my local webui is not functioning and I can only execute commands via Server Management on the https://connect.myunraid.net/ site? Edited September 17, 2024 by betaman Quote
JorgeB Posted September 17, 2024 Posted September 17, 2024 42 minutes ago, betaman said: my local webui is not functioning What do you see in the local GUI? Post a screenshot, also the diagnostics. Quote
betaman Posted September 17, 2024 Author Posted September 17, 2024 (edited) 1 hour ago, JorgeB said: What do you see in the local GUI? Post a screenshot, also the diagnostics. I can't get a command prompt, see the log file etc. unless I'm using the web version. Pulliing up the log is a blank screen and I'm guessing all commands except reboot and shutdown do nothing as well. I discovered the problem when I couldn't delete a Wireguard tunnel. Here's what the log file looks like through local GUI with Array started (same if it's not started though): As noted, I can't run a diagnostics either unless I use the https://connect.myunraid.net site. tower-diagnostics-20240917-1556.zip Edited September 17, 2024 by betaman Quote
JorgeB Posted September 18, 2024 Posted September 18, 2024 So the problem is the terminal window not working? Quote
betaman Posted September 18, 2024 Author Posted September 18, 2024 3 hours ago, JorgeB said: So the problem is the terminal window not working? That’s just one example. No terminal window, log or commands get executed when I click them from local gui. They only work from the online management gui. Quote
JorgeB Posted September 18, 2024 Posted September 18, 2024 Try booting in safe mode and see if the terminal works, if still not try a different browser. Quote
betaman Posted September 18, 2024 Author Posted September 18, 2024 (edited) 51 minutes ago, JorgeB said: Try booting in safe mode and see if the terminal works, if still not try a different browser. So it seems to be tied to one browser on one WIndows PC on my network. Browser is Chrome and PC is running WIndows 10 22H2. Chrome is logged in with my Google account so settings should be shared across platforms. I have another Win 10 environment (running in a VM on the Unraid server) that is working fine with Chrome. Any thoughts? EDIT: Just checked safari as well from my phone and it's working correctly. Also, the PC was working fine and then stopped all of the sudden (that's why it took me a while to figure out what was going on with my server). Some settings in the browser are managed by group policy but I have no idea what might be affecting this behavior since I can reach the server fine (ie firewall). Edited September 18, 2024 by betaman Quote
JorgeB Posted September 18, 2024 Posted September 18, 2024 10 minutes ago, betaman said: Any thoughts? If it's just that PC you could try uninstalling Chrome, then wipe all the leftover directories, then re-install it, if that doesn't help, you may need to re-install Windows. Quote
betaman Posted September 18, 2024 Author Posted September 18, 2024 31 minutes ago, JorgeB said: If it's just that PC you could try uninstalling Chrome, then wipe all the leftover directories, then re-install it, if that doesn't help, you may need to re-install Windows. Thanks for the help. Restarting the PC (and installing some Windows updates) seems to have fixed it for now. I'll report back if the issue returns or mark as solved. Thanks again. 1 Quote
Recommended Posts
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.