FEENX

Solved. It was XMP. Not sure why, but it was. Zero crashes since turning it off and I've done everything, sometimes all at once, with my unRAID server now. Docker, VM, stress tests, days running, etc. Thanks for the help, hopefully someone else will save the time and try XMP first.

So I'm about a week out of being able to afford a new PSU so I started just trying to see if I could replicate the crashes and then see if any one component was related, again at least. Started with one stick of RAM, and was running both Geekbench5 and Prime95 stress tests before moving on. Got up to 4, and was running super stable; completing each test just fine. Full clean shutdowns, and restarts. And then I went into the BIOS... and did what I've done for years. Enabled XMP. Instantly can't complete a single test to save my life. As I write this it's running just fine after finishing Geekbench5 with all 32 GBs of RAM but XMP disabled. Will keep working to verify stability but... yeah. I know XMP is technically "overclocking" but I never thought it was an issue, and I've probably had it on for every other crash because it's something I turn on as if it was default.

Well I decided to disconnect all the SATA drives to see if it could be the random drives I have in there. None are particularly new or known good. So far it's running without crashing for almost 18 hours, thinking about plugging in the SSD SATA and try getting the array started with just VM and Dockers running off the SSD with no hard drives or parity going. Well, decided to run Geekbench for Linux and try to make sure the hardware that was running was good and it crashed during. Makes me less sure it was the drives and more sure I need to swap the PSU. Yep, crashes at the Multi-core "Navigation" test every time. Not sure if that means anything.

For sure, I thought similar eerily on. I've been monitoring the CPU temps randomly since the crashing started happening. It'll hover around 21-25 and then when I do benchmarking it spikes into the mid 80s. So very normal imo. Plus the CPU/Cooler are different than when I started

For sure, the one it's using now that's been in there isn't modular and I don't think a cheap new one I get will be either but I appreciate it.

Based on the way it seems to "simmer" over and then come back after cool off, added to the fact the only part I haven't replaced is the power supply. I guess in theory if the power supply is failing, and perhaps something is overheating and then the next time there's a load it crashes. Then crashes again during boot at heavy load times. But then after cooling off it works again seemingly regularly. Not sure if I have another PSU to put it in, if not, I'll have to grab a cheaper one and see. Can buy a proper one if that's the issue for sure.

And there it goes again: Crashes, gets back to GUI ~1 mins later crashes, gets to all the boot up sequence text Crashes, over and over after "loading bzroot..." Just turned it off, can almost guarantee that in ~10 minutes I'll be able to boot it up just fine and it'll run seemingly fine for a few hours. I just can't figure out what would cause this.

Well it's been running since Thursday morning and so only crashed once, and re-booted fine. Not sure what that was, I walked into my office and it was starting up and stayed running the next "1 day 3 hours" now. Can't tell it rebooted multiple times or just once and stuck. Still been running with docker entirely off but VM engine now has Windows and Ubuntu running all the time. So far so good with the new kernel I guess. *knock on wood*

As it usually does, after being off for awhile it was perfectly fine booting up and is now running. I managed to upgrade to the RC as you can see from that screenshot, and rebooted just fine. It's now running with only 1 VM and the NAS features, Docker is off.

Okay. I'm going to try turning it on again soon. It's very odd cause it seems to "get worse" by crashing sooner and sooner in the sequence but then if I turn it off for a while it'll start to work again. As if it's overheating but by checking the BIOS I don't believe the CPU/MB are overheating. If it continues I'll looking at using that version. I see the creator tool can create using it, then I copy over the "/config" folder, correct? Appreciate the help of course!

Yeah just not sure which could be, cause since this starting happening I replaced It's motherboard, cpu, ram, usb drive. Changed from a Asus Z390 with a 9900k to a MSI Z490 with a 10600k. As for RAM I've run memtest for hours without errors, and even tried running with each of the DIMMs separately. Assuming it could be the SATA drives, other than SELF tests or benchmarking via DiskSpeed anything else I could do to check? It doesn't seem to be reproducible by doing filesystem stuff.

Now it's back to crashing during boot over and over. It crashes right as it says its checking "bzimage" or "bzfirmeware" can't tell it's too fast. But it doesn't make it to linux booting even. Only thing left to change out is the power supply, can't imagine it's the PSU tho.

I do have a SSD cache and Docker does run off that. And I will do, I deleted the docker image file so I assuming it'll create a new one when I start it up again. All in it's nice to be able to have stable NAS and VMs though, I run my Plex off a VM so I can use TV Tuners that don't have linux drivers, so this ended up not effecting my media server ha.

Yeah that's what I thought, cause it definitely would crash during the boot up, sometimes immediately after it auto-selected normal boot up. And yet, here I am without a single crash, I'm almost afraid to turn docker on haha.

So, I just happened to try and disable Docker and it stopped happening... completely. Is that even a possible cause?

Hello, I've been dealing with something very strange. I have a machine I've been trying to get unRAID running on in any fashion of stable possible. It crashes seemingly randomly during boot, sometimes it makes it far enough to start the array, other times it crashes as soon as it times out on the boot up selection screen. I haven't been able to narrow it down, it logs nothing when crashing it must be something hardware based. I'm running 4 x 8 GB RAM but I've removed them and inserted each of them alone, and then built back up to all four; nothing tied to any crashes and continued. Also can run memtest64 for days without any logged errors. I used to be on a ASUS WS Z390 Pro motherboard with a 9th generation Intel Core i9-9900k and was logging "machine check events" so I swapped to a MSI Z490 motherboard with a 10th gen Intel Core i7-10600k I haven't seen any machine check events in the log on this motherboard/CPU combination. It has a single PCI card for a TV Tuner, no GPU or anything else. It's running 6 SATA drives, 1 being an SSD. I just swapped USB drives hoping it was a corrupted boot files; but happened in lock step as it always does on the new drive, barely had time to "replace key" my license onto the new one. I gifted the Z390 and 9900k combo to my brother running Windows 11 and it has had zero issues. My next step is to try running Windows live off a USB and see if somehow it's unRAID/Linux only. Not sure why that would make sense, but here I am. P.S. I've attached diagnostics that were auto dump onto the previous drive two days ago, it should contain anything. olympus-diagnostics-20220722-0519.zip

So after running it 24 hours as just the NAS; then I did another 24 hours with my normal docker containers running. No crashes or errors or any kind in the logs. Within 5 minutes of enabling the VM Engine and my Windows 11 virtual machine it crashed with no error logged, just hard restart. I'm going to try having the VM Engine running without any VMs active and see if if I can narrow down the issue some more.

Thanks for helping. Indeed, I recently switched toa WD NVMe cache drive from Samsung 2.5" SATA SSD and started having my cache mnt remounted as root, then I noticed "nvme controller is down, reset" in the logs so I switched back to the 2.5" SATA based SSD. While the NVMe drive was in I was getting `mcpe` hardware errors that the CPU's ECC were correcting, and it was all Level 1 cache errors. It's been up for 12 hours or so since a crash, without the NVMe even installed into the motherboard. No mcpe errors, nor crashes but we'll see. Right now it's running with just the array disks, no cache at all. Update: I should note it often seem to crash when unRAID accessed something off the cache, like mover running or Plex querying the metadata that was on a cached share. Not sure if that matters.

Hello, I currently have an unRAID server that's been crashing at seemingly random intervals. Sometimes it'll be idle for 8 hours, other times it'll crash while starting the array. I wouldn't even notice if the motherboard didn't have an audile click when it reboots. I've attached the diagnostics, although much of this is foreign to me. I've attached the last few days of syslog entries; I have it storing in a share so I don't lose syslog after each crash. olympus-diagnostics-20220702-1810.zip syslog-192.168.86.2.log