boot failure upgrading to 25.03.b.20250306.0140 i

netblues

@renanlofiego Backup taken via pf? of something else?
I beleive if you reinstall 2.7.2 and it boots then restoring configuration is the obvious choice.

Still a hassle.

Yes you can, this is how I posted the above. You need to configure this in pf first
It is in systems, advanced, bottom of page.

renanlofiego

@netblues Whenever I changed something, I backed up the settings and then I just tested it on a virtual machine and it seems to have restored everything, it just didn't work perfectly because my virtual machine didn't have as many cards as the physical one did.

patient0

@renanlofiego and you also run pfSense Plus 24.11 and did an upgrade to 25.03-BETA?

renanlofiego

@patient0 This was already the second beta of 25.03

patient0

@renanlofiego said in boot failure upgrading to 25.03.b.20250306.0140 i:

This was already the second beta of 25.03

You are right, I just wanted to make sure that you are on Plus and not on CE 2.7.2 trying to upgrade to 2.8.0 Beta, or making a new installation.

renanlofiego

@patient0 @netblues Oh yes, I've been using Plus for a long time as a lab, but this is the first time I've seen this problem.

I'm still working on it and now it seems like another screen has appeared...

But I'm terrible at command lines here, I'm more of an administrator lol

renanlofiego

@netblues @patient0 I followed these guidelines with ? and listed this disk, it doesn't help at all

patient0

@renanlofiego you also have line like @netblues,

Mounting from zfs:pfSense/ROOT/default_20240714144502_20250329075912_20250329082412_20250329142348_20250401180456 failed with error 5.

I haven't had to deal with that kind of issue yet.
In your output of '?, I see that I assume is EFI/UEFI, your disk da1.

da0 is a CD-ROM which something is mounted, 3888MB in size (is a CD-ROM mounted? if yes, what is the boot order?)
da1 is an 24GB disk and the 2nd screenshot shows the disk by diskid. It's (U)EFI boot and seems to have 2 partitions da1p1 and da1p2.

Other than that it may as well be a bug.

renanlofiego

@patient0 I went to Boot Environment (option 8) and there were 18 different selections, I chose the most recent version and went back up, it worked again. It must be some bug in this beta. Thanks for your time!

renanlofiego

@patient0 It was the pen drive that was plugged into the USB, I was almost reinstalling everything, I tried a little more and it worked lol

That's what I selected in the boot menu, I know it worked but if I restart it won't work, I'll leave it like that and see later, I didn't even sleep today. It's 5:00am here and I get up to work at 6:30am lol

netblues

@stephenw10 Just for clarity this is an upgrade from 24.11 to the latest beta.
Didn't try the previous beta.

renanlofiego

@netblues Yes, I'm aware, it really was a problem, I always participate in betas but after restarting I had this problem.

stephenw10

Mmm, so just to review; if you change the disk type to something other than vitio block device (modern) it finds it and boots but still fails to find the virtio (modern) NICs?

netblues

@stephenw10 said in boot failure upgrading to 25.03.b.20250306.0140 i:

Mmm, so just to review; if you change the disk type to something other than vitio block device (modern) it finds it and boots but still fails to find the virtio (modern) NICs?

Yes, this is exactly the case.

If I change virtio ethernet to e1000, it also finds network interfaces.

netblues

@stephenw10 fiddling around I think I found the curlpit.
At some point kvm switched default emulated machine from i440fx to q35.
Latest supported os under latest kvm (or at least redhat supported) is freebsd14

So if hypervisor defaults are

Then virtio drivers don't work under freebsd15

changing to

makes virtio work again.

The problem is that changing this with virsh edit isn't easy, since it also changes pci configuration.
The obvious way forward is creating a new freebsd 14 vm, with manual config.
Add interfaces as needed,
adjust vlans/passthrough/bridges and maybe mac addresses as need
and then move the disk subsystem to the new config with virsh edit.

This allowed me to upgrade ce 2.7.2 to ce 2.8 without issues, and most probably it will also work
for plus,
I don't know if older chipset has any performance or other penalties, but pf used to work under this, and only changed to q35 recently.
I suspect freebsd15 dropped/changed something in virtio driver support.

netblues

@netblues And also plus updated to 25.03 beta, with no issues. Dirty upgrade too.

stephenw10

Hmm, interesting. I tried usssing a Q35 machine in Proxmox and it booted fine. That in itself also didn't change the PCI device type either.

I think it must be changing the presented PCIe controller since it seems to fail to detect entirely any NICs or the drive controller. Still couldn't make Proxmox do it though even with a bunch of custom command hackery.

netblues

@stephenw10 actually pcie isn't supported in i440fx, you have to change this to pci
In older kvm implementations, creating a new freebsd13.1 would create a q35 based virtual machine.
Now if you create a new freebsd14 i440fx is selected.

Proxmox isn't a redhat derivative as you know , too.

In any case, no issues in new installations. Upgrades will hurt "randomly" since this isn't really pfsense related. Its upstream freebsd

stephenw10

@netblues said in boot failure upgrading to 25.03.b.20250306.0140 i:

actually pcie isn't supported in i440fx,

Hmm, interesting. I wonder if my change didn't really apply somehow then.

jimp

Were you using an odd mix like q35+BIOS instead of q35+UEFI?

FreeBSD 15.x recently changed some things in probing of older ISA style devices, which I wouldn't expect to impact things here, but it's possible some quirk in that combination triggered an issue.

I use q35+OVMF/UEFI on nearly all my Proxmox VMs with all virtio devices (Proxmox 8.3.5) and everything runs perfectly.

I still have a few that are using i440fx+BIOS and all virtio devices and they're good, too.