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

    upgrade to 2.7.2 from 2.7.0 failed-install: No space left on device

    Scheduled Pinned Locked Moved
    Problems Installing or Upgrading pfSense Software
    5
    10
    7.0k
    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.
    • P
      pfPanda
      last edited by

      Hi,
      I just tried to upgrade from 2.7.0->2.7.2 from the GUI, and it failed with: "install: //boot/efi/efi/boot/INS@XSQmlE: No space left on device"
      My drive is showing 447GB free 6GB used.

      Thanks in advance for any help or guidance.

      Here is a copy n paste from the upgrade log to window:... correction... the very last part of it.... it keeps getting flagged as spam when i try to include the whole thing
      "
      Installed packages to be UPGRADED:
      pfSense-boot: 2.7.0 -> 2.7.2 [pfSense-core]

      Number of packages to be upgraded: 1
      [1/1] Upgrading pfSense-boot from 2.7.0 to 2.7.2...
      [1/1] Extracting pfSense-boot-2.7.2: .......... done
      Updating the EFI loader
      install: //boot/efi/efi/boot/INS@XSQmlE: No space left on device
      pkg-static: POST-INSTALL script failed
      failed.
      Failed"

      P 1 Reply Last reply Reply Quote 0
      • P
        pfPanda @pfPanda
        last edited by

        @pfPanda
        I did some more digging... perhaps something to do with undersized EFI partition?? And I think I still might be on UFS and not ZFS... thought I was on ZFS and that I wouldn't even have made it to 2.7.0 without that?
        Shell Output - gpart show
        => 40 976773088 nvd0 GPT (466G)
        40 409600 1 efi (200M)
        409640 968474624 2 freebsd-ufs (462G)
        968884264 7888863 3 freebsd-swap (3.8G)
        976773127 1 - free - (512B)

        so I guess next step is to figure out how to increase that EFI partition? and would converting to ZFS be mandatory at this point or optional?
        Thoughts?

        M S 2 Replies Last reply Reply Quote 0
        • M
          Misterb @pfPanda
          last edited by

          @pfPanda said in upgrade to 2.7.2 from 2.7.0 failed-install: No space left on device:

          and would converting to ZFS be mandatory at this point or optional?

          It's optional. I have two pfSense installations, both on 2.7.2 with one zfs and the other ufs.

          P 1 Reply Last reply Reply Quote 1
          • P
            pfPanda @Misterb
            last edited by

            @Misterb Thanks for that info.

            I did some more searching and I think a few others have run into something similar (assuming I am on the right trail here and not waaaaay off-path).

            Would anyone say that the 200M efi partition is a potential issue or ok? What is the state of the art from a fresh install?

            It seemed like one solution was to do a backup, then fresh install of 2.7.2, then restore.... would this 1) give me a bigger efi partition and lessen headaches in the future?, 2) give me less headaches in the future because then would be on ZFS (or would I need to do something particular to go to ZFS before fresh install)?

            I also had this in the upgrade log which I wonder if "normal" or is a problem:
            "
            104/104] Fetching php82-pdo_sqlite-8.2.11.pkg: . done
            Checking integrity... done (4 conflicting)

            • cpu-microcode-amd-20230808 [pfSense] conflicts with devcpu-data-amd-20230424 [installed] on /usr/local/share/cpucontrol/microcode_amd.bin
            • pfSense-2.7.2 [pfSense] conflicts with pfSense-rc-2.7.0 [installed] on /etc/pfSense-rc
            • cpu-microcode-rc-1.0 [pfSense] conflicts with devcpu-data-20230513 [installed] on /usr/local/etc/rc.d/microcode_update
            • cpu-microcode-intel-20230808 [pfSense] conflicts with devcpu-data-intel-20230512 [installed] on /usr/local/share/cpucontrol/06-03-02.00
              Checking integrity... done (0 conflicting)
              Conflicts with the existing packages have been found.
              One more solver iteration is needed to resolve them.
              "
            1 Reply Last reply Reply Quote 0
            • S
              SteveITS Rebel Alliance @pfPanda
              last edited by

              @pfPanda ZFS recreates the disk, needs a reinstall. And yes I’ve seen a couple of posts about EFI size. It must have been small on old installs. The 1100/2100 models ram into that issue with 23.01… reinstall fixes that too. Make a backup but
              https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html

              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
              Upvote 👍 helpful posts!

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

                The error you see is already covered by multiple other threads and Redmine issues...

                It could be one of a few things:

                • Undersize EFI filesystem https://forum.netgate.com/post/1140955
                • There is a memstick installer still plugged in (unplug it before upgrading)
                • The EFI loader from a second disk interfering: https://forum.netgate.com/post/1142397
                • EFI files getting put on the / disk and not the EFI partition: https://forum.netgate.com/post/1143525

                All of those can be worked around but a clean install of 2.7.2 would be the safest bet for success.

                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!

                P 1 Reply Last reply Reply Quote 1
                • P
                  pfPanda @jimp
                  last edited by

                  @jimp and @SteveITS

                  Thank you for taking the time to reply and try to help out.

                  I must admit this problem really has caught me by surprise.... if anything I was shaking in my boots when going to 2.7.0 and having to uninstall and reinstall all my packages... which went fairly well (just somehow the stream rules got turned back on in suricata and I had to troubleshoot that and fix but didn't take long).

                  I am thankful that the upgrade failed softly at least in that my firewall still appears to be functional (there's nothing like trying to troubleshoot your firewall/router/IDS when your, well, firewall/router/IDS is down 😬 )

                  So this looks like a tomorrow problem, that I will tackle over the holiday... I'm thinking I will just buy another pcie stick and figure out how to install pfsense again and what I need to do to format it as zfs instead of ufs.... maybe one day i will be adventurous enough to make the leap over to the plus side instead of CE side).

                  I did try to quickly search thru the forum before posting my problem... it wasn't until I did a bit more digging that it seemed to start pointing at the above issues... honestly the EFI partition thing being too small still blows me away, but if doing a clear 2.7.2 install will leave that in my read-view mirror then that will be good. I will have to do some quick research (starting with the threads you pointed to above) to see if there is any further tuning or size-setting under zfs... at least when I quickly looked at zfs items in the documentation it seems like it adds quite a bit of safety and flexibility (or is that only for pfsense +).

                  Thanks again.

                  S 2 Replies Last reply Reply Quote 0
                  • S
                    SteveITS Rebel Alliance @pfPanda
                    last edited by

                    @pfPanda said in upgrade to 2.7.2 from 2.7.0 failed-install: No space left on device:

                    somehow the stream rules got turned back on in suricata

                    I just realized that today.
                    https://forum.netgate.com/topic/185055/suricata-upgrade-install-adds-default-rulesets

                    re: EFI, I think it's one of those things where in 20 years the current 200 MB is going to be too small... well hopefully not!

                    Make a backup of course but if you reinstall see:
                    https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html

                    ZFS is the default for CE too, but CE doesn't have a web GUI for boot environments. It's more resistant to file system corruption however such as from power outages.

                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                    Upvote 👍 helpful posts!

                    N 1 Reply Last reply Reply Quote 0
                    • S
                      SteveITS Rebel Alliance @pfPanda
                      last edited by

                      @pfPanda said in upgrade to 2.7.2 from 2.7.0 failed-install: No space left on device:

                      somehow the stream rules got turned back on in suricata

                      Per https://redmine.pfsense.org/issues/15120 this is expected behavior.

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

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

                        @SteveITS I solved with this https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed/23

                        1 Reply Last reply Reply Quote 2
                        • Q QComp referenced this topic on
                        • First post
                          Last post