24.03 Update not booting

Mike-moon

Hi,
I am curious on your findings as my system behaves the probably the same. No clue whether it is also a driver issue but it always worked fine with 23.09.1 but does not start with 24.03. (The old start log shows a missing driver for my onboard WiFi but this should certainly not prevent the new system from starting.)
Regards, Michael

hypnosis4u2nv

@stephenw10 Ah, makes sense. Didn't realize it stayed on that branch after reverting back.

Here's the update log from the GUI for 24.03 if that helps.Update.txt

hypnosis4u2nv

@stephenw10 Here's the boot log for 23.09.1 boot log.txt

Mike-moon

@stephenw10 : In case it helps, here also my dmesg.txt from 23.09.1.

stephenw10

Ok different drives and different driver controllers.

@Mike-moon Are you actually seeing the same identical error?

@hypnosis4u2nv Your boot log from 23.09.1 shows the same error:

ahci0: <Intel Sunrise Point-LP AHCI SATA controller> port 0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xdf628000-0xdf629fff,0xdf62c000-0xdf62c0ff,0xdf62b000-0xdf62b7ff irq 16 at device 23.0 on pci0
ahci0: AHCI v1.31 with 3 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
...
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <SAMSUNG MZMTE256HMHP-000MV EXT41M0Q> ACS-2 ATA SATA 3.x device
ada0: Serial Number S1F1NSAG782964
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 244198MB (500118192 512 byte sectors)
ahcich0: Timeout on slot 28 port 0
ahcich0: is 00000000 cs 00000000 ss 10000000 rs 10000000 tfd 40 serr 00000000 cmd 0000c217
(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 10 90 2d 20 40 0b 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Command timeout
(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain

It seems likely to be the disk. Can you test a different drive?

hypnosis4u2nv

@stephenw10 Don't have a spare drive. Wouldn't hurt to get another one to swap out. Although I'll be starting a fresh install when I do. It's interesting though that it continues to boot past the error while on 24.03 it wants to hang.

Mike-moon

@stephenw10 : Seems that I do not have exactly the identical error. System seems to hang already in the bootloader.

stephenw10

It is. It could be a driver difference there causing that as a symptom and not a cause. I'm not aware of anything known that presents like that.

I would try to compare the boot log from 23.09.1 to that from 24.03. You might find, for example, that 24.03 has additional drivers that attach to some device you have and that is causing a conflict.

Mike-moon

@stephenw10 : But the system did not start at all after four upgrade attempts. Can I nevertheless find log files that may point on the conflict? Is there a boot log from 24.03 in case the boot was not successful?

stephenw10

Nope sorry our replies got out of order, my last was for the drive/drive controller issue.

You are stuck on the EFI frame buffer so some UEFI issue. I assume that's not a VM?

Mike-moon

@stephenw10 : No, it's a real machine. Is there anything I could do?

stephenw10

What hardware is it? It must have some UEFI quirk we have not seen locally.

hypnosis4u2nv

@stephenw10 Anyway to get the boot logs for 24.03 without a console cable? I ordered an mSATA drive for the box so I'll have to wait on that or the console cable, whichever gets here first. Curiously, are you seeing any reports similar to this issue?

stephenw10

No not that drive/drive controller error like that.

If you interrupt the boot at the console and prevent it rebooting you should be able to scroll back through the screen buffer to see what is shown. Or if you are able to boot into single user mode you can run dmesg to see that.

svc

@Mike-moon

I'm seeing the same, using a v.8.1.4 Proxmox VM:

!

Xeon D-1747NTE SuperMicro SYS-E300-12D-10CN6P host, 2 PCI NIC passthrough:

Mike-moon

@stephenw10 : Update: The EFI issue is gone - I don't know why. After being back in 23.09.1 I simply changed the update settings back to the previous version (23.09.1). A refresh on the dashboard shows the new release. I clicked it and changed the update settings to 24.03. and it did not stuck in the bootloader. Really, that' all I have done.

But it was interesting, that 24.03. starts (unfortunately not complete). In my setup, pfSense is located behind a cable modem that is in bridge mode. Sometimes, it happens that pfSense does not immediately get an WAN address and it's not clear to me whether it had a WAN connection. However, it tried to download all the Emerging Threats and Snort rules and ran into a timeout for all of them. I did not exactly check the time, but the unsuccessful download process at least took 10 minutes. Then, it went fast: It automatically performed a reboot - and I was back at 23.09.1...

stephenw10

That's a known issue: https://redmine.pfsense.org/issues/15396
Though I wouldn't expect it to take that long to timeout. Unless maybe you have a very large number of lists.

Try uninstalling pfBlocker and Snort/Suricata and then upgrading.

stephenw10

@svc said in 24.03 Update not booting:

I'm seeing the same, using a v.8.1.4 Proxmox VM:

If you have the CPU set as 'host' type. Try setting it as kvm64 instead.

svc

@stephenw10 said in 24.03 Update not booting:

If you have the CPU set as 'host' type. Try setting it as kvm64 instead.

The VM CPU was x86-64-v2-AES.

I restored a VM backup to v.23.09.1, changed CPU to "kvm64" and applied the v.24.03 upgrade with same boot error.

Restored VM backup to v.23.09.1, changed CPU to "host" and applied the v.24.03 upgrade. Same boot error. Rebooted a second time and v.23.09.1 successfully loaded. Went into "Boot Environments" and enabled v.24.03 boot environment and rebooted successfully, completing the v24.03 upgrade (using CPU as "host" type).

Not sure what happened, but have finished the upgrade and I'll continue using CPU set as "host" type for now.

Thank you for your input.

stephenw10

Hmm, odd. That's the opposite of what some other users have reported!
Glad you got upgraded though.