FreeBSD-update error after aborted update

H

HiddenWolf

Hi,

I ran freebsd-update just now on a machine running a 10.1-RC, and when faced with a huge list of to-be-changed files to scroll through, I broke it off, hitting control-c. That was apparently not something that it takes kindly to.

freebsd-update fetch && freebsd-update install now throws the following error:
Code: 
atlas# freebsd-update fetch && freebsd-update install
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching public key from update2.freebsd.org... done.
Fetching metadata signature for 10.1-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.
The following files will be removed as part of updating to 10.1-RELEASE-p2:

/

Installing updates...rmdir: ///: Is a directory
done.

I've gone through Google, cleaned out /var/db/freebsd-update/, checked /tmp/ and various other places where I suspect some sort of temporary file is stuck.
I've also rebooted the machine, but haven't found a solution.

Can someone help me out?
 
The issue is known and is being worked on. This was just posted to freebsd-announce@:
Dear FreeBSD community,

As many of you have noticed, running freebsd-update on FreeBSD 10.1
amd64 systems produces unexpected results, including reinstalling the
32-bit compatibility libraries (lib32) on systems where they are not
installed and claiming to want to remove the root directory.

When FreeBSD 10.1 was released, the lib32 component was inadvertantly
left out of the baseline used to generate freebsd-update patches. The
consequences are twofold: first, users upgrading from 10.0 to 10.1 would
lose lib32; and second, users who had either installed 10.1 from scratch
or manually reinstalled lib32 after freebsd-update removed it would not
receive patches for it.

When this issue was discovered, we were faced with two options: either
ignore it or use the next update to re-add lib32. The latter was
considered the lesser of two evils, as it was the only way to ensure
that lib32 receives security updates. An unfortunate side effect is
that freebsd-update will now recreate lib32 even on systems where it was
intentionally left out or removed.

Users who do not wish to have lib32 installed should replace "world"
with "world/base" on the "Components" line in /etc/freebsd-update.conf.

The second issue, attempting to remove '/', seems to be the consequence
of a bug in the freebsd-update build process which we do not yet fully
understand, but which results in an incorrect index for the lib32
component. We hope to be able to correct this (at the latest) when we
next publish an advisory. In the meantime, the error can safely be
ignored, as freebsd-update will not actually remove anything. Users who
have disabled lib32 in /etc/freebsd-update.conf as described above are
not affected.

DES
--
Dag-Erling Smørgrav - FreeBSD Security Officer
Click to expand...
 
Ah. That is... interesting.

I'll wait it out.
It is a nice change of pace though. Not my fault for a change! ;-)
 
The intent to remove the root directory scared me. But (after backing up) I could not resist to perform freebsd-install to see what would happen.

Now I read: (...) "the consequence of a bug in the freebsd-update build process which we do not yet fully understand". I really like that honesty. Luckily: "(...) as freebsd-update will not actually remove anything".

Accompanied with the output of uname -a and freebsd-version:
Code: 
root@pc1:/usr/home/frank # uname -a
FreeBSD pc1 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     [email]root@releng1.nyi.freebsd.org[/email]:/usr/obj/usr/src/sys/GENERIC  amd64
root@pc1:/usr/home/frank # freebsd-version
10.1-RELEASE-p2
root@pc1:/usr/home/frank # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files will be removed as part of updating to 10.1-RELEASE-p2:
/
root@pc1:/usr/home/frank # freebsd-update install
Installing updates...rmdir: ///: Is a directory
 done.
root@pc1:/usr/home/frank #
 
You must log in or register to reply here.
Back
Top