boot failure upgrading to 25.03.b.20250306.0140 i
-
@netblues Hello guys! I run an HP ProLiant ML310e Gen 8 physical machine and I'm experiencing this issue, could anyone help?
I didn't want to have to reconfigure everything, I have backups saved but there's always something that we change and forgets to copy the most recent backup
I don't use virtual machine, could someone help. Thank!
-
@renanlofiego This is related to virtio and kvm only.
Your case seems different. Any logs?
-
@stephenw10 said in boot failure upgrading to 25.03.b.20250306.0140 i:
Hmm, so I managed to get some modern devices but it still boots using:
Now that ce version does the same, I will try installing to a fresh alma linux machineI'm using bridge network interfaces too, but this doesn't explain booting issues
I don't seem to get many options too
-
@netblues It's practically the same screen that says they have errors.
I thought there was some command line that could solve it.
-
@renanlofiego Well, it seems it cant mount the boot volume and ends up the same.
However, the root cause is before that.
Can you capture booting via serial port?
Hardware details like raid, secure boot, bios settings etc is also of interest in a physical machine. -
@netblues Now I don't have a serial cable now :(
-
@netblues One question, maybe you can answer me better, I have a backup from January, since then I haven't changed anything major, and I have LAGG, 2 WAN, LAN ADM and other interfaces and a bunch of firewall rules, if I reinstall pfsense and pull this backup will everything go back to normal or will I need to reconfigure something?
I imagine it will work because everything is in the right place, what do you think?
-
@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. -
@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.
-
@renanlofiego and you also run pfSense Plus 24.11 and did an upgrade to 25.03-BETA?
-
@patient0 This was already the second beta of 25.03
-
@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 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 diskda1.da0is a CD-ROM which something is mounted, 3888MB in size (is a CD-ROM mounted? if yes, what is the boot order?)
da1is 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.
-
@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!
-
@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
-
@stephenw10 Just for clarity this is an upgrade from 24.11 to the latest beta.
Didn't try the previous beta. -
@netblues Yes, I'm aware, it really was a problem, I always participate in betas but after restarting I had this problem.
-
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?
