Unable to upgrade from 2.7.1 to 2.7.2

[eostrike]

Hello,

Like others I am having an issue upgrading to 2.7.2. I am hoping there is a fix where I do not need to start from scratch.

Below is a few items I pulled off my unit.

---

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

---

Any assistance would be appreciated.

[jimp]

The last person who had the same issue as you ended up having multiple disks in the system and the firewall was using the EFI partition from the "wrong" disk. This could also happen if you have left the installer memstick plugged in.

If you do have multiple disks and are only intending to use one, then you should wipe the other disk as described on https://docs.netgate.com/pfsense/en/latest/troubleshooting/multiple-disks.html

[eostrike]

My setup is a Shuttle PC with a single SSD hard drive.

2.7.1-RELEASE (amd64)
built on Fri Nov 17 15:03:00 PST 2023
FreeBSD 14.0-CURRENT

Version 2.7.2 is available.
Version information updated at Tue Dec 19 13:33:02 PST 2023

---

Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
Current: 1100 MHz, Max: 2900 MHz
6 CPUs: 1 package(s) x 6 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: No

---

Mount Used Size Usage
/ 2.8G 222G
1% of 222G (ufs)

---

Memory usage
1% of 65372 MiB

---

SWAP usage
0% of 3979 MiB

[eostrike]

@jimp I only have one SSD in my Shuttle PC. That is all that fits in this mini PC.

[jimp]

Run this command from a command prompt and show what it outputs:

geom -t

[eostrike]

@jimp

[2.7.1-RELEASE][root@erico.esoindustries.com]/root: geom -t
Geom Class Provider
nda0 DISK nda0
nda0 DEV
nda0 PART nda0p1
nda0p1 DEV
nda0p1 LABEL msdosfs/EFISYS
msdosfs/EFISYS DEV
nda0 PART nda0p2
nda0p2 DEV
nda0p2 LABEL gptid/9004f6cb-76ff-11eb-a980-80ee73eba529
gptid/9004f6cb-76ff-11eb-a980-80ee73eba529 DEV
ffs.gptid/9004f6cb-76ff-11eb-a980-80ee73eba529 VFS
nda0 PART nda0p3
nda0p3 DEV
nda0p3 LABEL gptid/900562f7-76ff-11eb-a980-80ee73eba529
gptid/900562f7-76ff-11eb-a980-80ee73eba529 DEV
swap SWAP
[2.7.1-RELEASE][root@erico.esoindustries.com]/root:

[jimp]

That seems to be OK, though your df output above implies the EFI partition wasn't mounted, but the fact that it didn't throw an error makes me think maybe some files got into the wrong place.

This set of commands should clean things up and get things back to the correct layout:

# mkdir -p /tmp/efitmp
# cp -Rp /boot/efi/* /tmp/efitmp
# umount /boot/efi
# rm -rf /boot/efi
# mkdir -p /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/

[eostrike]

@jimp

You are amazing, THANK YOU so much. Every command went through below except for the unmounting. I did paste them all in and then performed the update from the console and this time it went through. I am now on 2.7.2.

The only thing below is that it does not show the boot directory. Is this anything to be concerned with. I do not believe it did prior to the upgrade either.

---

[2.7.1-RELEASE][root@erico.esoindustries.com]/root: mkdir -p /tmp/efitmp
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: cp -Rp /boot/efi/* /tmp/efitmp
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: umount /boot/efi
umount: /boot/efi: not a file system root directory
[2.7.1-RELEASE][root@erico.esoindustries.com]/root:
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: rm -rf /boot/efi
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: mkdir -p /boot/efi
[2.7.1-RELEASE][root@erico.esoindustries.com]/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=255 HiddenSecs=0 HugeSectors=409600 FATsecs=3151 RootCluster=2 FSInfo=1 Backup=2
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: mount_msdosfs /dev/msdosfs/EFISYS /boot/efi
[2.7.1-RELEASE][root@erico.esoindustries.com]/root: cp -Rp /tmp/efitmp/* /boot/efi/
[2.7.1-RELEASE][root@erico.esoindustries.com]/root:

---

[2.7.2-RELEASE][root@ericoh.esoindustries.com]/root: df -hi /boot/efi/efi/boot/
df: /boot/efi/efi/boot/: No such file or directory
[2.7.2-RELEASE][root@erico.esoindustries.com]/root:

---

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

---

[2.7.2-RELEASE][root@erico.esoindustries.com]/root: geom -t
Geom Class Provider
nda0 DISK nda0
nda0 DEV
nda0 PART nda0p1
nda0p1 DEV
nda0p1 LABEL gptid/9004b6a2-76ff-11eb-a980-80ee73eba529
gptid/9004b6a2-76ff-11eb-a980-80ee73eba529 DEV
nda0p1 LABEL msdosfs/EFISYS
msdosfs/EFISYS DEV
nda0 PART nda0p2
nda0p2 DEV
nda0p2 LABEL gptid/9004f6cb-76ff-11eb-a980-80ee73eba529
gptid/9004f6cb-76ff-11eb-a980-80ee73eba529 DEV
ffs.gptid/9004f6cb-76ff-11eb-a980-80ee73eba529 VFS
nda0 PART nda0p3
nda0p3 DEV
nda0p3 LABEL gptid/900562f7-76ff-11eb-a980-80ee73eba529
gptid/900562f7-76ff-11eb-a980-80ee73eba529 DEV
swap SWAP
[2.7.2-RELEASE][root@erico.esoindustries.com]/root:

---

[jimp]

That's probably OK, unless the EFI partition is listed in /etc/fstab it won't automatically be mounted at boot time.

Look for a line like this in /etc/fstab:

/dev/msdosfs/EFISYS       /boot/efi       msdosfs rw              2       2

or

/dev/nda0p1       /boot/efi       msdosfs rw              2       2

Or something like that. The device names for nvme drives changed from older versions so it may be nvd0p1 as well. If it is, edit it and make it nda0p1.

You could add that line if it doesn't exist but it's not a hard requirement.

[eostrike]

@jimp I really appreciate your help. Thank you!

[paq237]

@jimp

Just chiming in with another account of this particular problem and - more importantly - that this procedure worked for me to resolve it.

Firewall - 1000 miles away - is now running on 2.7.2.

Thank you!

[eostrike]

@paq237 the support from jimp was outstanding. He sure knows his stuff.

[sgroom]

I know this is an old thread but for anyone who lands here looking for a solution, jimp's instructions above worked like a charm. Thank you, Sir!

[gremblin]

Same here. Thank you @jimp