I'm in a very heavy dilemma! As you can read in the report below I now have a new BE that has been upgraded to s10u8 without a single error! It is mountable and the files in /var/sadm/system/.. give no warnings!
BUT ... it has been created and updated with the update 7 LU packages! In other threads I have shown that the upgrade 8 LU packages are not capable to do the job, nor is patch 121431-43 for s10, because it contains the same LU packages as update 8. I would like advice on how to ACTIVATE the new BE. Two days ago I tried luactivate from update 7. That did not work. It even ruined my bootblocks. ;-) That may have been caused by different LU packages on the source and the newBE (?). Not sure, just a wild guess. So, I was thinking of: [a] install LU from update 8 now and luactivate the new BE (might this work?) or [b] install the old LU from update 7 on the new ABE (s10u8) so the LU packages are in sync. Which would be the choice with the highest chances of working? I'm SO close now to a new updated BE? Only activation... ###upgrade report ################# arwen# lucreate -n s10u8 Checking GRUB menu... System has findroot enabled GRUB Analyzing system configuration. Comparing source boot environment <goofy> file systems with the file system(s) you specified for the new boot environment. Determining which file systems should be in the new boot environment. Updating boot environment description database on all BEs. Updating system configuration files. Creating configuration for boot environment <s10u8>. Source boot environment is <goofy>. Creating boot environment <s10u8>. Cloning file systems from boot environment <goofy> to create boot environment <s10u8>. Creating snapshot for <rpool/ROOT/goofy> on <rpool/ROOT/go...@s10u8>. Creating clone for <rpool/ROOT/go...@s10u8> on <rpool/ROOT/s10u8>. Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10u8>. Creating snapshot for <rpool/ROOT/goofy/zones> on <rpool/ROOT/goofy/zo...@s10u8>. Creating clone for <rpool/ROOT/goofy/zo...@s10u8> on <rpool/ROOT/s10u8/zones>. Setting canmount=noauto for </zones> in zone <global> on <rpool/ROOT/s10u8/zones>. Creating snapshot for <rpool/ROOT/goofy/zones/shire> on <rpool/ROOT/goofy/zones/sh...@s10u8>. Creating clone for <rpool/ROOT/goofy/zones/sh...@s10u8> on <rpool/ROOT/s10u8/zones/shire-s10u8>. Creating snapshot for <rpool/ROOT/goofy/zones/yanta> on <rpool/ROOT/goofy/zones/ya...@s10u8>. Creating clone for <rpool/ROOT/goofy/zones/ya...@s10u8> on <rpool/ROOT/s10u8/zones/yanta-s10u8>. Creating snapshot for <rpool/ROOT/goofy/zones/midgard> on <rpool/ROOT/goofy/zones/midg...@s10u8>. Creating clone for <rpool/ROOT/goofy/zones/midg...@s10u8> on <rpool/ROOT/s10u8/zones/midgard-s10u8>. Saving existing file </boot/grub/menu.lst> in top level dataset for BE <daffy> as <mount-point>//boot/grub/menu.lst.prev. Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10u8> as <mount-point>//boot/grub/menu.lst.prev. File </boot/grub/menu.lst> propagation successful Copied GRUB menu from PBE to ABE No entry for BE <s10u8> in GRUB menu Population of boot environment <s10u8> successful. Creation of boot environment <s10u8> successful. ### arwen# lofiadm -a /export/iso/s10u8.iso /dev/lofi/1 arwen# mount -F hsfs -o ro /dev/lofi/1 /iso arwen# luupgrade -u -n s10u8 -s /iso System has findroot enabled GRUB No entry for BE <s10u8> in GRUB menu Copying failsafe kernel from media. Uncompressing miniroot Creating miniroot device miniroot filesystem is <ufs> Mounting miniroot at </iso/Solaris_10/Tools/Boot> Validating the contents of the media </iso>. The media is a standard Solaris media. The media contains an operating system upgrade image. The media contains <Solaris> version <10>. Constructing upgrade profile to use. Locating the operating system upgrade program. Checking for existence of previously scheduled Live Upgrade requests. Creating upgrade profile for BE <s10u8>. Checking for GRUB menu on ABE <s10u8>. Saving GRUB menu on ABE <s10u8>. Checking for x86 boot partition on ABE. Determining packages to install or upgrade for BE <s10u8>. Performing the operating system upgrade of the BE <s10u8>. CAUTION: Interrupting this process may leave the boot environment unstable or unbootable. Upgrading Solaris: 100% completed Installation of the packages from this media is complete. Restoring GRUB menu on ABE <s10u8>. Updating package information on boot environment <s10u8>. Package information successfully updated on boot environment <s10u8>. Adding operating system patches to the BE <s10u8>. The operating system patch installation is complete. ABE boot partition backing deleted. PBE GRUB has no capability information. PBE GRUB has no versioning information. ABE GRUB is newer than PBE GRUB. Updating GRUB. GRUB update was successfull. Configuring failsafe for system. Failsafe configuration is complete. INFORMATION: The file </var/sadm/system/logs/upgrade_log> on boot environment <s10u8> contains a log of the upgrade operation. INFORMATION: The file </var/sadm/system/data/upgrade_cleanup> on boot environment <s10u8> contains a log of cleanup operations required. INFORMATION: Review the files listed above. Remember that all of the files are located on boot environment <s10u8>. Before you activate boot environment <s10u8>, determine if any additional system maintenance is required or if additional media of the software distribution must be installed. The Solaris upgrade of the boot environment <s10u8> is complete. Installing failsafe Failsafe install is complete. ###END of report -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D + http://nagual.nl/ | SunOS 10u8 10/09 | OpenSolaris 2010.02 b123 + All that's really worth doing is what we do for others (Lewis Carrol) _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
