I wonder if anyone has any clue.

 

After the upgrade,  when rebooting, stuck at a particular point, see iKVM_capture(1).jpg

 

When booting 6.11.5, it goes smoothly and the corresponding section in the booting log looks like the following:

 

:
:
Oct 25 22:29:09 vault kernel: pci 0000:03:00.0: PCI bridge to [bus 04]
Oct 25 22:29:09 vault kernel: pci 0000:03:00.0:   bridge window [io  0xd000-0xdfff]
Oct 25 22:29:09 vault kernel: pci 0000:03:00.0:   bridge window [mem 0xf6000000-0xf70fffff]
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: working around ROM BAR overlap defect
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: [8086:1533] type 00 class 0x020000
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: reg 0x10: [mem 0xf7700000-0xf777ffff]
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: reg 0x18: [io  0xc000-0xc01f]
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: reg 0x1c: [mem 0xf7780000-0xf7783fff]
Oct 25 22:29:09 vault kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.2: PCI bridge to [bus 05]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.2:   bridge window [io  0xc000-0xcfff]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.2:   bridge window [mem 0xf7700000-0xf77fffff]
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: working around ROM BAR overlap defect
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: [8086:1533] type 00 class 0x020000
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: reg 0x10: [mem 0xf7600000-0xf767ffff]
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: reg 0x18: [io  0xb000-0xb01f]
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: reg 0x1c: [mem 0xf7680000-0xf7683fff]
Oct 25 22:29:09 vault kernel: pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.3: PCI bridge to [bus 06]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.3:   bridge window [io  0xb000-0xbfff]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.3:   bridge window [mem 0xf7600000-0xf76fffff]
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0: [10b5:8518] type 01 class 0x060400
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0: reg 0x10: [mem 0xf7300000-0xf731ffff]
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:1c.4 (capable of 16.000 Gb/s with 2.5 GT/s PCIe x8 link)
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.4: PCI bridge to [bus 07-0a]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.4:   bridge window [io  0x9000-0xafff]
Oct 25 22:29:09 vault kernel: pci 0000:00:1c.4:   bridge window [mem 0xf7100000-0xf73fffff]
Oct 25 22:29:09 vault kernel: pci 0000:08:01.0: [10b5:8518] type 01 class 0x060400
Oct 25 22:29:09 vault kernel: pci 0000:08:01.0: PME# supported from D0 D3hot D3cold
Oct 25 22:29:09 vault kernel: pci 0000:08:02.0: [10b5:8518] type 01 class 0x060400
Oct 25 22:29:09 vault kernel: pci 0000:08:02.0: PME# supported from D0 D3hot D3cold
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0: PCI bridge to [bus 08-0a]
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0:   bridge window [io  0x9000-0xafff]
Oct 25 22:29:09 vault kernel: pci 0000:07:00.0:   bridge window [mem 0xf7100000-0xf72fffff]
:
:

 

Configuration:

M/B:Supermicro X10SL7-F Version 1.01 - s/n: NM157S007108

BIOS:American Megatrends Inc. Version 3.0. Dated: 04/24/2015

CPU:Intel® Core™ i7-4790K CPU @ 4.00GHz

HVM:Enabled

IOMMU:Enabled

Cache:256 KiB, 1 MB, 8 MB

Memory:32 GiB DDR3 (max. installable capacity 32 GiB)

1. 0215 CMV8GX3M1C1600C11, 8 GiB DDR3 @ 1600 MT/s
2. 0215 CMV8GX3M1C1600C11, 8 GiB DDR3 @ 1600 MT/s
3. 0215 CMV8GX3M1C1600C11, 8 GiB DDR3 @ 1600 MT/s
4. 0215 CMV8GX3M1C1600C11, 8 GiB DDR3 @ 1600 MT/s

Network:eth0: 1000 Mbps, full duplex, mtu 1500

• eth1: 1000 Mbps, full duplex, mtu 1500
• eth2: interface down
• eth3: interface down
• eth4: interface down
• eth5: interface down

Kernel:Linux 5.19.17-Unraid x86_64

if you have access to the diags... others will ask for this... to me... I would question the USB... 

 

IMO... back up this USB and ensure that you have a good copy of the drive order/setup... 

 

reimage the USB with a fresh install of unraid... boot and create a new array with the drive order copied from before... you shouldnt have an issue with this...

 

there have been a number of upgrade issues recently... starting fresh is the way to go... ensure that the USB is healthy... and reimage it... that's my 10 cents

 

 

I will but in this warning... I am a lightweight when it comes to assisting others here... but wait for others to comment... dont take action on my advice

Is there any hardware being passed through to a VM?   If so this can cause an issue when upgrading if the hardware IDs are different on the new version and the pass-throughs need disabling before the upgrade and redoing afterwards.

It turns out i have a Supermicro AOC-SG-I4 4 port LAN card.  Removing it and the reboot goes to completion and UNRaid is up and running 6.12.13.

The 4 port LAN card is Intel 82576 based card.

 

I suspected earlier that the stuck at reboot might due to hw passthrough to some VM that is no longer run.  I therefore reboot with a fresh 6.12.13 USB stick.  The reboot is stuck at the very same point.

 

I therefore open the sever and see this unused LAN card.

 

Removing it and the UNRaid is fine

Edited October 27, 20241 yr by dandus