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

melik2k3

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

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/

Worked like charm :)

snagles

This solution is working in my case

@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/

foreach

Thank you @jimp
I was facing the same error while upgrading

install: //boot/efi/efi/boot/INS@rMbdew: Input/output error
netgate "pkg-static: POST-INSTALL script failed"

After running your commands, pfSense-upgrade had no issue upgrading from 23.09 to 23.09.1

BruceX

@jimp claude.ai was leading me through the same process but wanted to change to fat 16 instead of 32 because of an error message. I found this thread and asked about -F 32 -c 1 as an alternative. Claude's response: "This is a better approach than falling back to FAT16 since FAT32 is preferred for EFI systems."

Thanks!

jimp

Never trust output from LLMs. Especially not when it comes to potentially destructive modifications to your filesystem.

BruceX

@jimp it was interesting that it came up with almost the exact same solution except for the -c parameter, which suggests it didn't just copy your solution. I find AI brilliant and use it daily in my tech work.

pwnovak

@jimp Thank you very much for this. Worked flawlessly and saved me a 6 hour round trip drive!

Nikolay_Zhelev

@jimp Just wanted to thank you for this solution. My pfsense install was quite old (back from 2014) and this resolved the update issue.

Cris70

@jimp you're my savior!!
Oh my... thank you thank you thank you!!!