System broken during upgrading from 13.4-RELEASE-p1 to 13.4-RELEASE-p2

  • Thread starter Thread starter Deleted member 52077
  • Start date Start date
D

Deleted member 52077

Guest
Hi, on a 13.4-RELEASE-p1 system I tried a patch-level update:

Code: 
# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.4-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Fetching 2 metadata files... done.
Inspecting system... done.
grep: INDEX-OLD: No such file or directory
grep: INDEX-NEW: No such file or directory
grep: INDEX-OLD: No such file or directory
grep: INDEX-NEW: No such file or directory
grep: INDEX-OLD: No such file or directory
grep: INDEX-NEW: No such file or directory
grep: INDEX-OLD: No such file or directory
grep: INDEX-NEW: No such file or directory
grep: INDEX-OLD: No such file or directory
grep: INDEX-NEW: No such file or directory
comm: INDEX-OLD: No such file or directory
sort: No such file or directory
sort: No such file or directory
Preparing to download files... done.

Then I've done a very stupid thing: I had the next command ready and hit enter for error:

Code: 
# 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: 2879.
Performing sanity check on sshd configuration.
Starting sshd.
Scanning //usr/share/certs/blacklisted for certificates...
Scanning //usr/share/certs/trusted for certificates...
Scanning //usr/local/share/certs for certificates...

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
'freebsd-update [options] install' again to finish installing updates.

The last 4 lines are suspicious for a patchlevel update

If I try to fetch updates again:

Code: 
# freebsd-update fetch
src component not installed, skipped
You have a partially completed upgrade pending
Run 'freebsd-update [options] install' first.
Run 'freebsd-update [options] fetch -F' to proceed anyway.

Install is not better:

Code: 
# freebsd-update install
src component not installed, skipped
Creating snapshot of existing boot environment... /usr/sbin/freebsd-update: freebsd-version: not found
done.
Installing updates... done.


Note that the message is correct: freebsd-version is gone from my system.

Now nothing works anymore; as an aexample:

Code: 
# freebsd-update IDS
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... ld-elf.so.1: Shared object "libnv.so.0" not found, required by "libcasper.so.1"
[: -eq: unexpected operator
ld-elf.so.1: Shared object "libnv.so.0" not found, required by "libcasper.so.1"
mirrors found.
ld-elf.so.1: Shared object "libnv.so.0" not found, required by "libcasper.so.1"
[: -eq: unexpected operator

[...] Output goes on and on..


Anybody else is seeing something like this?
 
The problem seems different from what I wrote. There was no update to install today.

Yesterday I upgraded two machines from 13.3 to 13.4.

Today, on the other machine there are no updates to install:

Code: 
# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.4-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata patches.. done.
Applying metadata patches... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.4-RELEASE-p2.

On the machine I wrote about I had the behavior shown above.
 
I suggest to delete this thread of mine since it's misleading (or useless at best).
 
I don't know.. on an up-to-date system freebsd-update fetch followed by freebsd-update install removed things like /bin/freebsd-version and many other files belonging to the OS.

On an almost identical system freebsd-update fetch correctly tells the system is up-to-date.

However I restored a working boot environment and updated again from there and everything is working now.
 
You must log in or register to reply here.
Back
Top