November 21, 20241 yr I'm a new Unraid user as of last month and only recently installed a VM a few days ago. I'm currently using Unraid Version 6.12.13 and I have a Windows 11 VM which I torrent on, so I am constantly leaving it running. I have allocated 2 cores, 4gb RAM, and 200GB of disk space from my cache drive to this VM and it had been working fine until yesterday. I got home from work, and it was working fine so I locked my home computer and worked for a few hours on a microwave install. Upon coming back and checking on the VM, I noticed that I couldn't connect through VNC and that I couldn't even connect to it through browser to check if the VM was running still. I ended up shutting down the server and rebooting it but that didn't fix the problem. I had to boot into BIOS and boot into the boot flash drive manually. After doing this I was able to access the server but had to restart the array and do a mandatory parity check. I then started my Plex docker app and my VM and gave it some time to work. VM seemed to be working fine at first, but the moment I opened up Firefox browser, the whole server crashed again and the screen displaying from it showed my motherboard manufacturer's splash screen with no other pop-ups to boot into BIOS or otherwise. Server was again inaccessible after this. Is this a known issue with Firefox or completely unrelated? Other apps in the VM seem to be working fine, haven't tried any other browsers, but my torrenting app and VPN seem to be working regularly. Currently sitting at work after last night powering the system down and rebooting through BIOS; server is currently going through parity check.
November 21, 20241 yr Community Expert If the server is rebooting by itself that is almost always a hardware issue, but you can enable the syslog server and post that after a crash together with the diagnostics, in case there's something visible there.
November 21, 20241 yr Author 32 minutes ago, JorgeB said: If the server is rebooting by itself that is almost always a hardware issue, but you can enable the syslog server and post that after a crash together with the diagnostics, in case there's something visible there. I attached both of what you mentioned. The server was not rebooting by itself. I had the VM running for over a day at the point where everything stopped working. Everything was still on as well inside of the server, no motherboard lights or anything of the sort. And like I said the VM would only fail and shutdown the server whenever I opened a browser and attempted to make a search. Other apps inside of the VM working fine. VM is off now and Plex docker is currently running as it should be. Only issue is the VM homenas-diagnostics-20241121-1024.zip Syslog.txt
November 21, 20241 yr Community Expert 30 minutes ago, dfdonea said: The server was not rebooting by itself. That's what I understood, based on this: 2 hours ago, dfdonea said: the whole server crashed again and the screen displaying from it showed my motherboard manufacturer's splash screen Syslog is empty.
November 21, 20241 yr Author 3 minutes ago, JorgeB said: That's what I understood, based on this: Syslog is empty. It was my understanding that when you said reboot the server was back up and running again. It was essentially a shutdown though, as it did not come back online. Sorry for misunderstanding, still new to this. I didn't think it was a hardware issue because this only happened whenever I did something specific in a VM syslog1.txt
November 21, 20241 yr Community Expert Server showing the board logo suggests it reboot by itself, and not seeing anything relevant in the syslog, try creating a new VM, if it fdoes the same there you can rule out an issue with the current one, but I'm still suspecting hardware.
November 21, 20241 yr Author 2 minutes ago, JorgeB said: Server showing the board logo suggests it reboot by itself, and not seeing anything relevant in the syslog, try creating a new VM, if it fdoes the same there you can rule out an issue with the current one, but I'm still suspecting hardware. Currently remoting into my home system to check on it. VM is running now but reluctant to open browser. I might try Edge instead of Firefox first then a new VM later tonight if that still reboots. If it isn't the VM, then what hardware is typically the cause of the issue in this circumstance?
November 21, 20241 yr Community Expert Server rebooting by itself is usually in no particular order PSU, board, CPU or RAM.
November 21, 20241 yr Author 29 minutes ago, JorgeB said: Server rebooting by itself is usually in no particular order PSU, board, CPU or RAM. Got it. Started VM and seems to be working fine now; didn't launch Firefox but I will look into it again if it crashes. Thanks for your 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.