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

alethewizard

@slu

Now I think it may not be a physical appliance or virtual machine issue, but it may be due to EFI.

Probably the error is the same: please check /conf/upgrade_log.txt .

slu

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

Probably the error is the same: please check /conf/upgrade_log.txt .

You are right, exactly the same error!

stephenw10

So:

[1/1] Reinstalling pfSense-boot-23.09.1...
[1/1] Extracting pfSense-boot-23.09.1: .......... done
Updating the EFI loader
install: //boot/efi/efi/boot/INS@syoFrx: Input/output error
pkg-static: POST-INSTALL script failed

But with a different random filename?

slu

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

But with a different random filename?

If you mean the masked "123456" yes:

[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@123456: Input/output error
pkg-static: POST-INSTALL script failed
 failed.

beatvjiking

I've encountered this on a number of systems now, both on UFS and ZFS.

install: //boot/efi/efi/boot/INS@LAoX8f: No space left on device

These were set up with default partitioning done by the pfsense installer, all machines have plenty of storage and "gpart show" shows an EFI partition size of 200M, which I'm guessing is plenty.

alethewizard

@stephenw10

Yes.

jimp

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

I've encountered this on a number of systems now, both on UFS and ZFS.
install: //boot/efi/efi/boot/INS@LAoX8f: No space left on device
These were set up with default partitioning done by the pfsense installer, all machines have plenty of storage and "gpart show" shows an EFI partition size of 200M, which I'm guessing is plenty.

What does this show for you (or anyone getting similar errors):

# df -hi /boot/efi/efi/boot/

beatvjiking

@jimp output below:

[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root: df -hi /boot/efi/efi/boot/
Filesystem            Size    Used   Avail Capacity iused ifree %iused  Mounted on
zroot/ROOT/default    195G    966M    194G     0%     29k  407M    0%   /
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root:

slu

@jimp

df -hi /boot/efi/efi/boot/

Filesystem                                         Size    Used   Avail Capacity iused ifree %iused  Mounted on
/dev/gptid/123456                                  111G    2.4G    100G     2%     49k   15M    0%   /

jimp

Either those are not EFI systems or the EFI partition isn't mounted since it's showing the root slice there.

Try running mount /boot/efi before the df command.

# sysctl machdep.bootmethod
# mount /boot/efi
# df -hi /boot/efi/efi/boot/

beatvjiking

@jimp access to the efi partition seems blocked.

[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root: sysctl machdep.bootmethod
machdep.bootmethod: UEFI
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root: mount /boot/efi
mount: /boot/efi: unknown special file or file system
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root:

jimp

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

@jimp access to the efi partition seems blocked.

[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root: sysctl machdep.bootmethod
machdep.bootmethod: UEFI
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root: mount /boot/efi
mount: /boot/efi: unknown special file or file system
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/root:

Do you have either /dev/msdosfs/EFISYS or /dev/gpt/EFISYS? If so, try this instead:

# mount_msdosfs /dev/msdosfs/EFISYS /boot/efi

Or

# mount_msdosfs /dev/gpt/EFISYS /boot/efi

Followed by the df -hi /boot/efi/efi/boot/ command.

beatvjiking

@jimp that seems to have done the trick:

[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/dev: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/dev: df -hi /boot/efi/efi/boot/
Filesystem             Size    Used   Avail Capacity iused ifree %iused  Mounted on
/dev/msdosfs/EFISYS    780K    387K    393K    50%       3   509    1%   /boot/efi
[2.7.0-RELEASE][admin@pvd-dhall-1.cic.com]/dev:

seems a bit... cramped?

alethewizard

@jimp

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

jimp

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

There probably isn't going to be a safe way to upgrade those in-place given the space constraint there. You're better off reinstalling.

But with the config recovery in the installer that should only take a few minutes to do in most cases.

alethewizard

@jimp

Thank you.

My EFI partition is 200M.

Could I resize the /dev/msdosfs/EFISYS to be more than 800K?

jimp

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

@jimp

Thank you.

My EFI partition is 200M.

Could I resize the /dev/msdosfs/EFISYS to be more than 800K?

We looked into doing that in an automated manner at one time, but deemed it too dangerous. While technically possible you'd spend more time doing that and possibly messing it up than you would just reinstalling and recovering the configuration.

Once upon a time the FreeBSD EFI update method involved writing out a FAT filesystem image onto the partition rather than mounting and copying files, and that image was very small since it didn't need to be much larger than the loader itself. That was ... less than ideal for a number of reasons. But it's hard to break out of that in a safe manner.

beatvjiking

@jimp this install is from last year - I'd done a fresh install of 2.6 onto it to get ZFS in place. I have other machines on identical hardware and circumstances that aren't seeing the issue - is there some kind of weird corner case I hit? Maybe a workaround? The reinstalls are easy to do only if one can get to the machines.

alethewizard

@jimp

Thank you jimp!

Simply extraordinary! :)

You're right: with the config recovery in the installer in 3 minutes I have the VM again with new version 2.7.2.

Thank you very much!

jimp

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.