makin Posted July 23, 2021 Share Posted July 23, 2021 Hi everyone, a few days ago my unraid server started to shut itself down unexpectedly. I just noticed that my services were offline and then physically checked on the server and it was off. I enabled syslog on flash which I attached together with the diagnostics file (from after the shutdown unfortunately). Last week I enabled AMD-V on the bios in order to be able to work with VMs. I just had docker containers before. One thing also worth mentioning is that I use different VLANs for the unraid server, dockers and one of the VMs. Not sure whether this can cause such an issue though. From a time perspective, the behaviour occurred in the following timeframe. 18:16 Ethernet plugged out and back in 18:22 Reboot initiated Between 18:23 and 19:54 the system shut down itself. 19:54 it was manually booted up again. As you can see, there is no log entry between the reboot and the second time manually booting it. I am really at my wits end and have no idea what to try / troubleshoot. Thanks a lot in advance! gravity-diagnostics-20210723-2001.zip syslog-2 Quote Link to comment
JorgeB Posted July 23, 2021 Share Posted July 23, 2021 Shutting down by itself, instead of just crashing or locking up, is almost certainly a hardware issue and unlikely there will be something logged about that, start by checking temps and fans, could also be a PSU or board problem. Quote Link to comment
makin Posted July 23, 2021 Author Share Posted July 23, 2021 (edited) Thanks for your reply. Any known bugs regarding AMD-V being enabled? I remember some issues with C-States but I guess a kernel panic would’ve been logged? And do you think the NIC can cause issues of that kind? Or could my latest Ubuntu VM cause something like that? One thing worth mentioning regarding the network stuff: The reason why I plugged the network cable out and in again was the fact that the unraid server as well as my home assistant VM (same VLAN) were not reachable while the other VM (different VLAN) was still reachable. After plugging the cable out and in again, everything was reachable again. The hardware itself hasn’t changed since the server was put together. Edited July 23, 2021 by makin Typos Quote Link to comment
JorgeB Posted July 24, 2021 Share Posted July 24, 2021 On 7/23/2021 at 7:25 PM, makin said: Any known bugs regarding AMD-V being enabled? Not that I know of. On 7/23/2021 at 7:25 PM, makin said: And do you think the NIC can cause issues of that kind? Unlikely. Quote Link to comment
makin Posted July 24, 2021 Author Share Posted July 24, 2021 It happened again a few hours ago. I will track temperature and see whether this might be a potential issue. syslog-3 Quote Link to comment
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.