Update Clarity
-
Thanks all.
I tried it from command line and I get this t then just exits.
*Question* Any ideas what command I can run in the shell to pull the 2.7.2? Really not sure. For some reason I think the update has borked somewhere hence the lack of dashboard notifications.
My gui settings are
-
Run at the command line:
certctl rehash
Then try again. -
Thanks for that. In reality and from my screenshots previous what do you think has happened to cause this?. I know you don't have a crystal ball but identifying why these updates didn't register / notify would be good the know.
-
@zoqask Well per the link I posted above, "Due to changes in pkg, the new version of pkg may not be able to properly locate and use the CA trust store when running on the previous version before upgrading." A lot of (all) people had to run that command to be able to update.
-
Ok understood. I will try it out of hours and see if it gets a result.
Thanks in advance to both of you if t does
.If it doesn't work I will post a screenshot. Hopefully if this is a common issue indeed its tried / tested and a recurring theme is the past (As you say). Having had others wipe the sweat from their brow hopefully I can as well.
-
Yup it was a known bug in 2.7.0. It's fixed in 2.7.2 forward.
-
Ran certctl rehash
I now get update request. So its a case of waiting for the right time out of hours now and trying it out.
Out of interest, when you progress in the command line and is says saving old kernel etc. If the install fails for some reason how do you revert back to the previous version. This may be an incredibly overly simplified question but some sort of command line fu would be helpful for those of us that aren't clocking into these appliances every day.
-
You can choose to boot the old kernel at the bootloader menu. But that's only the kernel, it will still fail to boot if the rest of the system is broken.
In ZFS you can create a snapshot boot environment before upgrading you can roll back to. Plus does that automatically.
-
Morning all.
Well it updated to 2.7.2 and appears to all work. Thats good.
Do I have to re run the certctl rehash for 2.8? Reason I'm asking is is the dashboard said 2.8.1 is available but running 13 console update just says all the repositories are up to date and doesn't proceed with the upgrade.
After clicking the refresh icon on the dashboard I see this. But I always use the console and don't really feel comfortable with using the gui.
Do I have to select 2.8 from the stable branch here first?
Lots of questions but this is a major jump just doing due diligence.
-
@zoqask said in Update Clarity:
Do I have to re run the certctl rehash for 2.8? Reason I'm asking is is the dashboard said 2.8.1 is available but running 13 console update just says all the repositories are up to date and doesn't proceed with the upgrade.
You don't have to run rehash again, no. But you will have select the 2.8.1 branch in the GUI, System / Update / System Update beforehand.
-
@patient0 thanks for that.
I did the update and get this message at the end.
Any idea if when I reboot the system will run? this may mean my temp files are taking up too much space. I just don't want to reboot and break the whole system for now.
-
@zoqask said in Update Clarity:
Any idea if when I reboot the system will run?
I'm not sure, no. I'd say it's as it is written, the EFI partition has not enough space to update the boot loader.
I would try what is suggested: mount the EFI partition and check for file you can delete (but not sure how to know what to delete). And search the forum for similar errors.
Maybe @stephenw10 has an idea what can be delete from the EFI partition, and how to run to boot code upgrade again.
-
@patient0 maybe Stephen has some ideas.
-
@zoqask search the forum too, pretty sure I’ve seen discussions about that. Or just reinstall which will fix that and use the ZFS file system by default.
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html
-
It will probably boot with the old loader but I haven't tested that directly on CE. It's much more of an issue in arm64.
But I would prepare to reinstall if you have to. It's unclear from that output whether it removed the old loader. It shouldn't if it can't update it.
