Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    boot failure upgrading to 25.03.b.20250306.0140 i

    Scheduled Pinned Locked Moved Plus 25.03 Develoment Snapshots
    65 Posts 7 Posters 3.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      renanlofiego @patient0
      last edited by 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

      dad4ffe6-2885-4535-97e6-2eef95d9ff1e-image.png

      R 1 Reply Last reply Reply Quote 0
      • R
        renanlofiego @renanlofiego
        last edited by

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

        fcb748e3-ac78-40c6-924a-7c9213d8863e-image.png

        patient0P 1 Reply Last reply Reply Quote 0
        • patient0P
          patient0 @renanlofiego
          last edited by

          @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.

          R 2 Replies Last reply Reply Quote 0
          • R
            renanlofiego @patient0
            last edited by

            @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!

            1 Reply Last reply Reply Quote 0
            • R
              renanlofiego @patient0
              last edited by

              @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

              266a1a3a-9b45-4db6-8c9d-570c34124f84-image.png

              1 Reply Last reply Reply Quote 1
              • N
                netblues @stephenw10
                last edited by

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

                R 1 Reply Last reply Reply Quote 1
                • R
                  renanlofiego @netblues
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    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?

                    N 2 Replies Last reply Reply Quote 0
                    • N
                      netblues @stephenw10
                      last edited by

                      @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.

                      1 Reply Last reply Reply Quote 1
                      • N
                        netblues @stephenw10
                        last edited by

                        @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

                        34c56738-cfe8-4a09-a322-c5662f46de26-image.png

                        Then virtio drivers don't work under freebsd15

                        changing to
                        d2fa336d-6cff-4907-9a43-4739da0cacc1-image.png

                        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.

                        N 1 Reply Last reply Reply Quote 0
                        • N
                          netblues @netblues
                          last edited by

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

                          1 Reply Last reply Reply Quote 1
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            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.

                            N 1 Reply Last reply Reply Quote 0
                            • N
                              netblues @stephenw10
                              last edited by

                              @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

                              stephenw10S 1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator @netblues
                                last edited by

                                @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. ๐Ÿค”

                                1 Reply Last reply Reply Quote 0
                                • jimpJ
                                  jimp Rebel Alliance Developer Netgate
                                  last edited by

                                  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.

                                  Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                                  Need help fast? Netgate Global Support!

                                  Do not Chat/PM for help!

                                  N 1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Hmm, yes I probably did end up with Q35+BIOS.

                                    Do you see the PCI devices shown as (modern) in the boot logs?

                                    1 Reply Last reply Reply Quote 0
                                    • jimpJ
                                      jimp Rebel Alliance Developer Netgate
                                      last edited by jimp

                                      I don't see any mention of modern in my logs, they still show as VirtIO (legacy) even on recently created VMs.

                                      In the info qtree of all the VMs it doesn't seem to express a preference either way:

                                                      disable-legacy = "off"
                                                      disable-modern = false
                                      

                                      Same on every device

                                      Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                                      Need help fast? Netgate Global Support!

                                      Do not Chat/PM for help!

                                      1 Reply Last reply Reply Quote 1
                                      • N
                                        netblues @jimp
                                        last edited by

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

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

                                        Everything was/is q35 + bios, but the issue was that after booting couldn't load disk voiume.
                                        Just changing driver to scsci /or sata from virtio would allow startup normaly till network cards not being detected at later stage.

                                        This can't be a uefi thing IMHO.

                                        jimpJ 1 Reply Last reply Reply Quote 0
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate @netblues
                                          last edited by

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

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

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

                                          Everything was/is q35 + bios, but the issue was that after booting couldn't load disk voiume.
                                          Just changing driver to scsci /or sata from virtio would allow startup normaly till network cards not being detected at later stage.

                                          This can't be a uefi thing IMHO.

                                          Declaring that without trying it seems hasty. There isn't much of a compelling reason to run q35+BIOS so it's probably a much less tested combination comparatively.

                                          It absolutely can make a difference in how the system probes devices and boots.

                                          Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                                          Need help fast? Netgate Global Support!

                                          Do not Chat/PM for help!

                                          N 1 Reply Last reply Reply Quote 0
                                          • N
                                            netblues @jimp
                                            last edited by

                                            @jimp 14ed0df1-095b-4560-82cc-f40706dc29b1-image.png

                                            Tried, but it will take more than changing bios settings. Most probably a reinstall

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.