December 3, 201312 yr I dunno. Sometimes it stays up for 2 hours... other times 20 mins. I am running Simplefeatures, and virtualbox. That is about it.... Im going to set up a tail on the log now in case this does not show anything. On this particular reboot, the array was not even started, so virtualbox was not running. syslog.txt
December 3, 201312 yr Author I would still need a fairly easy to configure webserver to take its place. I know lightpd is available, but it is not super easy to configure.
December 3, 201312 yr I would still need a fairly easy to configure webserver to take its place. I know lightpd is available, but it is not super easy to configure. I don't use webserver to configure VBOX I use vboxmange and the command line. If that is your only reason for a webserver you may have to do it from the command line or use lightpd. Another option is to install a webserver on a different computer/VM that will then allow you to use phpvirtualbox. I know it is possible but I've been unable to get it to work myself that is why I've been using the command line to configure my VBOX VMs. I don't want SF installed on unRAID since it causes problems.
December 4, 201312 yr Author Well I removed SF, and it seems to have made it through the night. I took bobs advice, and started the VM from command line. All seems well so far.
December 5, 201312 yr Author I spoke too soon. It was up almost 48 hours, and had rebooted when I woke up this morning. Aside from a faulty driver, the only thing really different is the Virtualbox plugin that I am running. Perhaps the next thing to try would be to stop using the plugin, and install Vbox from the go file like I did in 4.7
December 5, 201312 yr If you haven't already run a memtest over night to see if your memory might be bad. If that passes after at least 9+ hours of testing then try a new power supply. Or at least new to that box but known working power supply anyway. Assuming of course getting rid of all the plugins and VirtualBox doesn't fix it. But if dropping the plugin and VirtualBox fixes the problem I would suspect bad memory as I've been running VBOX on an 8GB N54L with the plugin without problems.
Archived
This topic is now archived and is closed to further replies.