Strange System Update


#1

The update manager just told me to apply the updates - the system would reboot.
After clicking update, the system got to the stage where you can take a look at the updating process via ALT-F2 but it was finished the same moment I hit ALT-F2.
The system only rebooted once and is up and running again. (I am writing this on that system.)
The update log is telling me:

pc-updatemanager: Fri Jul 20 20:17:03 CEST 2018
Boot-strapping latest PKGNG
Updating the package repo database...
Cleaning old pkg upgrade cache...
...
_endless list of already unlocked packages_
...
Running: pkg-static upgrade -U -y
Checking for upgrades (524 candidates): .......... done
Processing candidates (524 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Moving updated pkg repo...
Extracting distribution files...
**Warning: Failed extracting distribution upgrade files**
Updating OpenRC settings...
Running OpenRC Migration...
Unmounting stage BE...
Copy upgrade.log to new BE...
Running: cp /var/db/pc-updatemanager/.pkgUpdateLog /.updateStage/usr/local/log/pc-updatemanager/upgrade.log
Running: cp /var/db/pc-updatemanager/.removed-pkg-list /.updateStage/removed-pkg-list
Determine new BE name...
Cleanup mounts...

The warning doesn’t sound very promising.

The about command is showing a brand new boot environment:

===================
General information
===================

boot environment now (N) … 12.0-CURRENT-up-20180720_205037 NR 2018-07-20
       after restart (R) … 12.0-CURRENT-up-20180720_205037 NR 2018-07-20
boot loader …………………………………… BSD
            type ……………………… BIOS
CPU ………………………………………………………… Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
    number of cores ……………… 4
host ……………………………………………………… trueos-7819
memory ………………………………………………… 16384 MB available, 14954 MB free
OS git branch ……………………………………………………………………………………… trueos-stable-18.03
OS git revision ………………………………………………………………………………… fa797a5a3
OS kernel build time ………………………………………………………… Mon 2018 Mar 26 00:24:47 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… STABLE
TrueOS version …………………………… TrueOS-Desktop-201803131015

Because of the extremely rapid process and only one reboot I am in doubt this being a real update.


TrueOS on Thumb Drive Won't Boot
#2

Update Manager did the same to me today and yesterday o_O (on stable branch)
Both logs look the same:

*** snip ***
{all packages}: already unlocked
Running: pkg-static upgrade -U -y
Checking for upgrades (652 candidates): … done
Processing candidates (652 candidates): . done
Checking integrity… done (0 conflicting)
Your packages are up to date.
Moving updated pkg repo…
Extracting distribution files…
Warning: Failed extracting distribution upgrade files
Updating OpenRC settings…
Running OpenRC Migration…
Unmounting stage BE…
Copy upgrade.log to new BE…
Running: cp /var/db/pc-updatemanager/.pkgUpdateLog /.updateStage/usr/local/log/pc-updatemanager/upgrade.log
Running: cp /var/db/pc-updatemanager/.removed-pkg-list /.updateStage/removed-pkg-list
Determine new BE name…
Cleanup mounts…

Any logic explanation for this behaviour?

Any reason to keep these two new BE, shouldn’t I just roll back to the BE before those two “updates”?

/Ludensen


#3

I had the same update, I think it was only on UNSTABLE though… There was no update on my STABLE machine.

I’m just taking a shot in the dark here, but this update might be related to creating a path and getting things ready for the Trident migration to be seamless.


#4

Yes, first I thought it was an update to the Update Manager, but apparently not…?


#5

and tomorrow, the update message will no longer appear.

no idea whey it happens


#6

So it’s safe to remove the BE’s created by these “updates”?
They haven’t updated anything, right…?


#7

yes. to be safe


#8

What is mean the message in the log ?

Warning: Failed extracting distribution upgrade files

There is a same line in my lastest log.
Is it no probrem ?


#9

would not worry to much about it at this point in time


#10

Would it be safe to not rollback?


#11

personal preference. no idea “what” got updated.


#12

As long as it’s not a security threat. I’m fine with just leaving the BE as is.


#13

I see this almost every day. Even if I decide to NOT “Update and Restart” it “updates” anyway, leaving a new BE:
BE Active Mountpoint Space Created
initial - - 37.9M 2018-08-04 18:05
12.0-CURRENT-up-20180812_234014 - - 1.3M 2018-08-12 23:40
12.0-CURRENT-up-20180813_222637 - - 35.4M 2018-08-13 22:26
12.0-CURRENT-up-20180814_134545 - - 1.1M 2018-08-14 13:45
12.0-CURRENT-up-20180814_223001 - - 1.2M 2018-08-14 22:29
12.0-CURRENT-up-20180815_224526 NR / 10.0G 2018-08-15 22:45