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

rcfa

@slu Exactly the same issue, here...

rcfa

This post is deleted!

rcfa

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

WARNING: These commands may cause unintended harm to your installation, your state of being, aura, personal wellness, sanity, favorite sports team, and/or pets. Use with caution. Have backups and installation media nearby.

If it's a VM, snapshot it before proceeding.

Assuming your EFI partition is /dev/msdosfs/EFISYS, this should work. If it's not, substitute in the proper path (e.g. /dev/gpt/EFISYS or maybe /dev/vtbd0p1 for example.)
# mkdir -p /boot/efi
# mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
# mkdir -p /tmp/efitmp
# cp -Rp /boot/efi/* /tmp/efitmp
# umount /boot/efi
# newfs_msdos -F 32 -c 1 -L EFISYS /dev/msdosfs/EFISYS
# mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
# cp -Rp /tmp/efitmp/* /boot/efi/
Afterwards you should have an EFI filesystem that is the full size of the partition, which is roughly 200M.

The upgrade should proceed after that.

If it doesn't work, roll back or reinstall. You never saw this post. That torpedo did not self-destruct. You heard it hit the hull. I was never here.

@jimp Thanks, this did the trick. Reinstalling wasn't really a viable option, as I have no physical access to the system without stepping into a plane and taking a long trip...

eostrike

This is where mine fails. Before I try the above commands I wonder if this is the same or different than with others are experiencing:

Installed packages to be REINSTALLED:
pfSense-boot-2.7.2 [pfSense-core]

Number of packages to be reinstalled: 1
[1/1] Reinstalling pfSense-boot-2.7.2...
[1/1] Extracting pfSense-boot-2.7.2: .......... done
Updating the EFI loader
install: //boot/efi/efi/boot/INS@wA0x7V: Input/output error
pkg-static: POST-INSTALL script failed
failed.

[2.7.1-RELEASE][root@erico.esoindustries.com]/root: df -hi /boot/efi/efi/boot/
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/gptid/9004f6cb-76ff-11eb-a980-80ee73eba629 222G 2.8G 201G 1% 53k 30M 0% /

[2.7.1-RELEASE][root@erico.esoindustries.com]/root: sysctl machdep.bootmethod
machdep.bootmethod: UEFI

jimp

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

This is where mine fails. Before I try the above commands I wonder if this is the same or different than with others are experiencing:

Yours is different. Start a new thread. Though it's probably an EFI partition from a second disk or installer media. Either way that belongs in a fresh thread, though.

eostrike

@jimp thank you I just started a new thread.

Sammy73

@jimp This worked for me too, thanks so much!

proger

@jimp
Thank you for this solution!
It's work for me at 2.7.0 -> 2.7.2 upgrade

conbonbur

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

@jimp

Hello.
I am coming late but I had the same problem and @jimp's solution worked perfectly.

@jimp
Thank you. Merry Christmas (late) and Happy New Year.

tumbleweedcity

@jimp Just another upvote for this fantastic stress-saving solution! Really appreciated, as your clear step by step instructions saved me literally hours of work having to re-install my pfSense+ edition from scratch via the lengthy process via the CE installer.

Massive thanks! Upgrade to 23.09.1 completed successfully following your instructions to increase the EFI partition to 200Mb. I'd buy you a coffee/beer if I could!

melik2k3

@jimp ty

noloader

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

mkdir -p /boot/efi

mount_msdosfs /dev/msdosfs/EFISYS /boot/efi

mkdir -p /tmp/efitmp

cp -Rp /boot/efi/* /tmp/efitmp

umount /boot/efi

newfs_msdos -F 32 -c 1 -L EFISYS /dev/msdosfs/EFISYS

mount_msdosfs /dev/msdosfs/EFISYS /boot/efi

cp -Rp /tmp/efitmp/* /boot/efi/

Afterwards you should have an EFI filesystem that is the full size of the partition, which is roughly 200M.

The upgrade should proceed after that.

Thank you sir!

zenon222

Worked for me too!

Bolka

@jimp I registered only to say thank you, your non-existing post helped me to save a lot of time and hassle. Failed to upgrade from 2.7.0 to 2.7.2 first, but all went smooth after using your trick. THANK YOU!

cjdias

@jimp you are lifesaver, saved me so much time avoiding a re-install!!

poochbowen

@jimp my sanity is always nebulous, but these commands did the trick for my system. thank you.

buldo

damn... @jimp a huge THANKS by me also!

Following your commands I've been able to update my customers remote firewalls without reinstall, thanks again!

musicwizard

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

WARNING: These commands may cause unintended harm to your installation, your state of being, aura, personal wellness, sanity, favorite sports team, and/or pets. Use with caution. Have backups and installation media nearby.

If it's a VM, snapshot it before proceeding.

Assuming your EFI partition is /dev/msdosfs/EFISYS, this should work. If it's not, substitute in the proper path (e.g. /dev/gpt/EFISYS or maybe /dev/vtbd0p1 for example.)
# mkdir -p /boot/efi
# mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
# mkdir -p /tmp/efitmp
# cp -Rp /boot/efi/* /tmp/efitmp
# umount /boot/efi
# newfs_msdos -F 32 -c 1 -L EFISYS /dev/msdosfs/EFISYS
# mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
# cp -Rp /tmp/efitmp/* /boot/efi/
Afterwards you should have an EFI filesystem that is the full size of the partition, which is roughly 200M.

The upgrade should proceed after that.

If it doesn't work, roll back or reinstall. You never saw this post. That torpedo did not self-destruct. You heard it hit the hull. I was never here.

I never saw this post that wasnt here. Somehow magically after reading this non-excisting post i could update from 2.7.1 to 2.7.2

olgecko00

ditto, thanks @jimp worked for me as well, very fast and painless, slick
'preciate ya!
But, it's probably a good point, I need to do a full resinstall some day, this was installed during COVID ~ Aug 2020

peterzy