Hi all,

 

Hopefully you can assist with this problem. We shutdown our docker and vm manager and made a network change.

We added Ip address to another interface and applied change but the server locked up when we did this.

We were running for current beta. When we plug a monitor in this is what we see. We tried to reboot and same effect.

Would anyone have any suggestions on how to fix 

Try booting with a new flash drive using a stock install, no key needed, that will confirm if the flash drive, or the config, is the problem

Yes, it will boot with a different USB with a stock image.

Edited November 26, 20241 yr by gvtci

Now try recreating your flash drive, backup the current one first and then recreate it using the USB tool and restore just the /config folder, retest, if it boots it was a flash drive issue with the OS files, if it still doesn't, there's a config problem, you can then try to drill down on that issue.

 

 

 

 

Nope it don't boot after recreating. I can go to an older backup, but I did some expansions

a few days ago and they wont be in it.

 

 

I can access the old flash as it's readable. Looking at the configs using vi it looks like the network.cfg is boned.

It's just gobbly goop machine lang. Sign,  I will look on an older backup for the network.cfg file and try again.

Thanks Jorge for putting me on the right track. I took just the network.cfg from an old flash backup and replaced it on the usb that won't boot. The unraid server now boots and starts (No new key necessary)  and the problem is resolved. Strange though, why did it corrupt the network.cfg file though? I did the network editing through the network settings area in the gui. 

10 minutes ago, gvtci said:

why did it corrupt the network.cfg file though?

Could have been a flash issue, that's not normal.