Any 6.11 version I have tried to update to has resulted in the same strange crashes happening within a couple minutes of the array being started. Downgrading to 6.10.3 completely fixes this error
I am currently running the system without starting the array to confirm it only happens when it is started, I'll update here if that changes. I've also attached my system diagnostics. I'm not entirely sure where I can get a log file in unraid so if that would help please let me know where to look

 

The usual sequence of events is as follows.

Unraid starts

Array starts
Everything appears normal, low cpu usage, docker containers all start as expected. everything is accessible where it should be accessible.

Crash, no warning, no error printed to the screen

press the power button again, lights come on, fan spins up. nothing else happens. No video out whatsoever, and no response to ping

force off the system. press the power, back to step 1

 

Any help at all would be appreciated

 

Edit: It's worth noting that this remains the same when docker and VMs are both disabled

jackdaw-diagnostics-20221126-1404.zip

Edited November 26, 20223 yr by RoryIsNotACabbage

If there's nothing on screen probably it won't help but you can still try to enable the syslog server to see if it catches something.

 

Also make sure that you are using the correct power supply idle control setting, and there are some reports that a kernel change might change things, including some cases where it was needed to fully disable C-States to gain back stability.

Thanks for the response. I've enabled syslog (although I have memory of looking at this before and getting nothing but maybe someone else will see something I didn't)

I'll check the idle control next reboot, this is something I've just learned about today, up until now unraid has always "just worked"

@JorgeBHere's my syslog if you can see anything. I'm not even entirely sure what is what here, everytime I think I've made sense of it I realise the times don't match up.

Note I started mirroring before I re-upgraded the system. And I've changed IPs to x.x.x, not that that really makes it more securesyslog

 

Edited November 26, 20223 yr by RoryIsNotACabbage

I've done both the suggestions about idle and c states and no change.

For just now I'm gonna have to downgrade again.

Try booting in safe mode to rule out any plugin issues but it could be a compatibility issue between your hardware and the newer kernel.

On 11/27/2022 at 10:09 AM, JorgeB said:

Try booting in safe mode to rule out any plugin issues but it could be a compatibility issue between your hardware and the newer kernel.

Apologies for taking so long to mark this solved, I was pre-clearing a drive and then I honestly just forgot for a while.

 

I've now run it a solid couple days in safe mode and it was good, so I removed every plugin (That really sucked) and it now runs fine unsafe. So now we slowly add things back and keep our fingers crossed.

 

Thanks for your help on this

Did you find out which plugin it was? Mine is doing the same thing. The GUI just said I had a corrupted flash drive and I was just going to buy a new one until I decided to check the forums and saw your post.

I never found out which one, I've been adding them back very slowly cause I've not spent as much time recently in the same location as my server is.

 

I never had an issue with the flash drive though, just an errorless blackscreen