Unraid hangs on boot after updating from 6.10 to 6.13 stable Diagnostics attached... I can get get the server to boot only if I enter the bios, then exit... it will boot up just that once. Any reboot or power down and restart causes it to hang again on boot....  Unless I enter the bios on startup and then exit it seems to only boot under this condition.  I receive the below error in the system log:

x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

Please help I cannot afford to lose my server. Any feedback on what to do is appreciated.

unraid2-diagnostics-20241018-0948.zip

Try booting with a different flash drive using a stock 6.12.13 install, no key needed, then retest to see if the issue is the release or the config.

2 minutes ago, JorgeB said:

Try booting with a different flash drive using a stock 6.12.13 install, no key needed, then retest to see if the issue is the release or the config.

Thanks for the feedback. Can I just downgrade back instead? its quicker to do that rather than obtaining another drive... will do so  if its the only option. thanks

 

You can do it using the GUI.

I just downgraded and it reboots without issue ... so something is wrong with 6.12.13

 

14 minutes ago, JorgeB said:

You can do it using the GUI.

So I just downgraded back to  6.12.10 and the server now reboots again without error. So its a bug or something that changes in 6.12.13 causing the issue for me. I would suspect something in 6.12.13 is causing this issue??>>>  SYSLOG indicating "crashing the kernel on kernel split_locks and warning on user-space split_locks"

I see there is middle update being skipped which is 6.12.11 ... should I update to that first instead of going directly to 6.12.13?
Any help or feedback is appreciated... I cannot be stuck downgraded indefinitely. Thank you!!!

Edited October 18, 20241 yr by Maz

I would guess more likely a compatibility issues with your hardware, since thousands of users are using 6.12.13, it would still be good to boot with a clean install to confirm it's not a config/plugin issue.

Thanks...

41 minutes ago, JorgeB said:

I would guess more likely a compatibility issues with your hardware, since thousands of users are using 6.12.13, it would still be good to boot with a clean install to confirm it's not a config/plugin issue.

Thanks. I was able to get as far as 6.12.11 without issue. When I go to 6.12.13 is when this issue starts. Might I ask, How do I get the attention of the Dev team to look at my diagnostics and determine the root cause? can this post be at least noted? I have standard hardware and controllers used in my build. To be honest there is nothing unique about my hardware that should cause this... if so, I would like to think it would be beneficial to all to understand where the issue lies.  If I move up to the 7.0 betas, is there the chance they will work? Can I downgrade back to 6.12.11 after upgrading to 7.0 B3 if there are still issues?   Thanks again..

Did you try a stock install?