Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.

Making_sense_of_pfSense

My /boot/efi partition was 779K.

Then I ran the commands that @jimp provided and now it's 197M!

After that, pfSense-upgrade had no issue upgrading from 2.7.1 to 2.7.2!
Thank you so much!

slu

Confirm, it's working!

/dev/msdosfs/EFISYS                                197M    512B    197M     0%    /boot/efi

Thank you very much @jimp

Klaus2314

@slu same issue here, but the procedure above fixed it. thanks! I had to power cycle the device after reboot though. it did not come back after reboot. same on my SG1100.

Updating the EFI loader
install: //boot/efi/efi/boot/INS@8I5bRD: Input/output error
pkg-static: POST-INSTALL script failed

lnxfrk

@jimp said in Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.:

You never saw this post.

I'm certainly glad I saw this post. Thank you @jimp - At some point I'll plan on doing a fresh install as I'm sure that will help long term. I think the initial install for me was 2.4.5p1 so it's been a while.
Again, thanks!

romanr

never saw this post! but it's working!

t1e1

I can confirm this worked for an MBT-2200 (Minnowboard) which has not had a fresh install since at least Ver 2.4.5 (and still hasn't).

I did not have to power-cycle the unit, though after close to 20 minutes I was almost ready to either do it, or hook a monitor to it (not as easy as it sounds, or I would have done it first). I'm glad I waited and didn't crash it during the final part of the upgrade!

Thanks @jimp!

fabiensch

@jimp thanks! It worked for me too!

Before :

[2.7.1-RELEASE][root@core]/root: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE][root@core]/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

After :

[2.7.1-RELEASE][root@core]/root: mkdir -p /boot/efi
[2.7.1-RELEASE][root@core]/root: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE][root@core]/root: mkdir -p /tmp/efitmp
[2.7.1-RELEASE][root@core]/root: cp -Rp /boot/efi/* /tmp/efitmp
[2.7.1-RELEASE][root@core]/root: umount /boot/efi
[2.7.1-RELEASE][root@core]/root: newfs_msdos -F 32 -c 1 -L EFISYS /dev/msdosfs/EFISYS
/dev/msdosfs/EFISYS: 403266 sectors in 403266 FAT32 clusters (512 bytes/cluster)
BytesPerSec=512 SecPerClust=1 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=409600 FATsecs=3151 RootCluster=2 FSInfo=1 Backup=2
[2.7.1-RELEASE][root@core]/root: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE][root@core]/root: cp -Rp /tmp/efitmp/* /boot/efi/
[2.7.1-RELEASE][root@core]/root: df -hi /boot/efi/efi/boot/
Filesystem             Size    Used   Avail Capacity iused ifree %iused  Mounted on
/dev/msdosfs/EFISYS    197M    386K    197M     0%       0     0     -   /boot/efi

Up to date in 2.7.2 now !

Have a nice sunday!

jimp

I opened a Redmine so we can look into an automated way to address this since it seems to be a lot more common than expected:

https://redmine.pfsense.org/issues/15081

discy

@jimp said in Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.:

Yeah, those must be rather old installations to have an EFI partition that small. I thought we made them significantly larger several years ago.

My first use of PFSense on this device (BYOD) started in April 2020 with whatever version was stable at that time.
From that point on I have only done in-place upgrades. This is the first time I run into issues.
Not sure what is considered to be old, but this doesn't seem that old to me.
The commands from your post did fix it.

xparanoik

@jimp thanks :) I have a pfSense box about 6,000 miles away, I owe you a beer!

dsp3

@jimp You are a star. Thank you

bippus

same here:
intel appliance, installed on November 2019:

Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/msdosfs/EFISYS 780K 387K 393K 50% 3 509 1% /boot/efi

stephenw10

Best option is reinstall.
If you're unable to do that then follow jimp's instructions here: https://forum.netgate.com/post/1140955

MushyMiddle

@jimp Brilliant! Worked a treat. Thanks!

P.S. This was an old-ish UFS install, probably originally 2.6.0. Originally installed in early 2021, most likely.

iorx

@stephenw10

Hi, I posted the same problem (In the "heat of the moment" I missed to search first of course...)

Was the installation affected / changed when getting this error? Do I dare to reboot?

https://forum.netgate.com/topic/184815/failed-pfsense-boot-2-7-1-2-7-2-pfsense-core-boot-efi-efi-boot-ins-uwm1ln-input-output-error

Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-boot: 2.7.1 -> 2.7.2 [pfSense-core]

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-boot from 2.7.1 to 2.7.2...
[1/1] Extracting pfSense-boot-2.7.2: .......... done
Updating the EFI loader
install: //boot/efi/efi/boot/INS@uwM1LN: Input/output error
pkg-static: POST-INSTALL script failed
 failed.
Failed

t1e1

@iorx I remember seeing the same screen output when I first attempted the update and it failed.

I did not reboot and instead searched, found, and followed @jimp's fix above, then re-attempted the upgrade (successfully) all in the same session.

I don't think you will have problems if you reboot at this point, since the upgrade did not get beyond downloading files and I haven't seen anyone else say they had problems, or bricked their server. However, I cannot say with 100% certainty.

iorx

@t1e1

Worked awesomely! Thank you for the swift response.

If anyone curios of the event:

My EFISYS was obiously matching here.

[2.7.1-RELEASE]/: mkdir -p /boot/efi
[2.7.1-RELEASE]/: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE]/: mkdir -p /tmp/efitmp
[2.7.1-RELEASE]/: cp -Rp /boot/efi/* /tmp/efitmp
[2.7.1-RELEASE]/: ls /tmp/efitmp/efi/boot/
BOOTx64.efi startup.nsh
[2.7.1-RELEASE]/: umount /boot/efi
[2.7.1-RELEASE]/: newfs_msdos -F 32 -c 1 -L EFISYS /dev/msdosfs/EFISYS
/dev/msdosfs/EFISYS: 403266 sectors in 403266 FAT32 clusters (512 bytes/cluster)
BytesPerSec=512 SecPerClust=1 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=409600 FATsecs=3151 RootCluster=2 FSInfo=1 Backup=2
[2.7.1-RELEASE]/: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE]/: cp -Rp /tmp/efitmp/* /boot/efi/
[2.7.1-RELEASE]/: df -hi /boot/efi
Filesystem             Size    Used   Avail Capacity iused ifree %iused  Mounted on
/dev/msdosfs/EFISYS    197M    386K    197M     0%       0     0     -   /boot/efi

updated from console:

Enter an option: 13

>>> 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. 549 packages processed.
All repositories are up to date.

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

Installed packages to be UPGRADED:
        curl: 8.4.0 -> 8.5.0 [pfSense]
        isc-dhcp44-relay: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense]
        isc-dhcp44-server: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense]
        openvpn: 2.6.7_1 -> 2.6.8_1 [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]

Number of packages to be upgraded: 10

**** 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 (10 candidates): .......... done
Processing candidates (10 candidates): .......... done
Checking integrity... done (0 conflicting)
The following 10 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        curl: 8.4.0 -> 8.5.0 [pfSense]
        isc-dhcp44-relay: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense]
        isc-dhcp44-server: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense]
        openvpn: 2.6.7_1 -> 2.6.8_1 [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]

Number of packages to be upgraded: 10
>>> Downloading pkg...

No packages are required to be fetched.
Integrity check was successful.
>>> Upgrading pfSense-boot...>>> Unmounting /boot/efi... done.
 done.
>>> Upgrading pfSense kernel...
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pfSense-kernel-pfSense: 2.7.1 -> 2.7.2 [pfSense-core]

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-kernel-pfSense from 2.7.1 to 2.7.2...
[1/1] Extracting pfSense-kernel-pfSense-2.7.2: .......... done
===> Keeping a copy of current kernel in /boot/kernel.old
>>> Removing unnecessary packages... done.
System is going to be upgraded.  Rebooting in 10 seconds.

and then

*** Welcome to pfSense 2.7.2-RELEASE (amd64) on fw ***

jimp

@iorx said in Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.:

@stephenw10

Hi, I posted the same problem (In the "heat of the moment" I missed to search first of course...)

Was the installation affected / changed when getting this error? Do I dare to reboot?

FYI- No, nothing was harmed. The odd-looking filename is from the install command attempting to create a new file with the new loader contents. The way the install command is invoked here it makes a new file and then only if that succeeds does it remove the old file and then rename the new file to the old name.

This means that it only actually changes things if each step succeeds, which is the safest method. Since the creation of the new file failed, it didn't end up changing anything, so it stopped processing at that point.

mikeinnyc

I borked this upgrade badly. I was down literally for an hour. I gave up and just installed fresh and loaded my backup. All good now.

MichelH

Thanks @jimp! Increasing the EFI filesystem size fixed the issue for me as well. My version started out as a 2.4.4 version back in the days.