geo10

I have tested this with Ubuntu 19, but after I started a VM on it a couple of minutes it crashed again, and sadly Ubuntu systemlogs are not persistent after a crash (?????) so I have no log files again. Since it didn't crash with Windows I think this is still software related. I'm firing up Windows Hyper-V VM right now to check whether it crashes or not.. Any input is appreciated.

Okay so I have set up the syslog server + mirroring the logs to the flash. Both of them including the crash: the syslog server one crashed at about 15:30, thats why you see it restarted the server there... No log entries really before that so I think this won't help too much. I will also inlcude the logs from the flash, but they are roughly the same with, just additional logs before that. It also shows that after 14:55 log entries werent created... But the server only crashed at about 15:30... I hope you guys can find anything in there. syslog-192.168.0.152.log syslog

I see. So then, I have included the syslog before the crash in my comment above. Do you have any insights what might be the cause?

I just started the server and fired up a windows VM, I enabled syslogs mirroring to the flash but it doesn't contain anything useful I think (also enabled local syslog server but that failed to even create a file...). When I get back home I will try to setup remote syslogs server. Meanwhile, here is the attached syslog file: syslog

Hey, Thanks for coming back! Sorry, I didnt directly say whether I am overclocking or not: I am running xeon cpus, so I am not overclocking nor have intention to. In my first post I have indicated I ran memtest to 10 passes, but since I am running ecc ram I would be suprised if anything popped out there. Let me attach the system diagnostics file. I have also enabled syslog server and if it crashes next time I will come back with the logs. Thanks tower-diagnostics-20191130-0852.zip

Hey, Thanks for contributing to this. I will link the diagnostics file tomorrow. I will also enable the syslog server tomorrow when I have time to get a look. Here is what I have tried: Tried 6.6.7 - Same error after 2 hours or something. Tried 6.8 rc7 - Same error after 1 and a half hours or so. I tried it with Windows 10 hosting a VM in virtualbox, that one didn't crash for more than 3 hours straight, so I suspect this is something to do with the underlying kernel. I have read this thread where the OP fixed his issue with rolling back to 6.2. I wouldn't mind rolling back to 6.2 as long as I get a working copy of Unraid...

Hey, May I get a download link to Unraid 6.2? I have an onging issue with the current release, and I have read on the forum that downgrading to 6.2 helped the person with the same issue. This is the post describing my problem: Thank you, C

I knew this is going to be an edge case and prolly not many ppl face it, but still if someone succesfully solved it I would appreciate some input, so BUMP for awareness. + Additional context: What I have tried since then: I have change the sata mode to IDE: succesfully ran AIDA64 stress test on the vm for half an hour, had to turn it off as it was about to go to sleep. Next day i change the sata mode to AHCI and disabled aggressive energy management in the BIOS, the AIDA64 test ran for 40 minutes then the host crashed with the usual error message. I, then unplugged the HDD and SSD and put the into a SATA2 slot on the mobo, the test ran for 1 hour and 10 minutes then crashed with the usual error. So, I have changed back the sata mode to IDE with the HDD and SSD staying in the SATA2 slots on the mobo and the test is running now for 37 minutes. Also the timing on the VM is strange as the second timer in AIDA64 does sometime skip a second or update it too fast or too slow, so its odd at best. Any gurus out there please drop me a clue.

Hi guys, I am having problems with setting up unraid windows 10 vms. Info about the system: mobo: supermicro x9dri-ln4f+ cpus: e5 2690 (v1) whenever I fire up the windows vm and start to tinker with it i get an error saying: Kernel panic not syncing timeout not all cpus entered broadcast exception handler. What I have tried I have did some digging and tried to start unraid with kernel option max_cstate=1, this didnt help. I have set energy saving mode of the cpu to max performance Ran memtest86 for a couple of passes ran to 10 passes stopped it there. I have read this might be because of a kernel bug... Any input is appreciated, I would love to use unraid as it has a very comfy ecosystem built around. Thanks, geo10 EDIT: for context the system halts with this error after the windows vm is started with varied time until system failure (5mins to 20 mins) EDIT2#: I have also flashed the newest bios on the board but that didn't help. Running unraid without the vm running doesn't produce the error so I am still hoping its some BIOS\software related issue.