Hi,

 

I'm new to unRAID having built a new server in December and getting it all setup, I initially ran the 6.4 RCs starting at RC14 and then RC18, RC20, before finally upgrading to 6.4 official.

 

I had some lockups in the RCs but ignored them as it was still RC and I'd been tinkering with things. Today I came home from work and found that my unRAID server is once again unresponsive, doesn't respond to pings and the WebGUI is down. The cursor is flashing on the monitor but the keyboard that was plugged in to it doesn't work and num lock wouldn't respond (usually a sure sign of a lockup!). Server uptime had been over 10 days, and when I'd upgraded from RC20 to 6.4 official my uptime had been over 10 days.

 

Obviously after a hard lock restart the logs aren't very useful, but I've included them anyway. I've kicked off a 'tail -f /var/log/syslog'. Am I likely to have any issues running this for potentially running an extended time?

 

Thanks

 

Hardware specs are as follows:

CPU - Intel i7-8700K

Motherboard - ASRock Z370 Taichi (BIOS 1.30)

RAM - Corsair Vengeance LPX 16GB (2x8GB) DDR4 PC4-21300C16

PSU - Seasonic P Series 760w

Cache SSDs - 2x Samsung 500GB 850 EVO

Parity HDD - WD Red 6TB

Array HDDs - 3x WD Red 3TB

Other SSDs (Unassigned) - SanDisk SDSSDA120G & SanDisk SDSSDHP128G (used for VMs)

aventine-diagnostics-20180126-1749.zip

Hi,

 

As an update I had a Call Trace yesterday, looking at the SysLog I can see the log data but nothing stands out...

 

Any ideas?

aventine-diagnostics-20180201-0707.zip

Are you using custom docker IPs, I seem to remember a few other users having call traces/crashes with that.

I do have PiHole with a separate IP address, this is the first call traces I’ve had since an early 6.4 RC so not sure why it would appear now

This is thread I saw call traces because of docker IP assignments:

 

 

Thanks for that, maybe I'll try setting PiHole Docker back to the unRAID Server IP, I know when I first set it up I had issues with it complaining about DNS port already in use which is something to do with VMs?

6 hours ago, PR. said:

Thanks for that, maybe I'll try setting PiHole Docker back to the unRAID Server IP, I know when I first set it up I had issues with it complaining about DNS port already in use which is something to do with VMs?

When you wrote, "DNS port" did you mean web gui port for docker? If so, then it may be complaining about deployed host ports, and the fact that it's already in use. Which case you can click on, "show deplyed host ports ..." (near the bottom); look at everything your box is using; next go to conflicting Host port field and change it to a number your box isn't using.

If you're changing a port that is used for a web gui then you'll also want to edit the webUI field.

 

An example might be 8080, change it to 8081 (assuming it's not already in use)

 

Your port issue won't be related to VMs; however it's plausible running the VMs could tax system such to perhaps lock up. As a diagnostic, you could run your unRAID box with all VMs down, for a period of time, normal to experienced lockups. If you lockup, you know the issue isn't part of the VM stuff, but if unRAID remains stable with your VMs down, that might be an area to look around: IE hardware conflict, bad hardware, driver issue, etc.

 

And I'm assuming you've run memtest for a pass or three just to be sure memory is ok? (Then again you had that 10 day streak; but never hurts to double check)

Also probably start with the advice from the guy with 10K posts, I just always look at things from general techsupport angles.

 

I hope that helps.

Edited February 2, 20188 yr by Jcloud