Today I moved my array, cache and usb over to the new build, listed below. I ran into a strange issue that I haven't been able to find any information on, and I have been digging through prior posts and other sites.

 

MOBO: ASRock z790 Lightning WiFi

CPU: intel i7-14700k

RAM: Corsair Vengeance DDR5 2x32gb

 

Issue: Unraid will boot into any other option but "Unraid OS". Right now I have it running as "Unraid Webgui", which has it functional with no errors showing the logs. All apps, plugins and vms start with no errors.

 

If I try to boot to Unraid OS the system loads all the way up until it trys to launch the OS, no errors shown, and locks the system up. The last entry is loading mcelog. The only way to resolve is a hard restart.

 

A clean install on the usb of unraid does boot without issue.

 

Steps already taken:

1) updated the bios for the 14th gen chip.

2) Went through the bios to verify virtual infrasture and vt-d is enabled.

3) fast boot is disabled(no change)

4) secure boot is disable(no change)

5) rebuilt the usb using unraid creator and manual creation. Then moved the config over. 

6) Replaced the prior usb with a new one.

7) Removed all of the plug-ins and re-installed once getting the system up under "Unraid WebGui"

 

Moved everything back to the old build and it boots fine again.

 

Everything points to an issue with the config somewhere, but I am not sure where to look. I don't want to wipe the data from the array and start over as I have a lot of unique configs built.

 

Any advice is appreciated and thank you.

 

Edited August 23, 20241 yr by renzema

4 hours ago, renzema said:

A clean install on the usb of unraid does boot without issue.

This suggest the current config is the problem, you can try redoing the flash drive, backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

8 hours ago, JorgeB said:

This suggest the current config is the problem, you can try redoing the flash drive, backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

 

Just for clarification.

I am going to need to move storage, pool, cache, key file, and super.dat. That will give me all of my data and arrary but nothing more correct? I am fine rebuilding the docker containers and plug-ins, if I have to, however want to avoid needing to re-add all the data.

33 minutes ago, renzema said:

That will give me all of my data and arrary but nothing more correct?

Correct.

3 hours ago, JorgeB said:

Correct.

Thank you for the assistance.

After rebuilding the usb, slowly added back configs until I found the root cause. Something in the docker configs was failing out. Was able to get the array, plugins, VMs and server configs though and I will take that as a win. Just glad to have all of the folder permissions and SMB users/pass back on it.

 

Would love to know what in there causes the issue, being it works perfect on my old build and only fails on the new build.

Edited August 23, 20241 yr by renzema