# uname -a FreeBSD domain.com 12.1-RELEASE-p6 FreeBSD 12.1-RELEASE-p6 GENERIC i386 # freebsd-update upgrade -r 12.2-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 12.1-RELEASE from update1.freebsd.org... done. Fetching metadata index... done. The update metadata index is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. # freebsd-update upgrade -r 13.0-RELEASE Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 12.1-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. The update metadata index is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further.
(In reply to Sergey from comment #0) > # uname -a > FreeBSD domain.com 12.1-RELEASE-p6 FreeBSD 12.1-RELEASE-p6 GENERIC i386 > > # freebsd-update upgrade -r 12.2-RELEASE Maybe not directly relevant to the bug, but instructions include a fetch and install prior to the upgrade attempt: <https://www.freebsd.org/releases/12.2R/installation/#upgrade-binary> <https://bokut.in/freebsd-patch-level-table/#releng/12.1> there's patch level 13 (superior to -p6).
(In reply to Graham Perrin from comment #1) The "fetch" command also does not work --- # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 12.1-RELEASE from update1.freebsd.org... done. Fetching metadata index... done. The update metadata index is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. ---
Is this reproducible when attempting to update to 12.4 or 13.2?
*** Bug 274232 has been marked as a duplicate of this bug. ***
(In reply to Ed Maste from comment #3) I think yes, in bug #274232 12.3-RELEASE-p6 i tried to 12.4 and 13.2 and 13.0-RELEASE to 13.2 some error
*** Bug 213935 has been marked as a duplicate of this bug. ***
> Flags: maintainer-feedback?(re@⋯) Can the patch in 2016 bug 213935 comment 0 help to shape thoughts here? Is there a documentation aspect to this report? ---- On closer inspection: I see that 213935 was not specific to i386. Closure as a duplicate might have been in appropriate; sorry.
(In reply to Graham Perrin from comment #7) tried this file, but the error did not go away (upgrade -r 13.2-RELEASE the same) # ./freebsd-update.sh fetch --debug Fetching metadata signature for 13.0-RELEASE from update2.freebsd.org... latest.ssl 512 B 7231 kBps 00s done. Fetching metadata index... a6e7097fb0199003840e09495c89a04247abdd7cf3b9b1 225 B 3327 kBps 00s done. The update metadata index is correctly signed, but failed an integrity check.
https://reviews.freebsd.org/D52222 is open to add some additional diagnostic information for this case
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=af4ba95daf75cf1b1624dd57038cfaa3ed2753e7 commit af4ba95daf75cf1b1624dd57038cfaa3ed2753e7 Author: Ed Maste <emaste@FreeBSD.org> AuthorDate: 2025-08-28 16:04:06 +0000 Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2025-11-17 14:42:17 +0000 freebsd-update: Add some diagnositic information for a failure case Users report freebsd-update failing with "The update metadata index is correctly signed, but failed an integrity check." Add a hint at which of the cases is failing to help track down the issue. PR: 264205 Reviewed by: dch Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52222 usr.sbin/freebsd-update/freebsd-update.sh | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
A commit in branch stable/15 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=d653eca0ef889a8e3fa1e370d2b3ce7b031441a2 commit d653eca0ef889a8e3fa1e370d2b3ce7b031441a2 Author: Ed Maste <emaste@FreeBSD.org> AuthorDate: 2025-08-28 16:04:06 +0000 Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2025-11-20 02:48:04 +0000 freebsd-update: Add some diagnositic information for a failure case Users report freebsd-update failing with "The update metadata index is correctly signed, but failed an integrity check." Add a hint at which of the cases is failing to help track down the issue. PR: 264205 Reviewed by: dch Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52222 (cherry picked from commit af4ba95daf75cf1b1624dd57038cfaa3ed2753e7) usr.sbin/freebsd-update/freebsd-update.sh | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=b409b786b8a42b05f006dfe7c0ac70923d5fbc70 commit b409b786b8a42b05f006dfe7c0ac70923d5fbc70 Author: Ed Maste <emaste@FreeBSD.org> AuthorDate: 2025-08-28 16:04:06 +0000 Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2025-11-23 21:01:48 +0000 freebsd-update: Add some diagnositic information for a failure case Users report freebsd-update failing with "The update metadata index is correctly signed, but failed an integrity check." Add a hint at which of the cases is failing to help track down the issue. PR: 264205 Reviewed by: dch Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52222 (cherry picked from commit af4ba95daf75cf1b1624dd57038cfaa3ed2753e7) (cherry picked from commit d653eca0ef889a8e3fa1e370d2b3ce7b031441a2) usr.sbin/freebsd-update/freebsd-update.sh | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)