From: Tim Evans (tkevans@tkevans.com)
Date: Fri Jul 25 2003 - 23:35:47 EDT
Trying to complete upgrade to Solaris 9 4/03 via Live Upgrade to my
Alternate Boot disk. First pass suceeded:
luupgrade -u -s /cdrom/cdrom0 -n bootdisk
[ "bootdisk" is the alternate boot environment name ]
Per the man page, I need to run luupgrade with the '-i' option to load
the contents of the second cdrom--right from the man page:
# luupgrade -i -n bootdisk -s /dev/cdrom/cdrom0 \
-O "-nodisplay -noconsole"
This starts out as if it were going to work:
Validating the contents of the media </cdrom/cdrom0>.
The media is a standard Solaris media.
The media contains a standard Solaris installer.
The media contains <Solaris_2_of_2> version <9>.
Mounting BE <bootdisk>.
Running installer on BE <bootdisk>.
After a few seconds, however, I get:
INFORMATION: </var/sadm/system/logs/upgrade_log> contains a log of the
upgrade operation.
INFORMATION: </var/sadm/system/data/upgrade_cleanup> contains a log of
cleanup operations required.
WARNING: <162> packages must be installed on boot environment <bootdisk>.
INFORMATION: </var/sadm/system/data/packages_to_be_added> on boot
environment <bootdisk> contains a list of packages that must be installed
on the boot environment for the upgrade to be complete. The packages in
this list were not present on the media that was used to upgrade this boot
environment.
INFORMATION: If the boot environment was upgraded using one media of a
multiple media distribution, for example the Solaris CD media, you must
continue the upgrade process with the next media. Complete the upgrade by
using the luupgrade <-i> option to install the next media of the
distribution.
Then:
Failure to complete the upgrade process with all media of
the software distribution makes the boot environment unstable.
INFORMATION: Review the files listed above on boot environment <bootdisk>.
Before you activate the boot environment, determine if any additional
system maintenance is required or if additional media of the software
distribution must be installed.
Unmounting BE <bootdisk>.
The installer run on boot environment <bootdisk> is complete.
Despite the "installer run is complete" message, the target bootdisk
won't 'luactivate'.
Anyone have a workaround to pkgadd those "162" packages to the alternate
and convice luactivate to do its thing? Do I dare manually flip the eeprom
to boot from the other disk, installboot it, and give it a go, then run the
cdrom #2 installer later?
Hate to waste the four hours I've already spent on this...
Thanks.
-- Tim Evans | 5 Chestnut Court tkevans@tkevans.com | Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | 410-748-0160 (pager) _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:49 EDT