Need help with Live Upgrade, S-10, update 3 to update 6
Amitava
to Update 6 using Live Upgrade.
I'm stuck at my current install and would appreciate help in
upgrading,
(btw, I posted this in Sun.com forums too)
--------------------------------------------------------------------------------
Current layout (sparc system w 3 disks)
--------------------------------------------------------------------------------
Disk 0: 16 GB:
/dev/dsk/c0t0d0s0 1.9G /
/dev/dsk/c0t0d0s1 692M /usr/openwin
/dev/dsk/c0t0d0s3 7.7G /var
/dev/dsk/c0t0d0s4 3.9G swap
/dev/dsk/c0t0d0s5 2.5G /tmp
Disk 1: 16 GB:
/dev/dsk/c0t1d0s0 7.7G /usr
/dev/dsk/c0t1d0s1 1.8G /opt
/dev/dsk/c0t1d0s3 3.2G /data1
/dev/dsk/c0t1d0s4 3.9G /data2
Disk 2: 33 GB:
/dev/dsk/c0t2d0s0 33G /data3
--------------------------------------------------------------------------------
The data file systems are not in use right now, and I was thinking of
partitioning the data3 into 2 or 3 file systems and then creating
a new BE.
This machine happens to have an existing Boot Environment which
is active and contains *all* file systems, even the data ones.
# lufslist -n 's10'
boot environment name: s10
This boot environment is currently active.
This boot environment will be active on next system boot.
Filesystem fstype device size Mounted on Mount Options
/dev/dsk/c0t0d0s4 swap 4201703424 - -
/dev/dsk/c0t0d0s0 ufs 2098059264 / -
/dev/dsk/c0t1d0s0 ufs 8390375424 /usr -
/dev/dsk/c0t0d0s3 ufs 8390375424 /var -
/dev/dsk/c0t1d0s3 ufs 3505453056 /data1 -
/dev/dsk/c0t1d0s1 ufs 1997531136 /opt -
/dev/dsk/c0t1d0s4 ufs 4294785024 /data2 -
/dev/dsk/c0t2d0s0 ufs 36507484160 /data3 -
/dev/dsk/c0t0d0s5 ufs 2727290880 /tmp -
/dev/dsk/c0t0d0s1 ufs 770715648 /usr/openwin -
I browsed the Solaris 10 Installation Guide and the man pages
for the lu commands, but can not find how to remove the data
file systems from the BE.
# lustatus shows
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
s10 yes yes yes no -
I can not even delete this BE, when I did run ludelete, it said
WARNING: Boot environment <s10> has one or more slices mounted at .
ERROR: The boot environment <s10> is the current BE.
ERROR: You are not allowed to delete the current active BE.
Unable to delete boot environment.
So, I find myself stuck.
Is there any way to do a Live Upgrade on this system ?
or do I have to do a fresh install of Sol 10 Update 6 ?
Thanks for your help.
Tim Bradshaw
> I can not even delete this BE, when I did run ludelete, it said
>
> WARNING: Boot environment <s10> has one or more slices mounted at .
> ERROR: The boot environment <s10> is the current BE.
> ERROR: You are not allowed to delete the current active BE.
> Unable to delete boot environment.
>
>
Blow away /etc/lu which will cause LU to forget its own name, and
start from scratch.
kangcool
This list is generated from vfstab of the s10 be
So all you have to do is remove the fs entries from vfstab, and they
will be removed from this list.
>
> I browsed the Solaris 10 Installation Guide and the man pages
> for the lu commands, but can not find how to remove the data
> file systems from the BE.
>
> # lustatus shows
>
> Boot Environment Is Active Active Can Copy
> Name Complete Now On Reboot Delete Status
> -------------------------- -------- ------ --------- ------ ----------
> s10 yes yes yes no -
>
> I can not even delete this BE, when I did run ludelete, it said
>
> WARNING: Boot environment <s10> has one or more slices mounted at .
> ERROR: The boot environment <s10> is the current BE.
> ERROR: You are not allowed to delete the current active BE.
> Unable to delete boot environment.
Because that is the OS your running.
>
> So, I find myself stuck.
>
> Is there any way to do a Live Upgrade on this system ?
> or do I have to do a fresh install of Sol 10 Update 6 ?
Two ways:
1) boot of DVD or netboot and do a upgrade
2) make some space on a disk slice - by umounting and removing from
vfstab
then do a lucreate.
>
> Thanks for your help.
Amitava
Thanks for the tips, they were of great help.
I commented out the entries in /etc/vfstab, also had to remove the
files /etc/lutab and /etc/lu/ICF.1
and then could create the Boot Environment from scratch.
I was also able to create another boot environment and copied into it,
but now I'm facing a different problem, error when trying to upgrade.
--------- BEGIN QUOTE -------------
# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
s10 yes yes yes no -
s10u6 yes no no yes -
--------- END QUOTE -------------
Now, I have the Solaris 10 Update 6 DVD image on another machine
which shares out the directory. I mounted it on this machine,
did a lofiadm and mounted that at /cdrom.
--------- BEGIN QUOTE -------------
# ls -CF /cdrom /cdrom/boot /cdrom/platform
/cdrom:
Copyright boot/
JDS-THIRDPARTYLICENSEREADME installer*
License/ platform/
Solaris_10/
/cdrom/boot:
hsfs.bootblock sparc.miniroot
/cdrom/platform:
sun4u/ sun4us/ sun4v/
--------- END QUOTE -------------
Now I tried to luupgrade and I get this error:
--------- BEGIN QUOTE -------------
# luupgrade -u -n s10u6 -s /cdrom
ERROR: The media miniroot archive does not exist </cdrom/boot/
x86.miniroot>.
ERROR: Cannot unmount miniroot at </cdrom/Solaris_10/Tools/Boot>.
{code}
--------- END QUOTE -------------
I find it strange that this sparc machine is complaining about
x86.miniroot.
BTW, the machine on which the DVD image is happens to be x86 running
Sol 10.
I thought that wouldn't matter, as it is just NFS sharing a directory
which has a DVD image.
What am I doing wrong?
Thanks.
Jim Leonard
> What am I doing wrong?
When performing a LiveUpgrade, always uninstall SUNWluu and SUNWlur
and then install those packages from the version you are trying to
upgrade to. The DVD layout changed in 10u6 and the newest liveupgrade
packages might be necessary to deal with the layout change.
Amitava
Thanks.
So, should I delete the Boot Environment and re-create it
or is it safe to continue with the BE-s already created ?
Is it sufficient just to update the SUNWluu and SUNWlur packages
and then run the luupgrade?
Thanks again.
Jim Leonard
> So, should I delete the Boot Environment and re-create it
> or is it safe to continue with the BE-s already created ?
> Is it sufficient just to update the SUNWluu and SUNWlur packages
> and then run the luupgrade?
Since it takes only a few minutes, I think it would be safest to
ludelete your BE, then upgrade the packages, then start over.
Amitava
Thanks!
Thomas Tornblom
And the easiest way to update the lu packages is probably to run:
Solaris*/Tools/Installers/liveupgrade20
from the new media.
Amitava
>
> - Show quoted text -
Just when I thought I passed the hurdles, I'm running into serious
problems.
The luupgrade ran fine without errors, but then I did "luactivate
newBE"
and then "init 6", but it booted back to the old BE.
I tried doing "init 0", then "boot disk2", that generated a lot of
errors (below)
and it ended up reverting back to the old BE.
I thought maybe something is wrong with disk2, so I did a "boot net"
and that too throws up same errors.
The errors are as follows:
------- BEGIN QUOTE ------
ufs-file-system
Loading: /platform/SUNW,UltraAX-MP/kernel/sparcv9/unix
Loading: /platform/sun4u/kernel/sparcv9/unix
SunOS Release 5.10 Version Generic_137137-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
os-io Configuring devices.
|
panic[cpu0]/thread=2a1045c5ca0: assertion failed: add_ivintr(hdlp-
>ih_vector, hdlp->ih_pri, (intrfunc)hdlp->ih_cb_func, hdlp-
>ih_cb_arg1, hdlp->ih_cb_arg2, NULL) == 0, file: ../../sun4/os/
ddi_impl.c, line: 771
000002a1045c4ef0 genunix:assfail+74 (10988e8, 1098960, 303, 1841000,
1259000, 0)
%l0-3: 00000000700091c0 00000000000007e8 000000000000000e
0000000070008a40
%l4-7: 0000000001259000 0000000000000000 000000000188cc00
0000000000000000
000002a1045c4fa0 unix:i_ddi_add_ivintr+50 (300000d4548, 0, e, e, d,
1098800)
%l0-3: 000006001093d190 0000000000000028 00000300000d42a8
00000000000000ff
%l4-7: 0000000000000001 0000000070000ad0 000000000000000e
0000000000000001
000002a1045c5050 pcipsy:pci_add_intr+268 (60011056ae8, 300002eb670,
300000d4548, 3000030ba80, 0, 28)
%l0-3: 00000300000d45b8 000006001100a768 000006001093d208
000006001100a740
%l4-7: 000006001093d190 00000000000007e8 00000300000d5888
00000000000007e8
000002a1045c5100 unix:i_ddi_intr_ops+e4 (300002eb670, 300002eb670, 6,
300000d4548, 0, 300002ed668)
.... etc etc...
----- END QUOTE ----
What could be the problem?