From: Mcrae, Darren A (darren.mcrae@capgemini.com)
Date: Wed May 19 2004 - 09:03:06 EDT
After reading the email concerning Live upgrade (something I'd never heard
of) I thought I have a look at it. In order to familarise myself with the
product I thought I try it first on my vmware solaris 8 installation. So
following the instructions I patched it with the latest patch cluster and
then installed live upgrade from disk 2 of my solaris 9 disks.
I thought I'd use the lu (fmli) interface first before trying the command
line interface. I went through the screens and created a solaris9 ABE, but
as it creates it I get these errors. As you can see it fails trying the
target device. Has anyone seen this before or can help.
SunOS vmware-sol 5.8 Generic_117351-02 i86pc i386 i86pc
----------------------------------------------------------------------------
------------
Analyzing system configuration.
No name for Current BE.
Current BE is named <solaris8>.
Creating initial configuration for primary BE <solaris8>.
PBE configuration successful: PBE name <solaris8> PBE Boot Device
</dev/dsk/c0d0s0>.
Comparing vfstab entries in source BE <solaris8> with file system(s) you
specified for the new BE. Determining which file systems should be in the
new BE.
Analyzing system configuration.
Comparing vfstab entries in source BE <solaris8> with file system(s) you
specified for the new BE. Determining which file systems should be in the
new BE.
ERROR: Configuration of BE failed.
Analyzing system configuration.
Comparing vfstab entries in source BE <solaris8> with file system(s) you
specified for the new BE. Determining which file systems should be in the
new BE.
Updating system configuration files.
Creating configuration for boot environment <solaris9>.
**********************************************************************
Beginning process of creating Boot Environment <solaris9>.
No more user interaction is required until this process is complete.
**********************************************************************
Creating file systems on BE <solaris9>.
Creating <ufs> file system on </dev/dsk/c1d1s0>.
Mounting file systems for BE <solaris9>.
Calculating required sizes of file systems for BE <solaris9>.
Populating file systems on BE <solaris9>.
Copying file system contents to BE <solaris9>.
Copying of file system / directory </> is in progress...
Copying of file system / directory </> completed successfully.
Creating compare database for file system </>.
Updating compare database on other BEs.
Updating compare database on BE <solaris9>.
Compare databases updated on all BEs.
CBE <solaris8> boot device is </dev/rdsk/c0d0p1>.
Copying X86 boot device.
Making Boot Environment <solaris9> bootable.
Updating bootenv.rc on ABE <solaris9>.
ERROR: Unable to mount target boot environment <solaris9> root device
</dev/dsk/c1d1s0> to mount point </tmp/.alt.2717>.
ERROR: The root slice <> of the target boot environment <solaris9> is not
available.
ERROR: Update of loader failed.
ERROR: Unable to umount ABE <solaris9>: cannot make ABE bootable.
Making the ABE <solaris9> bootable FAILED.
ERROR: Unable to make BE <solaris9> bootable.
ERROR: Unable to populate file systems on BE <solaris9>.
ERROR: Unable to make file systems for BE <solaris9>.
Creating configuration for boot environment <solaris9>.
ERROR: Internal Configuration File </etc/lu/ICF.2> is not a file.
ERROR: The BE <solaris9> is in an incomplete state and the internal
configuration file </etc/lu/ICF.2> is not valid.
Creating configuration for boot environment <solaris9>.
ERROR: Internal Configuration File </etc/lu/ICF.2> is not a file.
ERROR: The BE <solaris9> is in an incomplete state and the internal
configuration file </etc/lu/ICF.2> is not valid.
Regards
Darren
Our name has changed. Please update your address book to the following format: "recipient@capgemini.com".
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
_______________________________________________
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:28:41 EDT