DiskSuite and Live Upgrade 2.0

I have two Solaris 7 boxes running DiskSuite to mirror the O/S disk onto another drive.
I need to upgrade to Solaris 8. In the past I have used Live Upgrade to do so, when I have enough free disk space to partition an existing disk or to use a unused disk for the Solaris 8 system files.
In this case, I do not have sufficient free space on the boot disk. So, what is the best approach? It seems that I would have to:
1. unmirror the file system
2. install Solaris 8 onto the old mirror drive using LU 2.0
3. make the old mirror drive the boot drive
4. re-establish mirroring, being sure that it goes the right way from the Solaris 8 disk to the old boot disk
Comments, suggestions?

I recently built a system (specs below) and installed this card (MSI GF4 Ti4200 VTD8X MS8894, 128MB DDR), and when I try to use Live Update 2 (version 3.33.000, from the CD that came with the card), I get the same message:
"Warning!!! Your Display Card does not support MSI Live Update 2 function. Note: MSI Live Update 2 supports the Display Cards of MSI only."
I'm using the drivers/BIOS that came on the CD: Driver version 6.13.10.4107, BIOS version 4.28.20.05.11. I see on the nVidia site that they have the 4109 drivers out now, should I try those? ?(
I have also made sure to do the suggested modifications to IE (and I don't have PC-cillin installed):
"Note: In order to operate this application properly, please note the following suggests.
-Set the IE security setting 'Download signed ActiveX controls' to [Enable] or [Prompt]. (System default is [Prompt]).
-Disable 'WebTrap' of PC-cillin(R) or any web based anti-virus application when executing MSITM Live Update 2TM.
-Update Microsoft® Windows® Installer"
I downloaded a newer version of LIveUpdate (3.35.000), and installed it (after completely uninstalling the old version), and got the same results. Nothing on my system is currently overclocked.
Help!
System specs:
-Soyo SY-KT400 DRAGON Ultra (Platinum Edition) with latest BIOS & Chipset Drivers
-AMD Athlon XP Thoroughbred 2100+
-MSI GF4 Ti4200 VTD8X (MS-8894)
-WD Caviar Special Edition 80 GB HDD, 8 MB Cache
-512 MB Crucial PC2700 DDR (one stick, in DIMM #1)
-TDK 40/12/48 CD R/RW
-Daewoo 905DF Dynaflat 19" Monitor
-Windows XP Home Edition, SP1/all other updates current
-On-Board CMedia 6-channel audio
-On-Board VIA 10/100 Ethernet
-Altec-Lansing ATP3 Speakers

Similar Messages

Volume as install disk for Guest Domain and Live Upgrade

Hi Folks,
I am new to LDOMs and have some questions - any pointers, examples would be much appreciated:
(1) With support for volumes to be used as whole disks added in LDOM release 1.0.3, can we export a whole LUN under either VERITAS DMP or mpxio control to guest domain and install Solaris on it ? Any gotchas or special config required to do this ?
(2) Can Solaris Live Upgrade be used with Guest LDOMs ? or is this ability limited to Control Domains ?
Thanks

The answer to your #1 question is YES.
Here's my mpxio enabled device.
non-STMS device name STMS device name
/dev/rdsk/c2t50060E8010029B33d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
/dev/rdsk/c3t50060E8010029B37d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
create the virtual disk using slice 2
ldm add-vdsdev /dev/dsk/c4t4849544143484920373730313036373530303136d0s2 77bootdisk@primary-vds01
add the virtual disk to the guest domain
ldm add-vdisk apps bootdisk@primary-vds01 ldom1
the virtual disk will be imprted as c0d0 which is the whole lun itself.
bind, start ldom 1 and install OS (i used jumpstart) and it partitioned the boot disk c0d0 as / 15GB, swap the remaining space (10GB)
when you run format, print command on both guest and primary domain on this disk you'll see the same slice/size information
Part Tag Flag Cylinders Size Blocks
0 root wm 543 - 1362 15.01GB (820/0/0) 31488000
1 swap wu 0 - 542 9.94GB (543/0/0) 20851200
2 backup wm 0 - 1362 24.96GB (1363/0/0) 52339200
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
I havent used DMP but HDLM (Hitachi Dynamic link manager) seems not supported by ldom as i cannot make it work :(
I have no answer on your next question unfortunately.

Non-Global zones and Live Upgrade

Good afternoon,
Trying to find an answer for a question that I have.
Currently we have (2) T5140 servers. One of them is our production Sun Messaging Server and the other is the backup. The zones are SAN-attached disks(currently running on the Production server) and each server is "aware" of them. They are only mounted on one server at a time. My question is, I can do a LiveUpgrade on the backup server (from Solaris10u10 to Solaris10u11) and then detach/export the NGZ from the production system and use "update on attach" to upgrade the NGZ to Solaris10u11. If I don't upgrade the Production Box(Global) to u11 and have to move my NGZ back to it, will "update on attach" rollback the NGZs back to u10?
We have a test system that we will be working through to test using LiveUpgrade without detaching the zones. But wanted to see the feasibility of doing this the way I have it mention in the above paragraph.
Thanks in advance for your help!!
Doug

Found my answer: BigAdmin Feature Article: The Zones Update on Attach Feature and Patching in the Solaris 10 OS</title><meta nam…

ZFS root and Live upgrade

Is it possible to create /var as its own ZFS dataset when using liveupgrade? With ufs, there's the -m option to lucreate. It seems like any liveupgrade to a ZFS root results in just the root, dump, and swap datasets for the boot environment.
merill

Hey man.
I bad my head against the wall with the same question :-)
One thing that might help you out anyway is that i found a solution on how to move ufs filesystems to the new ZFS pool.
Let's say you have a ufs fs with let's say application server and stuff on /app which is on c1t0d0s6.
When you create the new ZFS based BE the /app is shared.
In order to move it to the new BE, all you need to do is to comment the lines in /etc/vfstab you want to be moved.
then run lucreate to create the ZFS BE.
After that, create a new dataset for /app, just give it a different mountpoint.
Copy all your stuff.
rename the original /app
and set the dataset's mountpoint
this is it, all your stuff are now on ZFS.
Hope it will be usefull,

UCE and live upgrade (again)

Hi, does anyone have any information on how one might use UCE to patch inactive LU BEs?
Thanks
--tim

Thanks!
--tim

Live upgrade, zones and separate mount points

Hi,
We have a quite large zone environment based on Solaris zones located on VxVM/VxFS. I know this is a doubtful configuration but the choice was made before i got here and now we need to upgrade the environment. Veritas guides says its fine to locate zones on Veritas, but i am not sure Sun would approve.
Anyway, sine all zones are located on a separate volume i want to create a new one for every zonepath, something like:
lucreate -n upgrade -m /:/dev/dsk/c2t1d0s0:ufs -m /zones/zone01:/dev/vx/dsk/zone01/zone01_root02:ufs
This works fine for a while after integration of 6620317 in 121430-23, but when the new environment is to be activated i get errors, see below[1]. If i look at the command executed by lucreate i see that the global root is mounted, but by zoneroot does not seem to have been mounted before the call to zoneadmd[2]. While this might not be a supported configuration, VxVM seems to be supported and i think that there are a few people out there with zonepaths on separate disks. Live upgrade probably has no issues with the files moved from the VxFS filesystem, that parts has been done, but the new filesystems does not seem to get mounted correctly.
Anyone tried something similar or has any idea on how to solve this?
The system is a s10s_u4 with kernel 127111-10 and Live upgrade patches 121430-25, 121428-10.
1:
Integrity check OK.
Populating contents of mount point </>.
Populating contents of mount point </zones/zone01>.
Copying.
Creating shared file system mount points.
Copying root of zone <zone01>.
Creating compare databases for boot environment <upgrade>.
Creating compare database for file system </zones/zone01>.
Creating compare database for file system </>.
Updating compare databases on boot environment <upgrade>.
Making boot environment <upgrade> bootable.
ERROR: unable to mount zones:
zoneadm: zone 'zone01': can't stat /.alt.upgrade/zones/zone01/root: No such file or directory
zoneadm: zone 'zone01': call to zoneadmd failed
ERROR: unable to mount zone <zone01> in </.alt.upgrade>
ERROR: unmounting partially mounted boot environment file systems
ERROR: umount: warning: /dev/dsk/c2t1d0s0 not in mnttab
umount: /dev/dsk/c2t1d0s0 not mounted
ERROR: cannot unmount </dev/dsk/c2t1d0s0>
ERROR: cannot mount boot environment by name <upgrade>
ERROR: Unable to determine the configuration of the target boot environment <upgrade>.
ERROR: Update of loader failed.
ERROR: Unable to umount ABE <upgrade>: cannot make ABE bootable.
Making the ABE <upgrade> bootable FAILED.
ERROR: Unable to make boot environment <upgrade> bootable.
ERROR: Unable to populate file systems on boot environment <upgrade>.
ERROR: Cannot make file systems for boot environment <upgrade>.
2:
0 21191 21113 /usr/lib/lu/lumount -f upgrade
0 21192 21191 /etc/lib/lu/plugins/lupi_bebasic plugin
0 21193 21191 /etc/lib/lu/plugins/lupi_svmio plugin
0 21194 21191 /etc/lib/lu/plugins/lupi_zones plugin
0 21195 21192 mount /dev/dsk/c2t1d0s0 /.alt.upgrade
0 21195 21192 mount /dev/dsk/c2t1d0s0 /.alt.upgrade
0 21196 21192 mount -F tmpfs swap /.alt.upgrade/var/run
0 21196 21192 mount swap /.alt.upgrade/var/run
0 21197 21192 mount -F tmpfs swap /.alt.upgrade/tmp
0 21197 21192 mount swap /.alt.upgrade/tmp
0 21198 21192 /bin/sh /usr/lib/lu/lumount_zones -- /.alt.upgrade
0 21199 21198 /bin/expr 2 - 1
0 21200 21198 egrep -v ^(#|global:) /.alt.upgrade/etc/zones/index
0 21201 21198 /usr/sbin/zonecfg -R /.alt.upgrade -z test exit
0 21202 21198 false
0 21205 21204 /usr/sbin/zoneadm -R /.alt.upgrade list -i -p
0 21206 21204 sed s/\([^\]\)::/\1:-:/
0 21207 21203 zoneadm -R /.alt.upgrade -z zone01 mount
0 21208 21207 zoneadmd -z zone01 -R /.alt.upgrade
0 21210 21203 false
0 21211 21203 gettext unable to mount zone <%s> in <%s>
0 21212 21203 /etc/lib/lu/luprintf -Eelp2 unable to mount zone <%s> in <%s> zone01 /.alt.up
Edited by: henrikj_ on Sep 8, 2008 11:55 AM Added Solaris release and patch information.

I updated my manual pages got a reminder of the zonename field for the -m option of lucreate. But i still have no success, if i have the root filesystem for the zone in vfstab it tries to mount it the current root into the alternate BE:
# lucreate -u upgrade -m /:/dev/dsk/c2t1d0s0:ufs -m /:/dev/vx/dsk/zone01/zone01_rootvol02:ufs:zone01
<snip>
Creating file systems on boot environment <upgrade>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c2t1d0s0>.
Creating <ufs> file system for </> in zone <zone01> on </dev/vx/dsk/zone01/zone01_rootvol02>.
Mounting file systems for boot environment <upgrade>.
ERROR: UX:vxfs mount: ERROR: V-3-21264: /dev/vx/dsk/zone01/zone01_rootvol is already mounted, /.alt.tmp.b-gQg.mnt/zones/zone01 is busy,
allowable number of mount points exceeded
ERROR: cannot mount mount point </.alt.tmp.b-gQg.mnt/zones/zone01> device </dev/vx/dsk/zone01/zone01_rootvol>
ERROR: failed to mount file system </dev/vx/dsk/zone01/zone01_rootvol> on </.alt.tmp.b-gQg.mnt/zones/zone01>
ERROR: unmounting partially mounted boot environment file systems
If i tried to do the same but with the filesystem removed from vfstab, then i get another error:
<snip>
Creating boot environment <upgrade>.
Creating file systems on boot environment <upgrade>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c2t1d0s0>.
Creating <ufs> file system for </> in zone <zone01> on </dev/vx/dsk/zone01/zone01_upgrade>.
Mounting file systems for boot environment <upgrade>.
Calculating required sizes of file systems for boot environment <upgrade>.
Populating file systems on boot environment <upgrade>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Populating contents of mountED.
ERROR: Unable to make boot environment <upgrade> bootable.
ERROR: Unable to populate file systems on boot environment <upgrade>.
ERROR: Cannot make file systems for boot environment <upgrade>.
If i let lucreate copy the zonepath to the same slice as the OS, the creation of the BE works fine:
# lucreate -n upgrade -m /:/dev/dsk/c2t1d0s0:ufs

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

X86 server: Live Upgrade - now no grub

Hi,
I am did a live upgrade of a server in a test environment, the test server mirrors our production hosts. The problem I have is I do not have the luxury of doing live upgrade on another slice on the same disk. I am working with an x4600, so my primary root disk is c3t0d0, alternate disk: c3t1d0. Since I do not have the ability to use c3t0d0 as a location of another BE, I am stuck using the only other disk, c3t1d0. So am left breaking the mirror and live upgrading to c3t1d0. Now the problem, once I complete the LU successfully, and everything is tested, we now make the new BE gold and basically sync up the old BE drive (c3t0d0) to the new BE (c3t1d0). HERE COMES MY ISSUES: The problem is once I do that i no longer have grub.
I receive this error when I run bootadm list-menu:
# bootadm list-menu
mount: /dev/md/dsk/d0 no such device
bootadm: mount of /dev/md/dsk/d0 (fstype ufs) failed
bootadm: cannot find GRUB menu
and you guess it, once I reboot, I am hosed. So I am left with going into single-user mode off of my jumpstart server. once I do that I add the following on both disks (c3t0d0 and c3t1d0)
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris 10 8/07 s10x_u4wos_10 X86
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
#---------------------END BOOTADM--------------------
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris failsafe
kernel /boot/multiboot kernel/unix -s -B console=ttya
module /boot/x86.miniroot-safe
#---------------------END BOOTADM--------------------
title Solaris 10 8/07 s10x_u4wos_10 X86 (single-user)
kernel /platform/i86pc/multiboot -s -B console=ttya
module /platform/i86pc/boot_archive
The server come up just fine, but STILL, when I do a bootadm list-menu, it STILL references the following:
# bootadm list-menu
mount: /dev/md/dsk/d0 or /tmp/GRUB_slice_mntpt.891, no such file or directory
bootadm: mount of /dev/md/dsk/d0 (fstype ufs) failed
bootadm: cannot find GRUB menu
any help would be appreciated, I know this is not the ideal usage of live upgrade, but when I have no other option, what am I suppose to do?
thanks

cat /etc/lu/GRUB_slice
set the PHYS_SLICE and LOG_SLICE to the correct one,
also check /etc/lu/GRUB_root and make sure the correct disk (either single disk or metadisk) is listed there.

Live upgrade - solaris 8/07 (U4) , with non-global zones and SC 3.2

Dears,
I need to use live upgrade for SC3.2 with non-global zones, solaris 10 U4 to Solaris 10 10/09 (latest release) and update the cluster to 3.2 U3.
i dont know where to start, i've read lots of documents, but couldn't find one complete document to cover the whole process.
i know that upgrade for solaris 10 with non-global zones is supported since my soalris 10 release, but i am not sure if its supported with SC.
Appreciate your help

Hi,
I am not sure whether this document:
http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach
has been on the list of docs you found already.
If you click on the download link, it won't work. But if you use the Tools icon on the upper right hand corner and click on attachements, you'll find the document. Its content is solely based on configurations with ZFS as root and zone root, but should have valuable information for other deployments as well.
Regards
Hartmut

I am on windows 7 and I upgraded to 10.0.2 and now it will not open. I have removed firefox completely and uploaded it again and that did not work. So my latest attempt I removed firefox 10 again and uploaded the beta version and once again nothing.

I am on windows 7 and I upgraded to the newest verison of firefox and now it will not open. I have removed firefox completely and uploaded it again and that did not work. I then made sure it could get through my firewall and that did not work. So my latest attempt I removed firefox 10 again and uploaded the beta version hoping that would do it and once again nothing. It will not open at all. Please help - is there a live chat or a number to talk to someone at Firefox?

I think when uninstalling you may also have to choose (tick) to delete the preferences and other personal data like the bookmarks, stored passwords etc. to erase completely. If you are installing afresh, please try right-clicking on the file and '''Run as administrator''' to install. And when uninstalling, please also make sure choose to delete all data and also manually delete any '''Mozilla''', '''Mozilla Firefox''' or '''Firefox''' from %appdata%, %localappdata% and %programfiles%. You can open a location by typing for eg. %appdata% in the '''Run''' box (Windows key + R). You may also have to check the '''VirtualStore''' folder in %localappdata%. Files in the VirtualStore can be problematic. I think a clean installation may help.
[https://www.mozilla.org/en-US/firefox/new/ Firefox]
[http://kb.mozillazine.org/Installation_directory Installation Folder]
[http://kb.mozillazine.org/Profile_folder Profile Folder]
Please note that using system restore would usually damage the Firefox installation.

How to delete file systems from a Live Upgrade environment

How to delete non-critical file systems from a Live Upgrade boot environment?
Here is the situation.
I have a Sol 10 upd 3 machine with 3 disks which I intend to upgrade to Sol 10 upd 6.
Current layout
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.
However, the system already has a BE (named s10) and that BE lists
all of the filesystems, incl 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.
How do I do a live upgrade on this system?
Thanks for your help.

Thanks for the tips.
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.
# 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    -        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.
# 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/Now I did luupgrade and I get this error:
# 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>.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.

Thin white line between line art and live paint fill?

I am using live paint to paint cartoon character illustrations. The artwork is brought into Illustrator CS3 and live traced. Then I convert it to a live paint group and use the paint bucket to fill. Everything looks fine no matter how much I zoom in. If I bring the AI file into Photoshop CS6 I can see a thin white line between the black line art and the fill. This is most noticeable where black meets black. I can also see this sometimes in file previews while browsing through files. If the white line cannot be seen in Illustrator is the file ok? I did just upgrade to CS6 if that would make a difference.
Thank you for any help.

If the white line cannot be seen in Illustrator is the file ok?
Without knowing specifics,nobody knows.
"Okay" for what?
If it looks okay to you in Illustrator, then it's okay for viewing in Illustrator.
If the export of it does not look okay in Photoshop at 1:1 or higher zoom, then it's probably not okay for whatever you're going to do with that raster image.
If it's printed to a low-res composite printer, then it may be okay, because the printer may not be able to resolve the whitish pixels.
If it's printed for commercial (color-separated) reproduction, it may not be okay, depending on the scale at which it will be printed, and on other considerations partially described below.
The autotrace routine does not build traps. Typically, when you color-fill cartoon line art manually, you don't make the shapes that define the fills merely "kiss" the black line work, as would the default treatments of a stupid autotrace. The black line work typically overprints the fills, thereby creating printing traps.
Suppose a portion of your cartoon is a hand-drawn closed circle. The black line work is irregular; it varies in width, having been drawn with a marker or a brush. The circle is colored in with a medium green. There are no sloppy gaps in the original between the green and the black.
You scan it and autotrace it. Unless you apply some deliberate care to make it do otherwise, the autotrace is going to create a compound path, filled with black, and with no stroke; and a green simple path which (hopefully) exactly "kisses" (abuts) the black path. Adobe's on-screen antialiasing of the edge where the two colors abut may or may not cause your monitor to display a faint whitish or grayish sliver between the two colors.
Similarly, Photoshop's rasterization of it, or the rasterization of a raster export filter may do the same, and may actually result in some off-color pixels along the edge. (Your description of the scenario kinda raises the question of why you are auto-tracing something that you're then just going to rasterize in Photoshop anyway. Why do that? Why not just work with the scan in Photoshop?.)
So let's leave Photoshop out of the picture and assume you are autotracing it because you want vector artwork. You zoom way in to see if the whitish sliver enlarges. It doesn't, so you assume it's just an aberation of Illustrator's on-screen antialising. And then someone tells you you're in the clear. But are you? Not so fast.
Let's assume the artwork is destined for commercial (color-separated) printing. Further assume the color of the autotraced black is 100% K, and the color of the autotraced green is 100Y 50C. Three inks involved. None of those three inks are shared between the two objects. So even if the paths do, in fact, perfectly abut, there is no "wiggle room" built in for the minor alignment shifts that almost aways do occur on press.
Bottom line: Even if you do determine that the common antialiasing aberations that frequently occur on-screen in Adobe apps is just that—just an onscreen aberation, that does not necessarily mean your file is suitable for commercial color-separated reproduction.
First, you need to understand that autotracing is not the one-click, instant "conversion" of a raster image to vector artwork that far too many think it to be. Just like everything else, you don't just launch a program like Illustrator, start autotracing things willy-nilly without understanding what's really going on. Just like anyting else, you can use an autotrace feature intelligently or...well...not.
You have options. Illustrator provides an auto-trapping feature. Read up on it in the documentation so you understand what it's all about. Alternatively, you can expand the results of your autotrace, select all the black linework and apply a composite color that includes 100% K and reasonable percentages of C, M, and Y (a so-called "rich black"). Or,depending on the artwork and the desired results, you may consider doing the autotrace as centerlines so you have stroked paths, not just filled paths for the linework. That way, using the flood fill (so called LivePaint) will cause the auto-created fill objects to extend to the paths, not just to the edges of their strokes. Then set the linework to overprint.
At any rate, if you are doing this professionally, you need to read up on the principles and practices of trapping and color separation.
JET

Solaris 10 5/08 live upgrade only for customers with serviceplan ?

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Live Upgrade 2.0 (from Sol8 K23 to Sol9 K05

Installed LU 2.0 from solaris 9 CDs
Created a new BE (= copy of my Sol8 K23)
Start upgrade on my inactiive BE to Sol9
insert Solaris 9 CD 1of2
luupgrade -u -n <INACT_BE> -s /cdrom/sol_9_403_sparc/s0
--> runs fine
eject cdrom
insert Solaris 9 CD 2of2
luupgrade -i -n <INACT_BE> -s /cdrom/sol_9_405_sparc_2 -O '-nodisplay'
After a few questions, the upgrade starts,
it first upgrade Live Upgrade ok,
then it start upgrading Solaris,
it than fails .
I checked the logs on the <INACT_BE> and found in
/var/sadm/install/logs/Solaris_9_pacjages...
it failed on installing SUNWnsm (Netscape 7) because already installed !!
It is right that I had SUNWnsm on my Solaris 8 system!!
Why is this causing LU to fail ?
It should just skip that package and go to the next
For the sake of it I deinstalled netscape 7 of my <INACT_BE> using pkgrm -R
I then restarted the LU using CD 2of2 , now it goes further but fails on package SUNWjhrt (java) which also existed !!
Do I miss something or is LU just unusable ??Thanks

Fred,
I personally have never read that caveat, what is recommended is to always run the same version on components that use the same firmware bundle, in other words.... For a B series upgrade, you need the Infraestruture bundle (include firmware for Fabric Interconnects, IOMs and UCSM) and also need the Server bundle (which includes the firmware for the CIMC, BIOS and Adapter).
Bottom line, the recommendation is to run exactly the same version for components that use firmware that come from the same bundle BUT, UCSM 2.1 introduces an enhancement: "Mixed version support (for infra and server bundles firmware) " wich allows the combination of SOME infraestructure bundles with some server bundles.
http://www.cisco.com/en/US/docs/unified_computing/ucs/release/notes/UCS_28313.html#wp58530 << Look for
"Operational enhancements"
These are the posible configurations I am aware of:
2.1(1f) infrastructure and 2.0(5a)+ server firmware
2.1(2a) infrastructure and 2.1(1f)+ server firmware
I hope that helps.
Rate ALL helpful answers.
-Kenny

Sparse zones live upgrade

Hi
I have problem with live upgrade on solaris 10 9/10 to 8/11 on sparse zone.
The installation on global zone is good but sparse zone cannnot boot because zonepath changed.
bash-3.2# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- pbspfox1 installed /zoneprod/pbspfox1-s10u10-baseline native excl
the initial path is /zoneprod/pbspfox1
#zfs list
zoneprod/pbspfox1@s10u10-baseline 22.4M - 2.18G -
zoneprod/pbspfox1-s10u10-baseline
# luactivate zoneprod/pbspfox1@s10u10-baseline
ERROR: The boot environment Name <zoneprod/pbspfox1@s10u10-baseline> is too long - a BE name may contain no more than 30 characters.
ERROR: Unable to activate boot environment <zoneprod/pbspfox1@s10u10-baseline>.
how to upgrade pbspfox1?
Please help
Walter

I'm not exactly sure what happened here but the zone name doesn't change. If the zone patch is wrong, I'd try using zonecfg to change the zone path to the proper value and then boot the zone normally.
zonecfg -z pbspfox1
set zonepath=/zone/pbspfox1 (or whatever is the proper path)
verify
commit
exit
zoneadm -z pbspfox1 boot
If the zone didn't get properly updated, you might be able to update it by detaching the zone:
zoneadm -z pbspfox1 detach
and doing an update reattach
zoneadm -z pbspfox1 attach -u
Disclaimer: All of the above was done from memory without testing, I may have gotten some things wrong.
Hopefully this will help. I've had similar issues in the past but I'm not sure I've had exactly the same problem so I can't tell for sure whether this will help you or not. It is what I'd try. Of course, try to avoid getting yourself into a position where you can't back something out if necessary. This kind of thing can be messy and may require more than one try. If a remember correctly there were some issues with the live upgrade software as shipped with Solaris 10 8/11. I'd get it patched up to current levels ASAP to avoid additional issues.

DiskSuite and Live Upgrade 2.0

Similar Messages

Maybe you are looking for