I think all common cases have been considered here: https://forums.freebsd.org/threads/update-of-the-bootcodes-for-a-gpt-scheme-x64-architecture.80163/
Could you please explain about this further, on what to do, in case of EFI?
What I find here is a change from directory to file.I had file and directory inconsistencies when I ranfreebsd-update IDS
.
This change does not handle the directory -> file case and further work is needed.
I had file and directory inconsistencies when I ranfreebsd-update IDS
. …
… a change from directory to file.
… 10 to 11 hours for freebsd-update upgrade / install / reboot / install. …
freebsd-update upgrade / install
Updating the bootcode is needed for ZFS systems only? or all upgrades from v13 to v14? And/or, only if using freebsd-update vs from source?Mount the partition (if it's not mounted already)
mount -t msdosfs /dev/ada0p1 /boot/efi
(Use the correct disk and partition for your system; look atgpart show
)
cp /boot/loader.efi /boot/efi/EFI/BOOT/Bootx64.efi
The 'target' directory and filename (EFI/BOOT/BOOTx64.efi) is on a FAT filesystem, FAT isn't case sensitive, so the exact case may be different on your system, case doesn't matter. Certain installations may also have created a EFI/FreeBSD/loader.efi, copy /boot/loader.efi to that too, just for good measure.
Some older installations may have a created a buggy FAT partition. You could get an error saying loader.efi doesn't fit even though the filesystem appears to be large enough. Then you may need to newfs_msdos(8) it first.
Yes. Due to a newer version of OpenZFS. If you have a system booting from UFS, then you don't need to update the bootcode.Updating the bootcode is needed for ZFS systems only?
From 12 to 13 and 13 to 14. So also from 12 to 14.or all upgrades from v13 to v14?
Both ways will get you a new ZFS version, so how you upgrade is irrelevant. Note that you only need to upgrade the bootcode IF you upgrade your boot zpool. If you don't upgrade the pool then the old bootcode will continue to work. So I recommend just finishing the FreeBSD version upgrade first and only if everything works should you upgrade the zpool (and the bootcode).And/or, only if using freebsd-update vs from source?
freebsd-update install
one more time, because it needs shared object libraries. If ports-mgmt/pkg is not installed, you'll get an error trying to run pkg, saying, "libsssl.so.111" not found, required by pkg. portsnap
is no longer in base. So, I'll have to resort to git
in base, then build pkg.Portsnap is still available, as a port/package, but yes, not included in the base anymore. No git in base either. Probably a good idea to keep a copy of the pkg package, and git-tiny perhaps?I'm without pkg and I've heard portsnap is no longer in base. So, I'll have to resort to git in base, then build pkg.
I thought git or some git using program replaced portsnap in base for installing/upgrading ports-tree.No git in base either
pkg bootstrap -f
seemed to fix my problem. I went into my outdated ports directory to attempt to rebuild pkg, and it gave me this message. portsnap fetch update -I
.Updating the bootcode is needed for ZFS systems only?
I thought git or some git using program replaced portsnap in base. …
freebsd-update install
again.. It was running without issues for a while but after some time it started throwing lots of 'File doesn't exist' errors mostly related to some man pages files. Then I rebooted the server again - it came back.. And.. Now I'm getting:
> sudo su -
ld-elf.so.1: Shared object "libintl.so.8" not found, required by "sudo"
su
command.. ;-) I know it's embarrassing.. Prepare a 14-RELEASE installation tool to reset the root passwordHi folks,
Sorry, I'm not 100% if this is related but I think that I ran into similar issue when upgrading from 13.2-RELEASE to 14-RELEASE yesterday
I've fetched all updates first. Then rebooted and ranfreebsd-update install
again.. It was running without issues for a while but after some time it started throwing lots of 'File doesn't exist' errors mostly related to some man pages files. Then I rebooted the server again - it came back.. And.. Now I'm getting:
> sudo su -
ld-elf.so.1: Shared object "libintl.so.8" not found, required by "sudo"
Now - this is the best part.. (and I know - it's stupid..) - I forgot root password.. And I cannot switch to root withsu
command.. ;-) I know it's embarrassing..
Can I ask if someone would have any suggestions on how I could fix this..?
Now - this is the best part.. (and I know - it's stupid..) - I forgot root password.. And I cannot switch to root withsu
command.. ;-) I know it's embarrassing..
Can I ask if someone would have any suggestions on how I could fix this..?
Will try Thank youPrepare a 14-RELEASE installation tool to reset the root password
ld-elf.so.1: Shared object "libintl.so.8" not found, required by "sudo"
% pkg provides libintl.so.8
Name : gettext-runtime-0.22.3
Comment : GNU gettext runtime libraries and programs
Repo : FreeBSD
Filename: usr/local/lib/libintl.so.8.4.0
usr/local/lib/libintl.so.8
Name : gettext-runtime-0.22.3
Comment : GNU gettext runtime libraries and programs
Repo : poudriere
Filename: usr/local/lib/libintl.so.8.4.0
usr/local/lib/libintl.so.8
% pkg query %o gettext-runtime
devel/gettext-runtime
%
13.2-RELEASE (which was already at latest) to 14.0-RELEASE on ZFS. I have NOT yet upgraded the zpool. This is on a Thinkpad T430p that has served me well.Was that condensed writing, or did you omit the minor update before the major upgrade?
13.2-RELEASE (which was already at latest) to 14.0-RELEASE on ZFS. …