Solved Problems upgrading from 9.2 to 9.3

[Crotalus]

I have a problem upgrading from 9.2 to 9.3. I get the famous "The update metadata is correctly signed, but failed an integrity check."

First the environment.

Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.2-RELEASE-p10 #0: Tue Jul  8 10:48:24 UTC 2014
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: AMD FX(tm)-4130 Quad-Core Processor             (3817.47-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x600f12  Family = 0x15  Model = 0x1  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x1e98220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x1c9bfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,NodeId,Topology,<b23>,<b24>>
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8186376192 (7807 MB)

Here is the upgrade output

root@Phaedra:/ # freebsd-update -r 9.3-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update4.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.3-RELEASE from update4.freebsd.org... done.
Fetching metadata index... done.

The update metadata is correctly signed, but
failed an integrity check.
Cowardly refusing to proceed any further.
root@Phaedra:/ #

I then ran the "fetch".

root@Phaedra:/ # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files will be updated as part of updating to 9.2-RELEASE-p11:
/boot/kernel/linker.hints
root@Phaedra:/ #

The next step was to install the updates.

root@Phaedra:/ # freebsd-update install
Installing updates... done.
root@Phaedra:/ #

I restarted just for a possible need to do so.

root@Phaedra:/ # shutdown -r now
Shutdown NOW!
shutdown: [pid 16312]
root@Phaedra:/ #                                                                                
*** FINAL System shutdown message from Keith@Phaedra.group1 ***              

System going down IMMEDIATELY                                                  
                                                                          
System shutdown time has arrived

I then ran the fix that I found on the forum.

root@Phaedra:/  # sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update

I got the same "The update metadata is correctly signed, but failed an integrity check."
So I tried this to see what it would produce.

root@Phaedra:/ # freebsd-update -r 9.3-RELEASE IDS
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 9.2-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
/boot/kernel/linker.hints has SHA256 hash acb18b41571bf97e13f33ab5a4059b475b4e63e18a6b4af76f8458abf407b225, but should have SHA256 hash 1027485d3bbea91931b1289c751d8530c33b67f562376237d39085133096bcfd.
/boot/kernel/linker.hints has SHA256 hash acb18b41571bf97e13f33ab5a4059b475b4e63e18a6b4af76f8458abf407b225, but should have SHA256 hash d2196e2046b1aa6d4b0e10d5d521d6cad0ab1daa814f6b6f80dd110df2aebcca.
/etc/crontab has SHA256 hash dd879d90236deb86593b804d484506eb4fef3be204768294bdfe8d289f7b48fe, but should have SHA256 hash da4b2db5e7b40015da2b162a238b6a588766e988111ef9f43d7ecae4a04c9436.
/etc/group has SHA256 hash a5968c52207a40b29d2d289d7b2d50e42ca768e686169c344b48f4d02616aeb5, but should have SHA256 hash d032cd84a01f2a547b7ce887207faddf621d1807d34d3321a1ca03e06b1060ce.
/etc/hosts has SHA256 hash b7e353cfa5eeb0a1b619ff6a2bf23b5482fc679fa17cd6f22bf4f14d97fc1ecf, but should have SHA256 hash 16121f6747fc03164e10c0eb13ae1bf39aa36aa6964e91deff621d837f720ba0.
/etc/inetd.conf has SHA256 hash c4ad398de634b0d81ff87dc7d87a674c3cc40086e8f27cb1ca6fe01353b9ee9b, but should have SHA256 hash 235195ebd4b1f37ecffa6a1f5e525fd3069397a0d36808ccb7f518ee212dc61b.
/etc/master.passwd has SHA256 hash 76cf075a4673e32be7395e49231973f052f8c50746869356f6a8bad726f375ae, but should have SHA256 hash 2dd6f42a5f68bc5db243112a29f0e7998dbe871383bb4e3e784e835ff4f22b97.
/etc/motd has SHA256 hash 54fe56f285f46d45c9ae08f4a81f1e724fec7123da79f020e6a35e0a7978c0c3, but should have SHA256 hash 98f082efc89da5e887e72bc4dcfa3e5fc8bada9d19db4bdbba9a32692a7c82a7.
/etc/passwd has SHA256 hash be079153f24e4d192cba4f4592f3eb38a5b6d0fda0da084e528d229ca8cb5ebc, but should have SHA256 hash e8dd2d43e7d35b3f34ff5d548a90c995a956e8e90a48f25d6c312f2965525cb6.
/etc/pwd.db has SHA256 hash 69883c10c6a9038e9d99b891cb9f8cb980ad11dcf1d6ce126841e170b42eec51, but should have SHA256 hash 10265dfafadd1b05598c1d5cec16a9fb42475e9061f78e36ee13eda50f2a2fb9.
/etc/shells has SHA256 hash c0095202c892a2e2567119fb0e9fc0fd645168c2c29bbd0c2f4b59d778983c38, but should have SHA256 hash 626fc9747917e91abe381e8389ca9328a0ef5c334caedc683433d59780e4372a.
/etc/spwd.db has SHA256 hash 4ae3d6698312a406b022203068014e2e72d4271e1ac7bf4905fe1fffcea12bf8, but should have SHA256 hash 0811d890eceaf7733987ca695ef429bfae5d864edcbeb69abf8c04c4ddefc2fb.
/sbin/nologin is a regular file, but should be a symlink.
/var/cache has 0755 permissions, but should have 0750 permissions.
root@Phaedra:/ #

I also booted into single user mode and ran root@Phaedra:/ # fsck /
I reran the above sequence again and received the same results on the upgrade.

Can anybody out there tell me what I am doing wrong and how to fix the problem so the upgrade will work.

Keith

 

[SirDice]

I'm not sure if it'll work but try removing everything in /var/db/freebsd-update/. Then try to fetch the files again. It may just have been corrupted somewhere.

 

[Crotalus]

I deleted everything in /var/db/freebsd-update and got the same results running the upgrade.

root@Phaedra:/var/db/freebsd-update # ls -l
total 0
root@Phaedra:/var/db/freebsd-update #

This is what the upgrade attempt put in the directory.

root@Phaedra:/var/db/freebsd-update # ls -l
total 8976
-rw-r--r--  1 root  wheel      225 Sep  9 01:50 588968597d0dc89a49355a01cd327c53ac40b3968cf03d966b802e63f243d0c3
-rw-r--r--  1 root  wheel  9103148 Sep 12 07:43 INDEX-OLD
-rw-r--r--  1 root  wheel      130 Sep 12 07:43 filelist
drwxr-xr-x  2 root  wheel      512 Sep 12 07:43 files
-rw-r--r--  1 root  wheel      130 Sep 12 07:43 patchlist
-rw-r--r--  1 root  wheel      800 Sep  9 01:50 pub.ssl
-rw-r--r--  1 root  wheel      124 Sep 12 07:43 serverlist
-rw-r--r--  1 root  wheel      124 Sep 12 07:43 serverlist_full
-rw-r--r--  1 root  wheel       25 Sep 12 07:43 serverlist_tried
-rw-r--r--  1 root  wheel      150 Sep 12 07:43 tINDEX.new
-rw-r--r--  1 root  wheel      150 Sep 12 07:43 tINDEX.present
-rw-r--r--  1 root  wheel      112 Sep 12 07:43 tag
-rw-r--r--  1 root  wheel      111 Sep 12 07:43 tag.new
root@Phaedra:/var/db/freebsd-update #

root@Phaedra:/var/db/freebsd-update # ls -l files
total 6284
-rw-r--r--  1 root  wheel  3205629 Sep 12 07:43 1a333b15bbb9ecd6846722cc5c8fefdd2c49a9bb10af1d21730aab1b162a6002.gz
-rw-r--r--  1 root  wheel     9765 Sep 12 07:43 568e57881ba5c4221af0ad4c6421ddf644dd695f464f04682c730bdb6b173a57.gz
-rw-r--r--  1 root  wheel  3114669 Sep 12 07:43 a6f6862ab05f6696451d327fe693aef0f5e4da167faf2935d1453f08130b1ff4.gz
root@Phaedra:/var/db/freebsd-update #

The INDEX-OLD has thousands of file with this being an example.

/usr/bin/tset|f|0|0|0555|0|3d923831af3c3505ec10a43099ca4c1d890bbbcb6f95734c6654cc0c6ae5d653|/usr/bin/reset
/usr/bin/tsort|f|0|0|0555|0|9678ac9700a4f3a3b10ae7d311ec44f1dbabaaa464d8428c694ff1ee0d302e4e|
/usr/bin/tty|f|0|0|0555|0|1692b18fbc1880d75edcd266d39a7cadfec0654f2e57324cab0c7dc628c07ca3|

Is there anything else I can do short of installing ver 9.3 and loading all of the applications? I can live with 9.2 if needs be.

Thanks!

Keith

 

[Crotalus]

I found the problem and was able to upgrade the system to version 9.3.

Some time ago I had a problem with the system hard drive and after running fsck I had to restore some files. This was when I was using version 9.1. I put them in /sbin by mistake instead of /usr/sbin. After this everything worked again without any problems for my version 9.1.

I ran freebsd-update -r 9.2-RELEASE upgrade without any problems. When the upgrade was completed the new files in /usr/sbin was updated and it left the files in /sbin intact. I located the old files by the date of the restore and deleted all of them from /sbin. I had two different versions of freebsd-upgrade and after all the old files were deleted I ran freebsd-update -r 9.3-RELEASE upgrade and every thing worked.

What was interesting I could upgrade to any of the 9.2 versions on the FreeBSD site and was not able to upgrade to version 9.3 after the change to any of the 9.2 versions.

There is joy in Mudville again.