Sol10 b54 upgrade

Similar Threads:

1.Unable to upgrade to Sol Express B54 on SB1000

I'm trying to upgrade an SB1000 from Solaris 10 3/05 to Solaris Express 
B54 with no success.

The installer gets to the point where it is "Gathering upgrade 
information" and then a dialog pops up with the message:

"Error!"  "Could not reinitialize system state. Please exit the 
installer and restart the installation."

Once I select 'Exit' a terminal window opens and I can try restarting 
the installation -- no joy.

Any ideas?

[It just occurred to me this might not be the correct place to ask this 
question -- if not, guidance will be appreciated.]

Thanks,
-- 
HZ

2.Live Upgrade Problem from Sol8 to Sol10

Hi
I am trying to upgrade from Sol8 to Sol10 using Liveupgrade
feature...I am encountering the following error...can someone help
resolve...

lucreate  sol8  /:/dev/dsk/c1t1d0s0:ufs  /usr:/dev/dsk/
c1t1d0s3:ufs  sol10



[bwprd]# lucreate -c sol8 -m /://dev/dsk/c1t1d0s0:ufs -m /usr:/dev/dsk/
c1t1d0s3
:ufs -n sol10
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
ERROR: device <//dev/dsk/c1t1d0s0> does not exist
ERROR: device <//dev/dsk/c1t1d0s0> is not available for use with mount
point </>
ERROR: cannot create new boot environment using file systems as
configured
ERROR: please review all file system configuration options
ERROR: cannot create new boot environment using options provided
[bwprd]# lucreate -c sol8 -m /:/dev/dsk/c1t1d0s0:ufs -m /usr:/dev/dsk/
c1t1d0s3:
ufs -n sol10
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
No name for current boot environment.
Current boot environment is named <sol8>.
Creating initial configuration for primary boot environment <sol8>.
WARNING: /etc/lib/lu/lubootdev: ERROR: Unable to determine the boot
device for this system.
WARNING: Unable to obtain root device directly from boot prom;
attempting to access boot device settings directly.
WARNING: Unable to determine root device by accessing boot device
settings directly.
ERROR: Unable to determine root device for current BE.
ERROR: Cannot determine the physical boot device for the current boot
environment <sol8>.
Use the <-C> command line option to specify the physical boot device
for the current boot environment <sol8>.
ERROR: Cannot create configuration for primary boot environment.
[bwprd]# /usr/sbin/lu

3.Sol10: Unable to do a live upgrade from Sol9

Arno Schneider wrote:

> I am unable to do an live upgrade from sol9 to sol10. After the luupgrade i
> got the messages that 19 packages failed to install. And f.e. the
> /etc/inittab on the sol10 boot environment is not updated. When i look
> in the logs i can see the following msgs:
> 
> Doing pkgadd of SUNWvolr to /.
> installf: ERROR: relative pathname in link specification </etc/rc0.d/K05volmgt>
> installf: ERROR: relative pathname in link specification </etc/rc1.d/K05volmgt>
> installf: ERROR: relative pathname in link specification </etc/rc2.d/K05volmgt>
> installf: ERROR: relative pathname in link specification </etc/rc3.d/S81volmgt>
> installf: ERROR: relative pathname in link specification </etc/rcS.d/K05volmgt>
> pkgadd: ERROR: class action script did not complete successfully
> pkgadd: ERROR: missing entry in contents file for </a/etc/rc0.d/K05volmgt>
> 
> Installation of <SUNWvolr> failed (internal error) - package
> 
> 
> Any hints?

Which live upgrade package did you use? The one from Sol9 or the
one from Sol10?

You need to use the one from the version you are upgrading to. In
this case Sol10.


/Roger

-- 
Roger Gustavsson
roger.gustavsson (_at_) teliasonera.com

4.Solved! [was: Unable to upgrade to Sol Express B54 on SB1000]

Removing the entry for the second disk from /etc/vfstab but leaving the 
disk physically connected allowed the install for Nevada Build 54 to 
proceed to completion.

The failure caused by the phantom /dev/dsk/c2* entry remains a Huge 
Freakin' Mystery.

Thank you to James and Ian for valuable suggestions.
-- 
HZ

5.Legato server upgrade (7.3.1 on Sol9 => sol10)

	I have a strange problem upgrading our EBS server OS from
	Solaris 9 to Solaris 10.

	The system has run almoust three years on Solaris 9 with 
	EBS 7.x, currently 7.3.1. The hardware is V240 with SE3310
	as adv_disk type cache and L25 with two LTO2 tape drives.
	About 150 clients.

	Now I broke the sol9 root mirror, and did full install of
	sol10 to the offbroken part. All fine, OS boots and works,
	but when I install and start EBS 7.3.1 (ie. 7.3 install
	and patches) on sol10, the nsrexecd processes newer go to
	backround (waited ~10 minutes) and so EBS boot script newer
	got past nsrexedc start. And according truss, the nsrexecd
	prosesses just sit idle, the first waiting for the second
	to write something back.

	EBS works still nicely if I boot the old sol9 partition.

	My guess is, that it is some kind of identity problem, but what?
	The new incarnation has same ip and name on same interface
	on same physical machine!

	EBS (client) starts fine on other sol10 machines.
-- 
 XXXX@XXXXX.COM , University of Helsinki, Computing Centre

6. Windows 7 (Vista7) Upgrade Woes : Beware the 20 hour Windows 7 upgrade

7. Upgrading Linux Fedora 11 v/s upgrading to Vista7

8. Windows 7 (Vista7) Upgrade Woes : Beware the 20 hour Windows 7 upgrade