What happened to Boot Environments during Package installation (Part – 1)

In this post I am going to explain the procedure to install the packages with consideration of BE.  In Solaris 11.1 BE is listed with help of beadm command instead of lu command.

Step 1 : Checking the current BE of server.  It is having only one BE currently. Checked the same thing in zone as well. Yes it is possible in Solaris 11.1

root@solaris11:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris NR / 9.93G static 2014-05-05 17:17

root@solaris11:~# zlogin testzone1
[Connected to zone ‘testzone1’ pts/3]
Oracle Corporation SunOS 5.11 11.1 September 2012

root@testzone1:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris NR / 517.80M static 2014-06-14 21:09

Step 2 : Now create the new BE during the installation of package. I have given the BE name solaris-newbe1 during installation of package now it will create the new BE.

root@solaris11:~# pkg install –be-name solaris-newbe1 diffstat
Packages to install: 1
Create boot environment: Yes
Create backup boot environment: No

Planning linked: 0/2 done; 1 working: zone:testzone2
Planning linked: 1/2 done; 1 working: zone:testzone1
Planning linked: 2/2 done
DOWNLOAD PKGS FILES XFER (MB) SPEED
Completed 1/1 6/6 0.0/0.0 0B/s

Downloading linked: 0/2 done; 1 working: zone:testzone2
Downloading linked: 1/2 done; 1 working: zone:testzone1
Downloading linked: 2/2 done
PHASE ITEMS
Installing new actions 24/24
Updating package state database Done
Updating image state Done
Creating fast lookup database Done
Executing linked: 0/2 done; 1 working: zone:testzone2
Executing linked: 1/2 done; 1 working: zone:testzone1
Executing linked: 2/2 done

A clone of solaris exists and has been updated and activated.
On the next boot the Boot Environment solaris-newbe1 will be
mounted on ‘/’. Reboot when ready to switch to this updated BE.

Step 3  : After installation of package we can verify the new BE using beadm command. Do the same check in non-global zone as well.

root@solaris11:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris N / 29.28M static 2014-05-05 17:17
solaris-newbe1 R – 10.00G static 2014-06-16 18:05

root@testzone1:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris NR / 2.20M static 2014-06-14 21:09
solaris-1 !R – 13.96M static 2014-06-16 18:05

Step 4 : Now verification part, check whether the package is installed in current environment no it isn’t. This is expected. 

root@solaris11:~# pkg list diffstat
pkg list: no packages matching ‘diffstat’ installed

  • Verification can be done in two ways either mounting the ABE on mount point and issue the below command.

root@solaris11:~# beadm mount solaris-newbe1 /mnt

root@solaris11:~# pkg -R /mnt list diffstat
NAME (PUBLISHER) VERSION IFO
text/diffstat 1.51-0.175.1.0.0.9.0 i–

  • Perform the reboot of server so when the server will boot from new BE.

root@solaris11:~# init 6

root@solaris11:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris – – 32.12M static 2014-05-05 17:17
solaris-newbe1 NR / 10.06G static 2014-06-16 18:05

root@solaris11:~# pkg list diffstat
NAME (PUBLISHER) VERSION IFO
text/diffstat 1.51-0.175.1.0.0.9.0 i–

What happened to non-global zone environment. It’s BE also changed.

root@testzone1:~# beadm list
BE Active Mountpoint Space Policy Created
— —— ———- —– —— ——-
solaris !R – 2.90M static 2014-06-14 21:09
solaris-1 NR / 35.25M static 2014-06-16 18:05

Advertisements

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