Error Handling: Upgrading PC-BSD 10.1-RELEASE-p27 to 10.2-RELEASE

Error Description:

So, I made use of the PC-BSD Update Manager in an attempt to upgrade my PC-BSD system (running nicely on a Dell Latitude E6420) from 10.1-RELEASE-p27 to 10.2-RELEASE.  After completing 949/950 operations, the Update Manager reported the following error:

...
[949/950] Deleting files for zip-3.0_1: ………. done
Error 2: chroot /.updateStage /.freebsd-up.sh -r 10.2-RELEASE upgrade

This resulted in an apparent hang in the Update Manager from which it would not exit (seeming to permanently report that a System Upgrade was in progress).  I Googled the matter and ran into this and then this, which seemed to indicate this is a fairly widespread problem. According to the note left by Kris Moore in the bug tracker, this issue should have been resolved 8 days ago.

Despite this assertion, it seems the issue is still present.

Resolution:

Simply fire up a terminal and execute the following command:

sudo pc-updatemanager install fbsd-10.2-RELEASE

Your system will reboot and apply many updates prior to entering the desktop environment, and when you sign in, you should notice (using the About utility) that you are now running PC-BSD version 10.2-RELEASE along with FreeBSD version 10.2-RELEASE-p4.

Presto!

Troubleshooting Process Details:

Given that I store all of my data on a central server (w00t for solid separation of responsibilities), I wasn’t too worried for the stability of my PC-BSD laptop, so upon my initial encounter of the error described above, I simply issued a reboot.

When the system came back up, I headed into the “About” utility through the KDE Kickoff menu and I saw:

PC-BSD-About

So that’s a bit of an odd version mismatch.  Furthermore, the Update Manager utility reports that the entire set of 950 operations is still in need of completion.  Simply executing the update again results in the same failure.  A reboot re-enters the loop, bringing me back to the beginning of this paragraph.

Noting Marchman’s solution, and assuming the bug to be circumvented outside of the PC-BSD Update Manager GUI, I performed the following commands:

[bitwiseoperator@workbench] ~% sudo pc-updatemanager check
Checking for FreeBSD updates...

The following updates are available:
------------------------------------
NAME: System Update to 10.2-RELEASE
TYPE: SYSTEMUPDATE
TAG: fbsd-10.2-RELEASE
VERSION: 10.2-RELEASE

To install: "pc-updatemanager install fbsd-10.2-RELEASE"



*WARNING* End of Life *WARNING*
-----------------------------------
This version of PC-BSD / TrueOS has passed its EOL date of:
Wed Aug 19 21:01:01 EDT 2015
You are strongly encouraged to upgrade your system!
-----------------------------------
[bitwiseoperator@workbench] sudo pc-updatemanager install fbsd-10.2-RELEASE
Stopping syscache...
Updating the package repo database...
Cleaning old pkg upgrade cache...
...
To install the downloaded upgrades, run "/.fbsdup install".
Installing updates...posix_memalign failed

Kernel updates have been installed.  Please reboot and run
"/.fbsdup install" again to finish installing updates.
Unmounting stage BE...
Unmounted successfully
GRUB configuration updated successfully
Renamed successfully
GRUB configuration updated successfully
Renamed successfully
GRUB configuration updated successfully
Activated successfully
Generating grub configuration file ...
Found theme: /boot/grub/themes/pcbsd/theme.txt
done
Installing GRUB to ada0
Starting syscache...
Update stage one is finished! Please reboot to start stage 2

Once you reach this point, a “System Restart Required” window appears, and you simply select “Reboot Now!”  Your system will reboot and perform ~640 additional FreeBSD updates prior to presenting the desktop manager’s sign-in screen.  When you are presented with the opportunity to sign in, do so, and check the About utility to note that you are now successfully running both PC-BSD 10.2-RELEASE and FreeBSD 10.2-RELEASE-*:

PC-BSD-About1

Advertisements
This entry was posted in Information Technology and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s