November 30, 20178 yr My server randomly crashed on me. No idea why. With no other choice, I logged in through IPMI and went to shutdown. 5 mintues later and it's still going. I plugged a monitor into the server. I see it ever so slowly attempting to shut down each and every docker. It's been about 20 minutes and it's still going. What'd I do wrong this time?! unraid-diagnostics-20171127-2222 (1).zip Edited November 30, 20178 yr by Living Legend
November 30, 20178 yr Seems strange to me Nov 29 20:28:58 unraid shutdown[11770]: shutting down for system halt Tells me that you tried to shutdown. But this is 2 minutes after you started the array And the system is still booting up because Nov 29 20:31:00 unraid root: Updating templates... Updating info... Done. Nov 29 20:31:09 unraid emhttp: shcmd (94): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 |& logger Nov 29 20:31:28 unraid kernel: BTRFS: device fsid 90f20dec-3f5c-408e-ace3-72638333fe1c devid 1 transid 1663 /dev/loop1 Nov 29 20:31:28 unraid kernel: BTRFS info (device loop1): disk space caching is enabled Nov 29 20:31:28 unraid kernel: BTRFS info (device loop1): has skinny extents Nov 29 20:31:29 unraid kernel: BTRFS info (device loop1): new size for /dev/loop1 is 1073741824 Nov 29 20:31:29 unraid root: Resize '/etc/libvirt' of 'max' Nov 29 20:31:30 unraid emhttp: shcmd (98): /etc/rc.d/rc.libvirt start |& logger Nov 29 20:31:30 unraid root: Starting virtlockd... Nov 29 20:31:31 unraid root: Starting virtlogd... Nov 29 20:31:33 unraid root: Starting libvirtd... And its also doing a parity check at the same time.
November 30, 20178 yr Author Let me elaborate on full story. I noticed one of my VMs had crashed. I tried to log into the Web UI. No good. I tried the console. No good. I did IPMI reset. unRAID resets and I'm brought back to the Web UI. I start the array. Everything seems super sluggish and I can't figure out why the Web UI isn't reloading. I try to SSH in after a few minutes. I'm getting nothing. Nothing on the Web UI either. This time I go for a full shutdown. Computer isn't shutting down. After a few minutes I plug monitor in to see that all of the dockers are slowly being stopped. Finally, computer shutdown. Now I've reboot and seem to be okay, but still attempting to decipher why the initial hiccup took place.
November 30, 20178 yr 7 hours ago, Living Legend said: mcelog isn't installed, so no way of telling what happened. Install mcelog via NerdPack then rerun the tests in FCP and more details should be forthcoming
December 1, 20178 yr Author 14 hours ago, Squid said: mcelog isn't installed, so no way of telling what happened. Install mcelog via NerdPack then rerun the tests in FCP and more details should be forthcoming I did so and saw some memory issues. Took all the sticks out, blew some clean air in the slots and all is good
Archived
This topic is now archived and is closed to further replies.