Failed Update from 2.7.1 to 2.7.2
-
Hello everyone,
I have a pfSense on 2.7.1, without any issues in the past.Updating to 2.7.2 seems impossible.
From System/Update/System Update text box i got:
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: .......... done pfSense repository update completed. 550 packages processed. All repositories are up to date. >>> Removing vital flag from php82... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense repository is up to date. All repositories are up to date. Checking for upgrades (8 candidates): ........ done Processing candidates (8 candidates): ........ done Checking integrity... done (0 conflicting) The following 8 package(s) will be affected (of 0 checked): .................... 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@dMh4Gb: Input/output error pkg-static: POST-INSTALL script failed failed. Failedwhen posting here the output, i have the error that don't let me post the logs :
Post content was flagged as spam by Akismet.com
Any suggestions appreciated.
-
Probably your system has an EFI partition size that is too small for the current boot loader. You may need to reinstall. Though if the partition is big enough you might be able to grow the filesystem to fill it.
-
@stephenw10 this info is from the disks widget:
If this is the case, is there a guidance to try something from shell ?
What about UEFI vs Bios boot ? Does this has to do anything ?
-
Also on another system with 2.7.0, is not detecting any more updates to jump to 2.7.1 or 2.7.2
-
@Bambos said in Failed Update from 2.7.1 to 2.7.2:
Also on another system with 2.7.0, is not detecting any more updates to jump to 2.7.1 or 2.7.2
That came up multiple times on the forum:
https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting
-
@patient0 thanks for this direction.
i have run certctl rehash from diagnostics -> command prompt , it run, and then i perform reboot. after reboot the update still is stuck like that.
Either not detecting updates on 2.7.0, or failed to go from 2.7.1 to 2.7.2. -
@Bambos said in Failed Update from 2.7.1 to 2.7.2:
Either not detecting updates on 2.7.0, or failed to go from 2.7.1 to 2.7.2.
Which of two is it, not detecting (rehash sould fix that) or failed?
And in the troubleshooting link it states:
"This will allow pkg to utilize the system certificates until the next reboot."
So, don't reboot after running the rehash.
And there is a general troubleshoot update page:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html
-
@patient0 certctl rehash and no reboot , helped for the system that was on 2.7.0 and not detecting updates, to detect up to 2.7.2. But the behavior is the same as the systems on 2.7.1 failed to update to 2.7.2.
-
@Bambos said in Failed Update from 2.7.1 to 2.7.2:
But the behavior is the same as the systems on 2.7.1 failed to update to 2.7.2.
Then you're at the same point: you gotta reinstall. That is by far the fasted option.
The EFI partition is usually the first and you can't resize because after the EFI the os or swap partition follows.
Never tried to switch back from UEFI to BIOS. Needs different boot loader and manual intervention will be necessary.
As @stephenw10 mentioned, maybe your file system for EFI partition can be grown.
Show the EFI partition size:
df -h /boot/efireturns something like:Shell Output - df -h /boot/efi Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 260M 2.6M 257M 1% /boot/efiThen you can get size of the partition, to check if the file system size is the maxium size for the partition (it usually is):
gpart show /dev/da0Shell Output - gpart show /dev/da0 => 40 12582832 da0 GPT (6.0G) 40 532520 1 efi (260M) ...In that example the size of the partition and the file system are identical. Then you will have to reinstall.
-
@patient0 said in Failed Update from 2.7.1 to 2.7.2:
gpart show /dev/da0
Thanks for your guidance.
device 1:
device 2:
device 3:
The common on those systems is the fact that during installation (i don't know how and why yet) the filesystem selected was UFS. I don't have this specific issue with devices on ZFS.
The outputs of df and gpart show are a little different than your example. how i know with these outputs that there is a partition size issue ?
-
@Bambos said in Failed Update from 2.7.1 to 2.7.2:
The outputs of df and gpart show are a little different than your example. how i know with these outputs that there is a partition size issue ?
The EFI partition is not mounted on your systems.
You would have to temporarily mount the EFI partition. First check if there is an entry in /etc/fstab for it by running
fgrep -i efi /etc/fstab.fgrep -i efi /etc/fstab /dev/da0p1 /boot/efi msdosfs rw 2 2If it looks similar (it would be with
ada0instead ofda0) the you can just runmount -v /boot/efiand check the file system size withdf -h /boot/efi:df -h /boot/efi Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 260M 2.6M 257M 1% /boot/efi... and afterwards unmount it again with
umount -v /boot/efi.If there is no entry you can mount it to
/mnt(mount -vt msdosfs /dev/ada0p1 /mnt) and check the file system size (df -h /mnt):For me it shows:
mount -vt msdosfs /dev/da0p1 /mnt /dev/da0p1 on /mnt (msdosfs, local, writes: sync 1 async 0, reads: sync 10 async 0, fsid 7b00000032000000, vnodes: count 1 ) df -h /mnt Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 260M 2.6M 257M 1% /mntAnd also umount afterwards,
umount -v /mnt. For me it shows:umount -v /mnt /dev/da0p1: unmount from /mnt -
@patient0 said in Failed Update from 2.7.1 to 2.7.2:
fgrep -i efi /etc/fstab
Hello Sir,
it seems that there is no record for -fgrep
-
No record ?
Let me try :
SSH (or console) - as these give you full control :[26.03-RELEASE][root@pfSense.bhf.tld]/root: fgrep usage: fgrep [-abcDEFGHhIiLlmnOopqRSsUVvwxz] [-A num] [-B num] [-C num] [-e pattern] [-f file] [--binary-files=value] [--color=when] [--context=num] [--directories=action] [--label] [--line-buffered] [--null] [pattern] [file ...]So the command 'fgrep' exists.
[26.03-RELEASE][root@pfSense.bhf.tld]/root: fgrep -i efi /etc/fstab /dev/gpt/efiboot0 /boot/efi msdosfs rw 2 2I use the ZFS file system, thus 'efi' exists and gets mounted from the device "/dev/gpt/efiboot0"
edit : btw : if you still use 2.7x, don't bother upgrading with the 'click here' version.
You really want the ZFS file system, so it's time to invest in a couple of more clicks.
Changing the file system means changes partitions and all that.
This implies a full install, so time to grab an USB key, download the Negate Installer, look for a 10 minutes (average) down time period, and re install.
You've already done this ones, when you installed the initial pfSense version. Doing this will take care of any "can't upgrade" issues ^^ -
@Gertjan Hello Sir,
i didn't say fgrep doesn't exists, i meant no record returned from this command run with the shell command from diagnostics -> Command prompt.
this is in accordance with the shell, because the same command :
please note that this filesystem is UFS.
-
@Bambos
Thanks for the fb.
So ? Planned for "ZFS" and "2.8.2" ? -
@Gertjan i guess !! ZFS and 2.8.1 for now.
this is the reason i'm posting here. to understand how and why i need to keep follow the updates of the devices from now on. I have also 2.4.5-p1 devices stuck on this version. So only reinstall can be done.
I just realize that UFS file system might get this issue, all my ZFS devices went from 2.7.2 to 2.8.1 without problem.
Last , i'm not sure yet if the bios boot setup VS UEFI boot system is affecting this.
Privacy Policy · Cookie Policy