SUMMARY: live upgrade / NetraX1 / boot-device

From: Geoff Lane <>
Date: Fri Oct 03 2003 - 05:48:37 EDT
I only received one reply (+a number of "I'm away" messages + a request from
an anti-spam filter asking me to visit some web page to confirm I was not
a spammer, which I ignored) included below.

I did some experiments and no matter what the boot-device was originally set
to, Live Upgrade could not set the correct boot-device for a newly activated
BE on this particular server (I've seen it work OK on others) so there is
more to the story than we currently know.

Setting by hand works OK so that's what I did and the cloned root drive


From: BAUMLER Julie L 

Live upgrade assumes that your boot-device variable in the OBP has a disk
listed as the first item.  If your OBP isn't set up so that disk is first,
live upgrade resets the first value in boot-device (like cdrom to cdrom2)
when it runs, your system will then boot off the second device since the
first doesn't exist or has no media and you will come up in your original
boot environment; you can fix this by changing the boot-device in eeprom
before creating a new boot environment, or by setting it in each boot
environment (using init 0; boot <boot-device> to get to your new boot
environment the first time.)  


> On a fully patched NetraX1 running Solaris8
> 	SunOS xxxx 5.8 Generic_108528-23 sun4u sparc SUNW,UltraAX-i2
> I'm trying to clone the root drive using Live Upgrade 2.0 08/01
> After activating the new boot environment(BE), and using
> 	shutdown -y -g0 -i6
> the system continues to reboot into the current BE and not the new BE.
> The following is part of the shutdown messages...
> ----------------------------------------------------------------
> Live Upgrade: Deactivating current boot environment <xxxx_8a>.
> Live Upgrade: Executing Stop procedures for boot environment 
> <xxxx_8a>.
> Live Upgrade: Current boot environment is <xxxx_8a>.
> Live Upgrade: New boot environment will be <xxxx_8b>.
> Live Upgrade: Activating boot environment <xxxx_8b>.
> Live Upgrade: Updating partition ID tag on boot environment <xxxx_8b>
> device </dev/rdsk/c0t2d0s2> to be root slice.
> fmthard:  New volume table of contents now in place.
> Live Upgrade: Updating boot loader for <SUNW,UltraAX-i2> on boot
> environment <xxxx_8b> device </dev/rdsk/c0t2d0s0> to match OS release.
> Live Upgrade: The boot device for boot environment <xxxx_8b> will be
> </dev/dsk/c0t2d0s0>.
> Live Upgrade: Changing primary boot device to boot 
> environment <xxxx_8b>.
> Live Upgrade: The current boot environment <xxxx_8a> boots from device
> <cdrom:a disk:a>.
> Live Upgrade: The new boot environment <xxxx_8b> boots from device
> <cdrom:a disk:a>.
> Live Upgrade: Activation of boot environment <xxxx_8b> completed.
> ----------------------------------------------------------------
> Notice that the boot device for the new BE is the same as the 
> current BE
> which explains the symptoms.  Altering boot-device with 
> eeprom works as
> expected. SunSolve and Google don't return anything useful.
> Does anybody have any idea why Live Upgrade isn't setting boot-device
> correctly?
> Thanks,
> -- 
> /\ Geoff. Lane. /\ Manchester Computing /\ Manchester /\ M13 
> 9PL /\ England /\
> _______________________________________________
> sunmanagers mailing list

----- End forwarded message -----

/\ Geoff. Lane. /\ Manchester Computing /\ Manchester /\ M13 9PL /\ England /\
sunmanagers mailing list
Received on Fri Oct 3 05:48:29 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:23 EST