unraid 6.2.4 boot only in gui mode

[Besark]

hi

 

i have installed new hardware cpu+motherboard),now i can only boot from gui mode,in normal mode it reboot instantly

 

i will fix it 

 

thx

[Mortumus]

I have the same problem.

I was told last night it's possibly something to do with the virtual RAM stored on the USB for each boot environment (or something like that). The GUI and the non-GUI boots will have different VM RAM files. The ram is backed up to disc if you like. Sounds a bit like a paging file on Windows.

If the server goes down suddenly (like mine did, the toaster blew the fuse), the VM RAM can become corrupted. I could have my terms wrong here, but it's a Linux thing.

The solution I am told is to download the latest copy of Unraid and overwrite the files on the USB with it. I'm not sure what happens to your configuration so perhaps someone else can chip in here with that info. I'm just passing on and paraphrasing what I was told by my Linux guru mate.

Edited March 12, 2017 by Mortumus

[Mortumus]

I tried this out.

1. First I backed up the USB onto another computer.
2. I downloaded the same build of Unraid as I had installed (6.3.2).
3. After extracting the files I copied everything over the top of the existing files, except my config files
4. I booted back up but it was exactly the same issue.
5. I then copied all of the files including the config files and booted back up.
6. Still the same issue but now the configurations are reset.
7. I then just copied the original files on again ... still the same issue but the configs are back to how they were.
8. Back to the drawing board.

[Mortumus]

OK ... another stab in the dark which worked. As this started after the upgrade to 6.3.2 I figured I'd try and revert back.

1. I simply copied the bzimage, bzroot and bzroot-gui files from the 'previous' folder on the USB (which seems to be the previous version).
2. I copied these over the current version files on the USB.
3. When I booted it went through the motions just fine in non-gui mode and booted OK.

If this didn't work I was going to simply try and change the menu so that the gui mode was the mode that booted unattended.

I'll try and upgrade again and see what happens, but I suspect i'll get the same issue.

 

Any other ideas welcome as this has allowed me to boot unattended, but it's not ideal.

[Airless]

I just recently went through this problem upgrading from v6.1.9 to v6.3.5 I had the same symptoms you describe and discovered in another thread that some of the newer X11 Supermicro boards have an issue when certain BIOS settings are enabled. I don't know the exact settings but basically setting the BIOS to default optimized settings fixed the issue for me. The specific post that helped me was here but there's lots of info on the page before and after in this thread.

 

Not sure if your board is an X11 Supermicro but if so this could be a solution.