Yes, the old one rebooted after lucreate. puh! Then
# luupgrade -u -n nv91 -s /media/SOL_11_X86/ [I have no .iso here] Copying failsafe kernel from media. Uncompressing miniroot Uncompressing miniroot archive (Part2) 13371 blocks Creating miniroot device miniroot filesystem is <ufs> Mounting miniroot at </media/SOL_11_X86//Solaris_11/Tools/Boot> Mounting miniroot Part 2 at </media/SOL_11_X86//Solaris_11/Tools/Boot> Validating the contents of the media </media/SOL_11_X86/>. The media is a standard Solaris media. The media contains an operating system upgrade image. The media contains <Solaris> version <11>. 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 <nv91>. Checking for GRUB menu on ABE <nv91>. Checking for x86 boot partition on ABE. Determining packages to install or upgrade for BE <nv91>. Performing the operating system upgrade of the BE <nv91>. 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. Deleted empty GRUB menu on ABE <nv91>. Adding operating system patches to the BE <nv91>. The operating system patch installation is complete. ABE boot partition backing deleted. Configuring failsafe for system. Failsafe configuration is complete. INFORMATION: The file </var/sadm/system/logs/upgrade_log> on boot environment <nv91> contains a log of the upgrade operation. INFORMATION: The file </var/sadm/system/data/upgrade_cleanup> on boot environment <nv91> contains a log of cleanup operations required. WARNING: <2> packages failed to install properly on boot environment <nv91>. INFORMATION: The file </var/sadm/system/data/upgrade_failed_pkgadds> on boot environment <nv91> contains a list of packages that failed to upgrade or install properly. INFORMATION: Review the files listed above. Remember that all of the files are located on boot environment <nv91>. Before you activate boot environment <nv91>, 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 <nv91> is partially complete. Installing failsafe Failsafe install is complete. Still, before having to fdisk the whole drive just another time, I considered the problem message: "The file </var/sadm/system/data/upgrade_failed_pkgadds> on boot environment <nv91> contains a list of packages that failed to upgrade or install properly." By now, thanks to your hint 'man live_upgrade', I could easily mount the new BE: # lumount nv91 /.alt.nv91 and read the problem statement: # cat /.alt.nv91/var/sadm/system/data/upgrade_failed_pkgadds SUNWxwplt SUNWmcc # luumount nv91 # Good so far. Next I'd need to know what went wrong with the 2 packages? By the way, I wonder if - with all the virtualisation - we should be able to 'test-boot' a boot environment; be it in VxM, qemu or whatnot. Doesn't need to be fast, not even X, just to get a console. Would save a lot of nerves; and a re-install of everything in case something fails after the luactivate. It is a full BE, so why would this not be feasible? But this is future. Next I need to know what to do about the 'partial luupgrade' that my efforts ended with. This message posted from opensolaris.org
