skip to content »

ec-clan.ru

Updating platform i86pc boot archive this may take a minute

[email protected]:/oraz1# zoneadm -z p2vsol10 install -a /oraz1/uasol10-u The following ZFS file system(s) have been created: oraz1/p2vsol10 Progress being logged to /var/log/zones/zoneadm.20140331T071607Z.p2vsol10.install Installing: This may take several minutes... ERROR: Unable to create directory /oraz1/p2vsol10/root/dev. zoneadm: zone 'p2vsol10': ERROR: installation failed: zone returning to configured state The following ZFS file systems are being removed: oraz1/p2vsol10 [email protected]:/oraz1#[email protected]:/oraz1# tail -100 /var/log/zones/zoneadm.20140331T071607Z.p2vsol10.install |more cpio: Cannot open/create .gconf/apps/panel, errno 28, No space left on device cpio: Cannot open/create .gconf/apps/panel/%gconf.xml, errno 28, No space left on device cpio: Cannot open/create .gconf/apps/panel/profiles, errno 28, No space left on device cpio: Cannot open/create .gconf/apps/panel/profiles/default, errno 28, No space left on device cpio: Cannot open/create .gconf/apps/panel/profiles/default/general, errno 28, No space left on device Hope this article will help you to make the solaris 10 physical servers as local zones on solaris 11 global zone.

updating platform i86pc boot archive this may take a minute-89

As you know that solaris 11 comes with image packaging system(IPS) and its also supports the legacy packaging system SVR4. Copy the flar image which we have created on solaris 10 physical machine to solaris 11 global zone. exit [email protected]:~# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 3 uasol10z1 running /oraz1/sol10z1/uasol10z1 solaris10 excl - uaz1 installed /export/zones/uaz1 solaris excl - uaz2 installed /export/zones/uaz2 solaris excl - p2vsol10 configured /oraz1/p2vsol10 solaris10 excl [email protected]:~#[email protected]:/oraz1# zoneadm -z p2vsol10 install -a /oraz1/uasol10-u The following ZFS file system(s) have been created: oraz1/p2vsol10 Progress being logged to /var/log/zones/zoneadm.20140331T080401Z.p2vsol10.install Installing: This may take several minutes... Postprocess: The following zones in this image will be unusable: u1 Postprocess: These zonepaths will be extracted but will not be used: Postprocess: /export/zones/u1 Postprocess: Updating the image to run within a zone Result: Installation completed successfully.# #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- title Solaris Express Developer Edition 1/08 snv_79a X86 kernel$ /platform/i86pc/kernel/$ISADIR/unix module$ /platform/i86pc/$ISADIR/boot_archive #---------------------END BOOTADM-------------------- #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- title Solaris x VM kernel$ /boot/$ISADIR/module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix module$ /platform/i86pc/$ISADIR/boot_archive #---------------------END BOOTADM-------------------- #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- title Solaris failsafe kernel /boot/platform/i86pc/kernel/unix -s module /boot/x86.miniroot-safe #---------------------END BOOTADM-------------------- title Windows rootnoverify (hd0,0) chainloader 1 ### Abhi: Linux entry added based on the windows one ### title Linux rootnoverify (hd0,3) chainloader 1 # Unknown partition of type 15 found on /dev/rdsk/c0d0p0 partition: 3 # It maps to the GRUB device: (hd0,2) .# Unknown partition of type 131 found on /dev/rdsk/c0d0p0 partition: 4 # It maps to the GRUB device: (hd0,3) .This format is useful for installing the system image into a zone. Choosen entry will be: /hgfs - WARNING: fdo: Ignoring duplicate filter entry. Installing: Using existing zone boot environment Error: this is a system image and not a zone image. Log saved in non-global zone as /oraz1/p2vsol10/root/var/log/zones/zoneadm.20140329T074121Z.p2vsol10.attach [email protected]:~# zoneadm -z p2vsol10 attach -F [email protected]:~# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 3 uasol10z1 running /oraz1/sol10z1/uasol10z1 solaris10 excl - uaz1 installed /export/zones/uaz1 solaris excl - uaz2 installed /export/zones/uaz2 solaris excl - p2vsol10 installed /oraz1/p2vsol10 solaris10 excl [email protected]:~#[email protected]:~# zoneadm -z p2vsol10 boot zone 'p2vsol10': Error: The installed version of Solaris 10 is not supported.Reissue command without -L option to produce an archive for root pool install. Choosen entry will be: /P2VSOL10 - Running precreation scripts... zone 'p2vsol10': SPARC systems require patch 142909-17 zone 'p2vsol10': x86/x64 systems require patch 142910-17 zone 'p2vsol10': /usr/lib/brand/solaris10/s10_boot p2vsol10 /oraz1/p2vsol10 failed zone 'p2vsol10': cannot unmount '/oraz1/p2vsol10/root': Device busy zone 'p2vsol10': ERROR: unable to unmount /oraz1/p2vsol10/root.zone 'p2vsol10': ERROR: Unable to mount zone root dataset.

zoneadm: zone 'p2vsol10': call to zoneadmd failed [email protected]:~# I have blindly started the migration without checking the prerequisites.

Please leave a comment if you have any issue on this migration.

After almost a year I decided to upgrade the Operating Systems on my laptop.

In the previous article ,we have seen that how to install the fresh solaris 10 localzone installation on solaris 11 global zone. If possible ,you can also mount the flar image directory as NFS. Log saved in non-global zone as /oraz1/p2vsol10/root/var/log/zones/zoneadm.20140331T080401Z.p2vsol10.install [email protected]:/oraz1# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared - uaz1 installed /export/zones/uaz1 solaris excl - uaz2 installed /export/zones/uaz2 solaris excl - uasol10z1 installed /oraz1/sol10z1/uasol10z1 solaris10 excl - p2vsol10 installed /oraz1/p2vsol10 solaris10 excl [email protected]:/oraz1# Here you can see solaris 10 zone has been successfully installed using the flar image. Boot the local zone and login to the zone’s console .

But here we will see how to convert the existing solaris 10 physical servers as local zone on solaris 11 global zone. If there is any initial configuration is required, just complete the sysconfig wizard.

The plan was to install the latest Solaris build – Solaris Express Developer Edition 1/08 (snv_79) and open SUSE 10.3 along with the pre-installed Windows XP.