Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.
-
@jimp I'll do my best Col. Klink impersonation. I see nothing! I know nothing!
Also, thanks for showing us that nothing. Might be less than elegant, and certainly risky... but, it means I don't need to physically move the system to a monitor to rebuild it completely. What's the point of working in software if we can't be a bit lazy now and then?
-
This worked for me, thank you for the help.
-
@jimp Logged in just to say thank you for posting this. It worked for me!
I appreciate your help!
-
@jimp Logged in just to say thank you for posting this. It worked for me!
I appreciate your help!
-
My /boot/efi partition was 779K.
Then I ran the commands that @jimp provided and now it's 197M!
After that,
pfSense-upgradehad no issue upgrading from 2.7.1 to 2.7.2!
Thank you so much! -
-
@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 -
@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! -
never saw this post! but it's working!
-
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!
-
@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/efiAfter :
[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/efiUp to date in 2.7.2 now !
Have a nice sunday!
-
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:
-
@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. -
@jimp thanks :) I have a pfSense box about 6,000 miles away, I owe you a beer!
-
@jimp You are a star. Thank you
-
S SteveITS referenced this topic on
-
I iorx referenced this topic on
-
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 -
Best option is reinstall.
If you're unable to do that then follow jimp's instructions here: https://forum.netgate.com/post/1140955 -
@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.
-
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 -
@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.
