After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....
-
@stephenw10
Hello, no the config has been the same for months -
Same issue observed just now on a VM that's had 0 issues with 24.03. Hard reboot on the VM booted successfully back into 24.03.
-
@stephenw10
Also I only have this one device and I have never imported a config to this device from any other device, it's the original config file. -
Were any of these units previously updated from 23.09 OK?
-
@stephenw10
I took shipment June24 so I don't expect ~9 month old firmware (23.09) was on there. I assume 24.03 came installed. Not sure how to check otherwise. -
@freph533 said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
Same issue observed just now on a VM that's had 0 issues with 24.03. Hard reboot on the VM booted successfully back into 24.03.
What type of VM? If it's Proxmox and running an EFI BIOS, it may be something we've hit before (adding a serial port to the VM hardware works around it) but that's different than the other problems reported in this thread.
-
@d9001089 said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
After I upgraded to 24.11 the reboot hangs at Start @0xffff... After waiting for 2 hrs I finally had to to unplug my 4200 to get it to boot successfully, however the upgrade was unsuccessful. Does anyone have any idea whats going on?
Can you (or someone else hitting this) try again but capture the serial console output for the entire boot? We need to see what came before this point, ideally the entire initialization process if possible.
Also if someone hitting this could post the contents of their
/boot/loader.confand/boot/loader.conf.localfiles that would help. -
@jimp
Here is my loader.conf but I dont have a loader.conf.local. Also I'll try it again and copy the console contents to this post.../root: cat /boot/loader.conf
opensolaris_load="YES"
zfs_load="YES"
kern.cam.boot_delay=10000
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
kern.ipc.nmbclusters="1000000"
kern.ipc.nmbjumbo9="524288"
kern.ipc.nmbjumbop="524288"
loader_conf_files="/boot/loader.conf.lua"
boot_serial="YES"
comconsole_speed="115200"
console="efi"
autoboot_delay="3"
debug.ddb.capture.bufsize="524288"
hw.e6000sw.default_disabled=1
hw.hn.vf_transparent="0"
hw.hn.use_if_start="1"
net.link.ifqmaxlen="128"
machdep.hwpstate_pkg_ctrl="0"
net.pf.states_hashsize="262144"/root: cat /boot/loader.conf.local
cat: /boot/loader.conf.local: No such file or directory -
@stephenw10
I have had the uint for about a year and have only done one upgrade to 24.03 -
@jimp
I re-ran the upgrade to get the print out you wanted from the console and this time it completed successfully... I didn't do anything except for uninstall the Acme package because its been crashing do to a PHP error which I will list below, if you have any insights, and yes I will create a new ticket in another channel for this issue.16:16:02 PHP ERROR: Type: 1, File: /usr/local/www/acme/acme_accountkeys.php, Line: 158, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/acme/acme_accountkeys.php:158
Stack trace:
#0 {main}
thrown -
Are you seeing that error in 24.11 if you reinstall the pkg? Or just in 24.03?
-
@stephenw10
Yes, and now I don't see the acme menu option under services even when i do a reinstall. The only way to get to it is using the URL. Once I'm at acme.xml page I select account keys and that's when it crashes. -
Ok opened a bug to track that: https://redmine.pfsense.org/issues/15892
-
Anyone hitting this console issue try booting verbose. Escape the loader menu to the prompt (OK>) and enter:
boot -v -
@jimp said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
@freph533 said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
Same issue observed just now on a VM that's had 0 issues with 24.03. Hard reboot on the VM booted successfully back into 24.03.
What type of VM? If it's Proxmox and running an EFI BIOS, it may be something we've hit before (adding a serial port to the VM hardware works around it) but that's different than the other problems reported in this thread.
Yes, it's in Proxmox on EFI BIOS. There's no serial port on the VM hardware so that might be part of the cause in my case, though given the feedback from others it seems like it may be something else.
@stephenw10 Given my setup with the Proxmox VM is it still useful for me to provide output on an attempted upgrade (and if so, with or without adding a serial port to the VM devices? FWIW I've never had issues through several upgrades without a serial device on this VM)?
-
Yes, if you can try booting verbose after the upgrade.
Also you could try adding a serial port to confirm if that has any effect since that might be a useful clue.
-
@stephenw10 said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
Yes, if you can try booting verbose after the upgrade.
Also you could try adding a serial port to confirm if that has any effect since that might be a useful clue.
Adding the serial device let me upgrade successfully. Upon removing the serial device and attempting multiple reboots it hangs at the same spot with the error. Adding the serial device back lets the VM boot again. So it seems like 24.11 has a hard dependency on a serial port existing whereas 24.03 does not.
-
@freph533 said in After upgrade 24.03 to 24.11 reboot hangs at start @ 0xffffff....:
So it seems like 24.11 has a hard dependency on a serial port existing whereas 24.03 does not.!
It's not new in 24.11, it just seems to hit some VMs differently than others, and we haven't nailed down why yet:
-
Happening to me with a 24.03 to 24.11 upgrade on a Netgate 4200 MAX
Verbose boot logs, unfortunately doesn't offer anything new:
OK boot -v Loading kernel... /boot/kernel/kernel text=0x1a4c98 text=0xff3048 text=0x17ed568 data=0x180+0xe80 data=0x24c808+0x3b37f8 0x8+0x1d4108+0x8+0x1e9a19 Loading configured modules... /boot/kernel/opensolaris.ko size 0x1e2a8 at 0x37be000 /boot/kernel/zfs.ko size 0x619a40 at 0x37dd000 can't find '/boot/entropy' can't find '/etc/hostid' staging 0x3fa00000-0x43f40000 (not copying) tramp 0x43f40000 PT4 0x43f41000 Start @ 0xffffffff803a5000 ... / -
I opened a ticket with TAC support and they're telling me to "just reinstall the software". No effort to try and figure out what's wrong.
I don't doubt a reinstall will help, but what worries me is if it doesn't I'll have to then reinstall to 24.03 and that's downtime I can't afford when I use this device for my work.
I'll have to sit on 24.03 until the issue is identified.
