Date: Wed, 17 Dec 2025 20:13:31 -0800 From: Dan Bernstein <freebsd@dan.bernstein.name> To: Martin <iio7@protonmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: freebsd-update - just partly Message-ID: <360A5264-B5C4-4B3A-80D4-E4FC1833E37E@dan.bernstein.name> In-Reply-To: <AHGKSccrPrPBKmbF1hnppwXt9nSds4l7hRJbgybcDFg0V-9gwFfB-Sz32M_7Al2d18L8_esIiv23NsJaso2jGxu_xOw1096maxJcPHRKw2g=@protonmail.com> References: <AHGKSccrPrPBKmbF1hnppwXt9nSds4l7hRJbgybcDFg0V-9gwFfB-Sz32M_7Al2d18L8_esIiv23NsJaso2jGxu_xOw1096maxJcPHRKw2g=@protonmail.com>
index | next in thread | previous in thread | raw e-mail
I’m observing a similar issue after attempting to update an arm64 system from 14.3-RELEASE-p6 to 14.3-RELEASE-p7. I now see: $ freebsd-version -kru 14.3-RELEASE-p5 14.3-RELEASE-p5 14.3-RELEASE-p7 freebsd-update fetch reports that “No updates needed to update system to 14.3-RELEASE-p7” while “freebsd-update IDS” shows hash mismatches for the kernel itself and several other files under /boot/kernel. Inexplicably (to me), it shows multiple different expected hashes for some files, for example: /boot/kernel/kernel has SHA256 hash c20c901ec19379ce5629207c603113bdda14e75373838201eaad68f497ca8430, but should have SHA256 hash 418fb8b11c0578ff77b5004a1982d823d899b9e4f073d6a66febc2fbb14b728f. /boot/kernel/kernel has SHA256 hash c20c901ec19379ce5629207c603113bdda14e75373838201eaad68f497ca8430, but should have SHA256 hash b51253d9a93559ebc9ffdc400e7ca871ceafb3ef74fdde4e7cb02f0befe9f16c. I am not sure what’s a good way to complete the update to this system. > On Dec 17, 2025, at 2:26 PM, Martin <iio7@protonmail.com> wrote: > >> It seems you did not get the kernel update neither. >> >> Usually, this works, and I have been using it since 9.0. However, >> "freebsd-version -kru" on the non-pkgbase systems prints: >> 15.0-RELEASE >> 15.0-RELEASE >> 15.0-RELEASE-p1 >> >> Which means I did not get the kernel update, and only userland was >> updated to -p1. freebsd-update fetch did download files: >> >> [root@log /root]# freebsd-update fetch >> src component not installed, skipped >> Looking up update.FreeBSD.org mirrors... 3 mirrors found. >> Fetching public key from update2.freebsd.org... done. >> Fetching metadata signature for 15.0-RELEASE from >> update2.freebsd.org... done. >> Fetching metadata index... done. >> Fetching 2 metadata files... done. >> Inspecting system... done. >> Preparing to download files... done. >> Fetching 6 patches.... done. >> Applying patches... done. >> >> [root@log /root]# freebsd-update install >> src component not installed, skipped >> Creating snapshot of existing boot environment... done. >> Installing updates... >> Restarting sshd after upgrade >> Performing sanity check on sshd configuration. >> Stopping sshd. >> Waiting for PIDS: 73910. >> Performing sanity check on sshd configuration. >> Starting sshd. >> done. >> >> ^^ after the usual procedure I did a shutdown -r now. After that, >> "uname -a" prints "FreeBSD log 15.0-RELEASE FreeBSD 15.0-RELEASE >> releng/15.0-n280995-7aedc8de6446 GENERIC amd64" - so no kernel update. >> >> On the pkgbase system, after the reboot, "uname -a" prints "FreeBSD >> vmfreebsd 15.0-RELEASE-p1 FreeBSD 15.0-RELEASE-p1 >> releng/15.0-n280999-7bceec30b351 GENERIC amd64" >> >> I did get the kernel update on the pkgbase-system: "freebsd-version >> -kru" prints: >> 15.0-RELEASE-p1 >> 15.0-RELEASE-p1 >> 15.0-RELEASE-p1 > > This is the same situation for me on all my non-pkgbase systems! > >help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?360A5264-B5C4-4B3A-80D4-E4FC1833E37E>