Had a perfectly working 6.9.x unraid instance and upgraded to 6.10.1. received kernel panic (attached) on first boot after upgrading.

 

So far i've wiped the USB flash drive and created a totally vanilla instance, same error.

I've tried setting root-sda in syslinux.cfg, same error.

reverted the chanbges made in syslinux.cfg, same error.

Tried booting in both UEFI (No CMS) mode and Legacy BIOS boot, same error.

Veried that secure boot was disabled in each scenerio.

 

I've tried just about everything I can think of to fix the problem. I'm Kind of regreting that i took the leap to upgrade from 6.9.x I hoave no idea why this would suddenly occur on my server? my USB drive has one partition and was created by the official tool. also occurs with a vanilla USB drive at this point.  I suspect this might have something do to with the chipset on the mobo but I just dont know enough on how i might  go about passing thru the kernel panic. Any asisstance would be much appreciated at this point. Totally stumped and somewhat in a panic.

 

Update: Whats even stranger is that when i boot a vanila instance in either UEFI or BIOS mode, the boot menu does not appear. rather it just goes straight to booting the default menu item which boots as headless. I dont even get a boot option to boot in GUI mode.

 

Edited May 31, 20224 yr by nerdzero

Looks like a failure reading files off the flash drive, so have you tried the procedure documented here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI?

On 5/31/2022 at 1:26 AM, itimpi said:

Looks like a failure reading files off the flash drive, so have you tried the procedure documented here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI?

 

Many thanks for reaching out itimpi. After carefulluly reading thru the documentation, I was able to determine 'in part' the cause of the kernel panic that has been re-occuring on my server. I say in part only becaue I had to tinker with the /EFI boot loader to get 6.10.2 fully funtional. I replaced the stock bootx64.efi file with the rEFInd boot loader, thus producing a hybrid UEFI + Legacy Boot loader. Upon rebooting the system with the rEFInd boot loader in place, I was able to fully boot the server by selecting the option to boot Linux (Legacy) from UNRAID from the rEFIns Main Menu. (attached). Next, I was presented with the official Lime Technologies boot menu. I selected athe default boot option. The system booted and I was able to get to the login prompt.

 

I later soon discovered that my network interface had been lost in the shuffle somehow (eth0 does not exist).  I placed an empty tg3.conf file in boot/config/modprobe.d/ as sugested in the documentation and rebooted. UnRAID now boots with or without gui. Safe mode also appears to boot without fail. This one really had me stumped. Thanks again for your guidance. 

 

Edited June 3, 20224 yr by nerdzero

Hello,

is it possible that you upload the config files or is it just the way that the Bootx64.efi file is exchanged!? I've also tried other bootloaders that also work, but if it was able to boot completely to the prompt without user input, that would be great!