So I just moved over from Open Media Vault, I transferred all my data over to other disks in the array, so I could take my 3TB HD and make it the Parity Drive.

 

I am doing the preclear on the drive (preclear script and accompanying plugin).

 

I am about 18 hours in and the web gui crashed. All of my dockers are still active and from what I can tell from HD activity, the preclear is still going.

 

What do I do at this point? Is there a way to restart the web gui? I found a few posts about killing a restarting emhttp, but have also read that this does not work in current versions and that a restart is necessary? Is there a way to see the progess of the preclear via terminal? If I have to restart, I would much rather wait until the preclear is done. Any help would be greatly appreciated.

How much RAM?

4gb. It looked like it was only using about 30% when it crashed.

 

I was playing around setting up OpenVPN docker and I when to stop the docker and that is when it crashed.

 

What is the proper restart method once the preclear that is still going done?

Before you reboot, be sure to type the command  diagnostics    on the command line.  That will write the diagnostics file to the  logs    folder on your Flash Drive.  That will assure that you have the logs from when the event occurred.

 

A few releases back there was an issue with the emhttp process getting dumped from memory when the OS ran out of memory.  I can't  remember quite how that issue was addressed.  (Remember that unRAID works without virtual memory...)  Preclear does use a fair amount of RAM when it runs and perhaps that with your docker work on OpenVPN was enough to cause that to happen.

 

You might want to think about installing some additional RAM to get you to 8GB. 

Awesome. Thanks for the insight. I do plan on maxing my ram out (16GB). There looks to be some options in the bios for ECC, so I need to see if my mobo does infact support ECC before my RAM purchase. I think my processor (AMD Phenom II X3) supports unbuffered unregistered ECC.

You didn't by chance install a webUI or a OS update while the preclear was going on (or run the New Permissions tools), or attempt to stop the array?  Those 4 items will all issue a "sync" command which is going to hang the system because preclear is still in progress.  If that's the case, after the preclear is finished, the system will respond

What I did was installed OpenVPN and started setting it up, but had to go to work before I had everything the way I wanted, so I stopped the OpenVPN Docker. When I did this, the webUI stopped responding immediately.

On 18/08/2016 at 4:59 AM, adamfritzsche said:

What I did was installed OpenVPN and started setting it up, but had to go to work before I had everything the way I wanted, so I stopped the OpenVPN Docker. When I did this, the webUI stopped responding immediately.

 

I've just run into this exact same problem.

 

I was changing some network settings in the Linuxserver group OpenVPN-AS docker and the WebUI stopped responding, as did SSHD, and pings went unanswered.

 

I rebooted, no change, still unresponsive over the network, but wold respond to local keyboard inputs, IE I could login at the local console.

I rebooted into safe mode, no change.

I removed "bonding" from the network.cfg, not sure why it was on. I've never changed it.

Then restarted in GUI mode, opened the GUI locally and everything came up. I quickly changed the OpenVPN docker off auto-start.

 

Now I started OpenVPN docker and it happened again, but as it was not set to auto start now I could just reboot.

I tried again. and the same thing.

I deleted the docker container and it's image, re-installed it and it happened again.

 

Any ideas? I'm not sure if it's a network issue, I suspect it is, as the machine responds locally. But I deleted the docker and it happened again on reinstall, and isn't the whole point of docker that what happens in the docker stays in the docker? So it shouldn't be able to change network settings for the unRAID server itself?

 

How do I tell if the docker image is getting full or if there is some other problem, like running out of memory that might be causing the problem. The docker image is 10GB, and if I look at the bottom left of the Dashboard page it says it is 36% and my memory is about 25% of 8GB.