41 minutes ago, bcjenkins said:

I went 30 days without a crash running on RC9, updated to 10,

 

Did you see this:

 

 

3 hours ago, johnnie.black said:

 

Did you see this:

 

 

I don’t use Ryzen. This is an Intel i7 

4 minutes ago, bcjenkins said:

I don’t use Ryzen. This is an Intel i7 

 

Sorry, don't know how I got the idea you were using Ryzen, probably thread mix up.

i have these hard crashes too. A week ago i came home to find my server unresponsive. after reboot my system wouldn't boot up in unraid.

i inserted my USB boot drive into a windows machine and got the 'you need to check this volume' so i did

after this i made the drive bootable again and iserted it in my server

server booted up and i got into the WEBGUI. started the array and started the parity check

all well and all until 2 days later. same happend out of the blue. no warning no nothing. just a hard lockup

after going through the same procedure as before i got into the system yet again. making this photo.

Now again my system is unresponcive and wont even boot.

maybe it has something to do with my hardware. will have to wait till next week.

On 11/4/2017 at 6:47 AM, bcjenkins said:

Earlier in the beta I had been running bridge mode on all of Dockers and would crash constantly. I have disabled this mode again and will advise if another crash occurs.

 

Very curious to see if the network mode for docker containers is having an affect on system stability!

On 11/5/2017 at 11:10 PM, BBoYTuRBo said:

 

Very curious to see if the network mode for docker containers is having an affect on system stability!

 

I was on the previous GA release, I believe it was 6.3.5 and was very stable. This is a server that has been stable for years. I wanted to get rid of pipework and move to the more native way of giving a docker container a dedicated IP. I have been hard crashing every few days. Is pipework compatible with the 6.4.0_rc10b version? I am considering going back to pipework just to see if I can regain stability.

 

thank you

 

10 hours ago, NOX6 said:

 

I was on the previous GA release, I believe it was 6.3.5 and was very stable. This is a server that has been stable for years. I wanted to get rid of pipework and move to the more native way of giving a docker container a dedicated IP. I have been hard crashing every few days. Is pipework compatible with the 6.4.0_rc10b version? I am considering going back to pipework just to see if I can regain stability.

 

thank you

 

 

Using version 6.4.0-rc10 and all my docker containers use macvlan (custom) networks without a problem.

 

Can you post your diagnostics after a crash happens.

 

2 hours ago, bonienl said:

 

Using version 6.4.0-rc10 and all my docker containers use macvlan (custom) networks without a problem.

 

Can you post your diagnostics after a crash happens.

 

 

The server was not responsive on the console. It is back up, usual docker containers started and it is doing a parity check. The one virtual machine is also back up.  The last hard crash was Monday around 8pm, this one was overnight Tuesday/Wednesday.

 

If it is the macvlan then I'm considering just not using it for the time being. The intent of separate IPs for each docker container was just so that it made it easier to track traffic in the firewall.

 

thank you

 

srv-tower-02-diagnostics-20171108-0641.zip

The server just crashed again after about an hour. It was doing a parity check from the overnight crash. I brought it back up and will leave all docker containers and the virtual machine stopped. I was to try to get a successful parity check before starting them back up.

 

Just now, NOX6 said:

The server just crashed again after about an hour. It was doing a parity check from the overnight crash. I brought it back up and will leave all docker containers and the virtual machine stopped. I was to try to get a successful parity check before starting them back up.

 

 

There was nothing on the console for this crash, just the login prompt from before as I had left it.

You should log in and tail the syslog as per the instructions in the first post of this thread. In my case, I was locking up with bridge mode enabled for a docker. I have disabled it and haven't crashed since.

i downgraded to unraid 6.3.1. and then i couldn't even boot.

turned out i had faulty memory.

now with the memory stick removed im running ok

so far the system is responsive and i have been running it for 1 day now.

not sure is the hard crashes are memory related.

i will post my diagnostics here too. maybe someone can find something that is useful

tower-diagnostics-20171108-1249.zip

tower-syslog-20171108-1244.zip

8 hours ago, bcjenkins said:

You should log in and tail the syslog as per the instructions in the first post of this thread. In my case, I was locking up with bridge mode enabled for a docker. I have disabled it and haven't crashed since.

 

I have removed all of the dedicated IPs from my docker containers. They are now all back on Network Type: Host.  The parity check from the hard crash this morning is at 85%. I am hoping that this makes the server stable again. Thanks to all.

I reverted back to rc9f, but did keep the last 2 diagnostics that I ran after each clean boot. This zips also include the log tail. My server is a Ryzen system just so you know, hope this can help. As a note, I do keep a monitor, keyboard, and mouse attached to my server, and when it hard locked, it showed the login screen as usual, but was not able to do so.

crash1.zip

crash2.zip

On 11/4/2017 at 5:47 AM, bcjenkins said:

I went 30 days without a crash running on RC9, updated to 10, waited a few days and then turned on bridging for one of my dockers (plex) instead of host mode. It ran for about a day, then crashed shortly after applying an update to the docker this morning. Earlier in the beta I had been running bridge mode on all of Dockers and would crash constantly. I have disabled this mode again and will advise if another crash occurs. 

 

I hope this helps. 

 

 

 

 

Hi and thank you for providing us with this detail.  We do not know the exact cause of the issue yet and it may be related to either Docker itself or the Linux kernel, but either way, we will continue to monitor this issue and let you know what we find.

update on the crash issue

after installing new memory and staying on version 6.3.1 my system runs like a well oiled machine

very responcive and fast.

no issues whatsoever.

i think in my case it was memory related.

next step is upgrading hardware

just bought a dell H310 controller with cables and a new WD red 4TB to replace my parity drive

if that upgrade is running fine i will upgrade the OS to the latest version.

 

again, so far the systems runs fine again

On 2017-09-26 at 11:35 AM, dkerlee said:

How about installing "Nerd Tools" plugin which has Screen. Starting a screen session with

tail /var/log/syslog > /mnt/disk1/syslog.txt

detaching from the Screen and plodding along like normal? If/when it hard crashes again, the file would be available after the boot on /mnt/disk1/syslog.txt?

 

Getting a hard crash every ~24 hours since doing a "fresh" rc20 install. I did this, and foolishly copy-pasted and so forgot the -f flag....d'oh! Oh well, I'll have to wait another day to see the cause.