Hello,

 

I'm currently experiencing an issue with my virtual machines. It seems that whenever I have a VM that has 4 out of the available 8 cores (using a 4 core with hyperthreading CPU), it seems to react oddly.

 

At first, it was simply that for some strange reason, the Windows Server 2008 R2 VM would crash Minecraft server of all things, at a very specific time of the day, 3:40AM to 3:50AM. I originally thought it was simply the VM, so I erased it and decided to install Linux Mint to run Minecraft and other game servers. Well, that didn't end up working, same crashing at the same time, plus the VM would pause during the night. Not shutdown, pause on its own.

 

It was strange, because I have another VM that runs Linux Mint, using 2 cores and 2 GB of RAM, and that never crashes, is always up (( it's running Unify NVR software, no cameras yet ))

 

I switched back to a Windows Server Based OS for my primary game server hosting VM, but same issue, using Windows Server 2012 R2. Minecraft crashes at the same time, and the VM pauses at night. It's getting annoying.

 

My unRAID server specs:

Intel Xeon E3 1245-V5 (Skylake based Xeon Processor)

16GB Kingston ECC Unbuffered RAM (2 8gb sticks)

Asus P10S-WS Motherboard, running the C232 chipset

2 3TB Western Digital RED NAS Hard Drive (Main storage drives)

2 250GB Samsung 850 EVO SSDs (Cache drives)

 

Any other questions you may have, ask away, I'm really frustrated at this. It used to work flawlessly, and now I'm sure it has to do with UNRAID, because the issue persists through Linux and Windows, at the same time frame...

Something with mover then? What time does it run? 

Something with mover then? What time does it run?

 

Where do I find the setting for the Mover? I haven't touched that yet x:

Something with mover then? What time does it run?

 

Okay, never mind. Found it, it starts at the specified time, 3:40AM

After the next freeze (or change the schedule to have mover run now and let it freeze) post your diagnostics (tools - diagnostics)

After the next freeze (or change the schedule to have mover run now and let it freeze) post your diagnostics (tools - diagnostics)

 

So I just thought of this now, while I was invoking the mover.

 

My Windows Server is Cache only, so it uses just the cache drive, while the other VM uses the normal Hard Drives. Does the Mover only affect the Cache Drives? (( Minecraft by the way, is crashing as I type this, so it is the Mover's fault... ))

After the next freeze (or change the schedule to have mover run now and let it freeze) post your diagnostics (tools - diagnostics)

 

So I just thought of this now, while I was invoking the mover.

 

My Windows Server is Cache only, so it uses just the cache drive, while the other VM uses the normal Hard Drives. Does the Mover only affect the Cache Drives? (( Minecraft by the way, is crashing as I type this, so it is the Mover's fault... ))

Mover only touches shares that are either use cache yes or use cache prefer

Here's the diagnostics after the crashing.

 

I'm thinking of moving the entire VM from a SSDVM share I created to just simply the hard drives, I loved having it on the SSD cache for booting times, but the mover is causing issues. Oh well, long as it doesn't crash anymore, I'm fine with it being in the Hard Drive. Thanks for all your help, but please do look at the diagnostics.

xylerserver-diagnostics-20161218-0941.zip

Looks like the cache drive is full

 

 

Dec 18 04:04:09 XylerServer root: rsync: write failed on "/mnt/cache/domains/MichiSecurity/vdisk2.img": No space left on device (28)

 

domains is set to be cache: prefer

 

Also, you've got docker enabled (with a size of 100G which is major overkill), but there's no path to the image location so docker is non-functional, and throwing a ton of errors in the syslog.  Either give it a path to the image location, or disable the docker service if you're not using it.

I disabled the Docker setting, don't know how to use it yet, so I don't really need it. I also set the docker folder to 20GB

 

The SSD Cache drives are for some reason only having 1.07GB left. I'm moving the 200GB VM allocation for the Games Server hosting VM to the Domains Share, then seeing if that goes down. Also gonna change that to not prefer using the cache.

 

Should solve a few issues right?

Ugh, okay.

 

MichiSecurity was causing issues being on the SSD cache also due to the Domain folder. It was for some reason, taking up 210GB even though it only had Linux Mint on it with others, and I specified it to use the Hard Drives only, but it saved in SSD also.

So, I moved the Windows Server VM over to domain, took off use SSD cache prefered, and deleted the other VM. This time, I hope everything sorts itself out.

 

Thank you so much for your help