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

    Error during the update from 2.7.1 to 2.7.2

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    15 Posts 3 Posters 1.5k 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.
    • _
      _alex @stephenw10
      last edited by

      @stephenw10 said in Error during the update from 2.7.1 to 2.7.2:

      You have a more complete log from the upgrade? If you run it from the console and log that for example?

      Enter an option: 13

      Setting vital flag on php82... done.
      Updating repositories metadata...
      Updating pfSense-core repository catalogue...
      Fetching meta.conf: . done
      Fetching packagesite.pkg: . done
      Processing entries: . done
      pfSense-core repository update completed. 4 packages processed.
      Updating pfSense repository catalogue...
      Fetching meta.conf: . done
      Fetching packagesite.pkg: ......... done
      Processing entries: .......... done
      pfSense repository update completed. 550 packages processed.
      All repositories are up to date.

      The following 8 package(s) will be affected (of 0 checked):

      Installed packages to be UPGRADED:
      curl: 8.5.0 -> 8.6.0 [pfSense]
      pfSense: 2.7.1 -> 2.7.2 [pfSense]
      pfSense-base: 2.7.1 -> 2.7.2 [pfSense-core]
      pfSense-default-config: 2.7.1 -> 2.7.2 [pfSense]
      pfSense-kernel-pfSense: 2.7.1 -> 2.7.2 [pfSense-core]
      pfSense-repo: 2.7.1 -> 2.7.2 [pfSense]
      strongswan: 5.9.11_2 -> 5.9.11_3 [pfSense]
      unbound: 1.18.0_1 -> 1.19.1 [pfSense]

      Number of packages to be upgraded: 8

      **** WARNING ****
      Reboot will be required!!
      Proceed with upgrade? (y/N) y
      Removing vital flag from php82... done.
      Downloading upgrade packages...
      Updating pfSense-core repository catalogue...
      Fetching meta.conf:
      Fetching packagesite.pkg:
      pfSense-core repository is up to date.
      Updating pfSense repository catalogue...
      Fetching meta.conf:
      Fetching packagesite.pkg:
      pfSense repository is up to date.
      All repositories are up to date.
      Checking for upgrades (8 candidates): ........ done
      Processing candidates (8 candidates): ........ done
      Checking integrity... done (0 conflicting)
      The following 8 package(s) will be affected (of 0 checked):

      Installed packages to be UPGRADED:
      curl: 8.5.0 -> 8.6.0 [pfSense]
      pfSense: 2.7.1 -> 2.7.2 [pfSense]
      pfSense-base: 2.7.1 -> 2.7.2 [pfSense-core]
      pfSense-default-config: 2.7.1 -> 2.7.2 [pfSense]
      pfSense-kernel-pfSense: 2.7.1 -> 2.7.2 [pfSense-core]
      pfSense-repo: 2.7.1 -> 2.7.2 [pfSense]
      strongswan: 5.9.11_2 -> 5.9.11_3 [pfSense]
      unbound: 1.18.0_1 -> 1.19.1 [pfSense]

      Number of packages to be upgraded: 8
      Downloading pkg...

      No packages are required to be fetched.
      Integrity check was successful.
      Upgrading pfSense-boot... Unmounting /boot/efi... done.
      failed.

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

        Hmm, not seeing the error you initially posted there. What was different?

        If there's something unusual about that install though I'd be tempted to just install 2.7.2 clean and restore the config.

        Steve

        1 Reply Last reply Reply Quote 1
        • _
          _alex @stephenw10
          last edited by stephenw10

          @stephenw10 said in Error during the update from 2.7.1 to 2.7.2:

          You have a more complete log from the upgrade? If you run it from the console and log that for example?

          [2.7.1-RELEASE][admin@pfSense]/root: df -hi /boot/efi/efi/boot/
          Filesystem            Size    Used   Avail Capacity iused ifree %iused  Mounted on
          zroot/ROOT/default    809G    1.1G    808G     0%     48k  1.7G    0%   /
          [2.7.1-RELEASE][admin@pfSense]/root:
          
          1 Reply Last reply Reply Quote 0
          • S
            slu @_alex
            last edited by slu

            @_alex
            https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed?_=1713473952714

            pfSense Gold subscription

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

              Ah OK. So try the full output of: gpart list

              Perhaps one of the drives in the mirror has an efo partition that's too small.

              Is this the same install you referenced in that thread? I don't see any mention of a mirror there.

              _ 1 Reply Last reply Reply Quote 1
              • _
                _alex @stephenw10
                last edited by

                @stephenw10

                [2.7.1-RELEASE][admin@pfSense]/root: gpart list
                Geom name: ada0
                modified: false
                state: OK
                fwheads: 16
                fwsectors: 63
                last: 1953525127
                first: 40
                entries: 128
                scheme: GPT
                Providers:

                1. Name: ada0p1
                  Mediasize: 209715200 (200M)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r1w1e2
                  efimedia: HD(1,GPT,96fdba21-f4f5-11ea-95ee-503eaa11083a,0x28,0x64000)
                  rawuuid: 96fdba21-f4f5-11ea-95ee-503eaa11083a
                  rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
                  label: efiboot0
                  length: 209715200
                  offset: 20480
                  type: efi
                  index: 1
                  end: 409639
                  start: 40
                2. Name: ada0p2
                  Mediasize: 524288 (512K)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r0w0e0
                  efimedia: HD(2,GPT,97249595-f4f5-11ea-95ee-503eaa11083a,0x64028,0x400)
                  rawuuid: 97249595-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
                  label: gptboot0
                  length: 524288
                  offset: 209735680
                  type: freebsd-boot
                  index: 2
                  end: 410663
                  start: 409640
                3. Name: ada0p3
                  Mediasize: 2147483648 (2.0G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r1w1e0
                  efimedia: HD(3,GPT,976896a2-f4f5-11ea-95ee-503eaa11083a,0x64800,0x400000)
                  rawuuid: 976896a2-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
                  label: swap0
                  length: 2147483648
                  offset: 210763776
                  type: freebsd-swap
                  index: 3
                  end: 4605951
                  start: 411648
                4. Name: ada0p4
                  Mediasize: 997845893120 (929G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r1w1e1
                  efimedia: HD(4,GPT,97909eb8-f4f5-11ea-95ee-503eaa11083a,0x464800,0x742a2000)
                  rawuuid: 97909eb8-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
                  label: zfs0
                  length: 997845893120
                  offset: 2358247424
                  type: freebsd-zfs
                  index: 4
                  end: 1953523711
                  start: 4605952
                  Consumers:
                5. Name: ada0
                  Mediasize: 1000204886016 (932G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r3w3e6

                Geom name: ada1
                modified: false
                state: OK
                fwheads: 16
                fwsectors: 63
                last: 1953525127
                first: 40
                entries: 128
                scheme: GPT
                Providers:

                1. Name: ada1p1
                  Mediasize: 209715200 (200M)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r0w0e0
                  efimedia: HD(1,GPT,98248a2a-f4f5-11ea-95ee-503eaa11083a,0x28,0x64000)
                  rawuuid: 98248a2a-f4f5-11ea-95ee-503eaa11083a
                  rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
                  label: efiboot1
                  length: 209715200
                  offset: 20480
                  type: efi
                  index: 1
                  end: 409639
                  start: 40
                2. Name: ada1p2
                  Mediasize: 524288 (512K)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r0w0e0
                  efimedia: HD(2,GPT,984f94f1-f4f5-11ea-95ee-503eaa11083a,0x64028,0x400)
                  rawuuid: 984f94f1-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
                  label: gptboot1
                  length: 524288
                  offset: 209735680
                  type: freebsd-boot
                  index: 2
                  end: 410663
                  start: 409640
                3. Name: ada1p3
                  Mediasize: 2147483648 (2.0G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r1w1e0
                  efimedia: HD(3,GPT,98949ca2-f4f5-11ea-95ee-503eaa11083a,0x64800,0x400000)
                  rawuuid: 98949ca2-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
                  label: swap1
                  length: 2147483648
                  offset: 210763776
                  type: freebsd-swap
                  index: 3
                  end: 4605951
                  start: 411648
                4. Name: ada1p4
                  Mediasize: 997845893120 (929G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r1w1e1
                  efimedia: HD(4,GPT,98b917b8-f4f5-11ea-95ee-503eaa11083a,0x464800,0x742a2000)
                  rawuuid: 98b917b8-f4f5-11ea-95ee-503eaa11083a
                  rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
                  label: zfs1
                  length: 997845893120
                  offset: 2358247424
                  type: freebsd-zfs
                  index: 4
                  end: 1953523711
                  start: 4605952
                  Consumers:
                5. Name: ada1
                  Mediasize: 1000204886016 (932G)
                  Sectorsize: 512
                  Stripesize: 4096
                  Stripeoffset: 0
                  Mode: r2w2e3
                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Hmm, it's not mounting efiboot correctly.

                  Try running mount /boot/efi first then checking df -hi /boot/efi/efi/boot/ again.

                  Also check in /dev I expect to see the two efi partitions listed under GPT like:

                  [24.03-RC][admin@plusdev-4.stevew.lan]/dev/gpt: ls
                  efiboot0 efiboot1 gptboot0 gptboot1
                  
                  _ 2 Replies Last reply Reply Quote 1
                  • _
                    _alex @stephenw10
                    last edited by

                    @stephenw10

                    [2.7.1-RELEASE][admin@pfSense]/root: mount /boot/efi
                    mount: /boot/efi: unknown special file or file system

                    1 Reply Last reply Reply Quote 0
                    • _
                      _alex @stephenw10
                      last edited by

                      @stephenw10

                      [2.7.1-RELEASE][admin@pfSense]/root: df -hi /boot/efi/efi/boot
                      Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
                      /dev/msdosfs/EFISYS 779K 386K 393K 50% 3 509 1% /boot/efi
                      [2.7.1-RELEASE][admin@pfSense.gsrmz.su]/root:

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

                        Is that the same system? That's very different to the output you posted above.
                        That's too small to upgrade which is the same issue as in the thread you linked to. But the actual partition sizes are large enough so you might be able to fix it in place with the commands @jimp posted there.

                        _ 1 Reply Last reply Reply Quote 1
                        • _
                          _alex @stephenw10
                          last edited by

                          @stephenw10
                          @slu

                          Thanks so much, pfsense has been updated

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