Unstable update 2018-01-30 problems


#21

Hello Rod,

This is post 21 in thread. Please see post 18 for all my update attempt details.

-Ben


#22

did you successfully get it to run?

did you run --> sudo pc-updatemanger startupdate

edit:

type beadm list <---------> and post output here


#23

beadm list output is in post 18 above.

I will run the CLI command tomorrow and let you know if it resolved the issue.

Thank you
-Ben


#24

type

sudo beadm activate 12.0-CURRENT-up-20171018_170852

sudo reboot

that should put you on the previous BE


#25

Yes but … from post 19…

I will try running the “sudo pc-updatemanger startupdate” on the command line and see what happens. I saw this in the log but for some reason assumed TrueOS would run it on it’s own.

-Ben


#26

not if you disable it


#27

So I click the Apply Updates button and …


#28

clicking button should start the upgrade process


#29

Ok… so after that above reboot… no new BE is available. Just same ole…

[user@BFOREST-VM] ~> beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            3.4G 2017-02-03 16:07
12.0-CURRENT-up-20171018_170852 -      -            5.6G 2017-10-18 21:07
12.0-CURRENT-up-20171214_150305 NR     /           18.3G 2017-12-14 14:55

[user@BFOREST-VM] ~> tail -n 5 /var/log/pc-updatemanager.log
Verifying / fetching packages for FreeBSD Base
-----------------------------------------------
Your update is staged and ready to install.
To reboot and begin the update run # pc-updatemanager startupdate
Creating stage BE...

[user@BFOREST-VM] ~> sudo pc-updatemanager startupdate
No update staged. Please run /usr/local/bin/pc-updatemanager pkgupdate first
[user@BFOREST-VM] ~>

Should I do the pkgupdate? (I thought this was what I was doing when I clicked the button to apply updates.)


#30

rollback to the previous BE.

open a terminal and type

sudo beadm activate 12.0-CURRENT-up-20171018_170852

like I mentioned last night, again in the terminal and type

beadm list

this should show R behind the middle BE. If so type

sudo reboot now

once rebooted open a terminal and type

sudo pc-updatemanager pkgcheck && sudo pc-updatemanager pkgudate && sudo pc-updatemanager startupdate


#31

well… I followed the instructions in the Log as shown above… in fact here is the end of my history file: (beginning with the beadm list from above.)

|195|19:36|beadm list|
|---|---|---|
|   196|19:37|tail -n 5 /var/log/pc-updatemanager.log|
|   197|19:37|sudo pc-updatemanager startupdate|
|   198|19:47|sudo /usr/local/bin/pc-updatemanager pkgupdate|
|   199|19:49|sudo pc-updatemanager startupdate|
|   200|19:49|exit|

Reboot happened here. Then after I got back to my desktop:

[user@BFOREST-VM] ~> beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            3.4G 2017-02-03 16:07
12.0-CURRENT-up-20171018_170852 -      -            5.6G 2017-10-18 21:07
12.0-CURRENT-up-20171214_150305 NR     /           18.3G 2017-12-14 14:55

So the update process is doing nothing. …and it has been this way for weeks with a shutdown happening each evening.

[user@BFOREST-VM] ~> uname -a
FreeBSD BFOREST-VM.work.local 12.0-CURRENT FreeBSD 12.0-CURRENT #10 d26791952(trueos-stable-17.12): Sat Dec  9 18:10:09 UTC 2017     root@chimera:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

… ok just received your previous message (#29)… I am doing that now.

[user@BFOREST-VM] ~> sudo beadm activate 12.0-CURRENT-up-20171018_170852
Password:
Activated successfully
[user@BFOREST-VM] ~> beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            3.4G 2017-02-03 16:07
12.0-CURRENT-up-20171018_170852 R      -           13.0G 2017-10-18 21:07
12.0-CURRENT-up-20171214_150305 N      /            5.6G 2017-12-14 14:55

Rebooting now…

[user@BFOREST-VM] ~> beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            3.4G 2017-02-03 16:07
12.0-CURRENT-up-20171018_170852 NR     /           13.0G 2017-10-18 21:07
12.0-CURRENT-up-20171214_150305 -      -            5.6G 2017-12-14 14:55

Running your commands now…

sudo pc-updatemanager pkgcheck && sudo pc-updatemanager pkgudate && sudo pc-updatemanager startupdate

but as I suspected… they will not run on the same line like this. …

Ok Pkgcheck is done. running pkgupdate…


#32

Please see additional notes above:

Ok… “sudo pc-updatemanager pkgupdate” requested a system reboot when it completed.

After the reboot… Beadm list shows:

[user@BFOREST-VM] ~> beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            3.4G 2017-02-03 16:07
12.0-CURRENT-up-20171018_170852 NR     /           13.0G 2017-10-18 21:07
12.0-CURRENT-up-20171214_150305 -      -            5.6G 2017-12-14 14:55

now your last command:
[user@BFOREST-VM] ~> sudo pc-updatemanager startupdate
No update staged. Please run /usr/local/bin/pc-updatemanager pkgupdate first

… Interesting…


#33

open a terminal and type;

ls -la /

and post here


#34
[user@BFOREST-VM] ~> ls -la /
total 121
drwxr-xr-x  22 root  wheel      30 Oct 18 21:07 .
drwxr-xr-x  22 root  wheel      30 Oct 18 21:07 ..
-rw-r--r--   1 root  wheel     887 Jan 21  2017 .cshrc
-rw-r--r--   1 root  wheel     177 Jan 21  2017 .profile
drwxr-xr-x   2 root  wheel       2 Feb 18  2017 .updateStage
drwxr-xr-x   3 root  wheel     512 Feb  2 20:38 autofs
drwxr-xr-x   2 root  wheel      48 Jun 23  2017 bin
drwxr-xr-x   9 root  wheel      56 Feb  2 20:07 boot
drwxr-xr-x   3 root  wheel       3 Jun  2  2017 compat
-r--r--r--   1 root  wheel    6142 Jan 21  2017 COPYRIGHT
dr-xr-xr-x  11 root  wheel     512 Feb  2 20:37 dev
drwxr-xr-x  33 root  wheel     128 Dec  5 03:35 etc
lrwxr-xr-x   1 root  wheel       9 Feb  3  2017 home -> /usr/home
-rw-r--r--   1 root  wheel    3520 Oct 18 21:07 install-pkg-list
drwxr-xr-x   4 root  wheel      59 Jun 23  2017 lib
drwxr-xr-x   4 root  wheel       6 Jun 23  2017 libexec
drwxr-xr-x   2 root  wheel       2 Nov  3 16:51 media
drwxr-xr-x   2 root  wheel       2 Jan 21  2017 mnt
drwxr-xr-x   3 root  wheel     512 Feb  2 20:38 net
drwxr-xr-x   2 root  wheel       2 Feb  3  2017 packages
-rw-r--r--   1 root  wheel   27358 Jun  2  2017 pkg-add.log
-rw-r--r--   1 root  wheel  134688 Oct 18 21:07 previous-pkg-list
dr-xr-xr-x   1 root  wheel       0 Feb  2 20:59 proc
drwxr-xr-x   2 root  wheel     151 Jun 23  2017 rescue
drwxr-xr-x  11 root  wheel      27 Dec  5 03:53 root
drwxr-xr-x   2 root  wheel     145 Jun 23  2017 sbin
lrwxr-xr-x   1 root  wheel      11 Jan 21  2017 sys -> usr/src/sys
drwxrwxrwt  13 root  wheel      25 Feb  2 20:59 tmp
drwxr-xr-x  17 root  wheel      17 Feb  3  2017 usr
drwxr-xr-x  27 root  wheel      35 Aug  7 17:18 var

Done.


#35

in a terminal type;

ls -la /.updateStage

make sure this is empty along with /tmp

then try and update again. Remember it reboots at least twice to accomplish the update


#36
[user@BFOREST-VM] ~> ls -la /.upstage
ls: /.upstage: No such file or directory

[user@BFOREST-VM] ~> ls -lha /tmp
total 29
drwxrwxrwt  13 root      wheel    25B Feb  2 21:23 .
drwxr-xr-x  22 root      wheel    30B Oct 18 21:07 ..
-rw-r--r--   1 root      wheel   3.8K Feb  2 20:56 .rebootRequired
drwxrwxrwx   2 root      wheel     3B Feb  2 20:53 .trueosflags
drwx------   2 root      wheel     2B Feb  2 20:53 .sysupdateA79hhC
drwx------   2 root      wheel     2B Feb  2 20:39 .sysupdateb4hMfj
drwx------   2 root      wheel     2B Feb  2 20:56 .sysupdateNe40yC
drwx------   2 root      wheel     2B Feb  2 20:53 .sysupdatenwCouY
drwx------   2 root      wheel     2B Feb  2 20:57 .sysupdateWGu4gq
drwx------   2 root      wheel     2B Feb  2 20:46 .sysupdatexEwBNi
. . .

Lots of files in /tmp…


#37

ls -al /.updateStage/
total 9
drwxr-xr-x 2 root wheel 2 Dec 12 13:26 .
drwxr-xr-x 22 root wheel 31 Feb 2 16:00 …


#38
[user@BFOREST-VM] ~> ls -la /.updateStage/
total 3
drwxr-xr-x   2 root  wheel   2 Feb 18  2017 .
drwxr-xr-x  22 root  wheel  30 Oct 18 21:07 ..

Not sure what to do about /tmp. Can that be deleted while I am logged in?


#39

at this point, other than a fresh install, I am without any ideas.

Going back one Boot Environment (BE) should have fixed your update problem.

The last thing I can think of

sudo pc-updatemanager pkgcheck
sudo pc-updatemanager pkgupdate -f

This forces you computer to re-download everything. If that does not work. I’m at a loss


#40

Thanks Rod! I appreciate your assistance!