When upgrading from 11.4 to 12.3

H

hruodr

After waiting hours, I get the following:

Code: 
% freebsd-update -r 12.3-RELEASE upgrade
....
42010....42020....42030....42040....42050....42060....42070....42080....42090....42100....42110....42120....42130....42140....42150....42160....42170....42180....42190... done.
Applying patches... done.
Fetching 53552 files... gunzip: (stdin): unexpected end of file
6974668243b9fbc72f385349853a585ec196c793a11bdf30e28a3d22dcec6a0d has incorrect hash.

Any hint what to do?
 
Delete the file in /var/db/freebsd-update/files and run the upgrade again. It probably got corrupted during the download. Also check to make sure your filesystem isn't full.
 
Or you could try consecutive upgrades.
Code: 
freebsd-update -r 12.0-RELEASE upgrade
freebsd-update -r 12.1-RELEASE upgrade
freebsd-update -r 12.2-RELEASE upgrade
freebsd-update -r 12.3-RELEASE upgrade
 
I run it again, now it is fetching only 31799 files, 20000 less than before.

Terrible!

Would not be better two or three compressed tarballs?!
 
If you want to start "fresh" then delete everything in /var/db/freebsd-update (don't remove the directory itself, only its content). But then it's going to have to download everything again.
 
hruodr said:
But I think, the upgrade could be faster. ...
Click to expand...
Yeah, it's not the fastest process in the world. Even if you have a decent internet connection like mine (600Mbit/s) it's still quite slow. If you have multiple machines you need to upgrade it helps if you can set up a caching proxy. Then only the first update would be slow (it downloads the patches from upstream) but the next machine should be a lot faster (it gets the updates from the proxy's cache).
 
I want my own configuration files (/etc), how to skip the merge process when upgrading?

I do not understand its notation ("<<current version" and such).

It is terrible that one is forced to do that work in the context of upgrading
and not in calm.
 
hruodr said:
It is terrible that one is forced to do that work in the context of upgrading
and not in calm.
Click to expand...
Ehm, you are doing this in calm. The freebsd-update -r .... upgrade process doesn't change anything yet. The actual changes will be made during the freebsd-update install phases.
 
SirDice said:
Ehm, you are doing this in calm.
Click to expand...
It seems, the install did not work, because I answered somewhere, that it is not reasonable what it wrote.

No I am running the command that takes so much time for third time.

You are offered to change things, but not to leave them as they are, or to correct what one changes.

I do not like this upgrade procedure.
 
hruodr said:
This means files are only added, not deleted.
No inconsistencies created?
If it is so simple, why these update commands?
Click to expand...
Restoring /etc can be tricky when you do it manually the first time. But it's not too complicated. Thats why SirDice mentions the use of etcupdate to simplify.
 
hruodr said:
The kernel compiles reasonable time, but probably the rest is too much for my slow computer.
Click to expand...
You can build kernel and world on a faster computer then tar /usr/src and /usr/obj from the faster computer and copy it to the older computer.
Then you just untar these directories on the slower computer and run make installworld & make installkernel.
 
I am back!!!!

But now:

# uname -a
FreeBSD fbsd.local 12.3-RELEASE-p3 FreeBSD 12.3-RELEASE-p3 GENERIC amd64
Click to expand...

The first negative impression: blurr and awfull fonts in the console.

Is there a way to get the old fonts back in the console?!

I wonder how spread tastelessness is, when it comes to fonts.

It took hours to upgrade the system and the packages, almost a whole day.
And now I must recompile a lot of programs. Perhaps reinstalling is better.
I got the message:

Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run "/usr/sbin/freebsd-update install"
again to finish installing updates.
Click to expand...

But how to delete old shared objects?

The last freebsd-update install, after pkg-static upgrade -f
took also a lot of time and ended in something like an error:

% freebsd-update install
Creating snapshot of existing boot environment... done.
Installing updates...rmdir: ///var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl/man: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/openssl: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.UTF-8: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man/en.ISO8859-1: Directory not empty
rmdir: ///var/db/etcupdate/current/usr/share/man: Directory not empty
rmdir: ///usr/tests/lib/libpam: Directory not empty
done.
Click to expand...
 
While it shouldn't matter you might want to consecutive in terms of chronological order, in this case that would be 12.2 and then 12.3 .
 
hruodr said:
… how to delete old shared objects? …
Click to expand...

If you built and installed from source, is this what you want?

Code: 
root@mowa219-gjp4-8570p-freebsd:~ # cd /usr/src
root@mowa219-gjp4-8570p-freebsd:/usr/src # make -DBATCH_DELETE_OLD_FILES delete-old
>>> Removing old files (only deletes safe to delete libs)
>>> Old files removed
>>> Removing old directories
>>> Old directories removed
To remove old libraries run 'make delete-old-libs'.
root@mowa219-gjp4-8570p-freebsd:/usr/src #

Also, you might like to boot in single user mode and check the file system.
 
You must log in or register to reply here.
Back
Top