Luactivate Error Unable To Mount The Boot Environment
Contents |
» Common Live Upgrade Problems By User12611829-Oracle on Jun 30, 2011 As I have worked with customers deploying Live Upgrade in their environments, several problems seem to surface over error: unable to determine the configuration of the current boot environment and over. With this blog article, I will try to collect these troubles, luconfig error could not analyze filesystem mounted at as well as suggest some workarounds. If this sounds like the beginnings of a Wiki, you would be right. luactivate not working At present, there is not enough material for one, so we will use this blog for the time being. I do expect new material to be posted on occasion, so if you ludelete force wish to bookmark it for future reference, a permanent link can be found here. To help with your navigation, here is an index of the common problems. lucreate(1M) copies a ZFS root rather than making a clone luupgrade(1M) and the Solaris autoregistration file Watch out for an ever growing /var/tmp Without any further delay, here are some common Live Upgrade problems. Live Upgrade copies
Solaris Live Upgrade Cheat Sheet
over ZFS root clone This was introduced in Solaris 10 10/09 (u8) and the root of the problem is a duplicate entry in the source boot environments ICF configuration file. Prior to u8, a ZFS root file system was not included in /etc/vfstab, since the mount is implicit at boot time. Starting with u8, the root file system is included in /etc/vfstab, and when the boot environment is scanned to create the ICF file, a duplicate entry is recorded. Here's what the error looks like. # lucreate -n s10u9-baseline Checking GRUB menu... System has findroot enabled GRUB Analyzing system configuration. Comparing source boot environment 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. Creating configuration for boot environment . Source boot environment is . Creating boot environment . Creating file systems on boot environment . Creating file system for > in zone on . The error indicator -----> /usr/lib/lu/lumkfs: test: unknown operator zfs Populating file systems on boot environment . Checking selection
By user12625760 on May 27, 2008 It took a bit of work but I managed to pursuade my old laptop to live upgrade to nevada build 90 with ZFS root. First I upgraded to build 90 on ufs
Solaris Ludelete
and then created a BE on zfs. The reason for the two step approach was error: all datasets within a be must have the canmount value set to noauto. to reduce the risk a bit. Bear in mind this is all new in build 90 and I am not an expert on ludelete example the inner workings of live upgrade. So there are no guarantees. The upgrade failed at the last minute with this error: ERROR: File not found in top level dataset for BE
for a more or less long time. Also it allows one to switch back to the previous state, when something went wrong, without the http://iks.cs.ovgu.de/~elkner/luc/lutrouble.html neeed to backuot patches from the "male"functioning boot environment. The main steps for LiveUpgrade are create a snapshot aka alternative boot environment (ABE) from the current running system applying the changes http://wiki.pressy.net/LiveUpgrade (upgrade or patches) to the ABE instead of the currently running system activate the ABE boot into the new ABE by 'init 6' However, especially when zones are used, LiveUpgrade unable to has often issues which require you to manually fix the problems until they get fixed in the main release. This page tries to show most common problems and how to resolve them. Debugging lucreate, lumount, luumount, luactivate, ludelete If one of the lu* commands fails, the best thing to do is to find out what the command in question actually does. The luactivate error unable follwing receipt shows a way how to get all information one usually needs to find the cause of the problem and finally to resolve it. + tcsh setenv SNVR b103 setenv NBE snv_$SNVR setenv CD /net/install/pool1/install/`uname -p`/Solaris_11_$SNVR setenv JUMPDIR /net/install/pool1/install/jumpstart setenv RPOOL `df / | grep -v ^Filesystem | cut -f1 -d/` setenv ERR err.${NBE}.log setenv OUT out.${NBE}.log setenv DBG dbg.${NBE}.log setenv TRC trc.${NBE}.log setenv LU_DEBUG_OVERRIDE 11 echo 'proc:::exec-success { \ printf("%d\t%s\n",timestamp,curpsinfo->pr_psargs); \ }' >/tmp/exe.d setenv DTRACE "dtrace -s /tmp/exe.d -o $TRC -c" setenv GAWK "gawk -f /local/misc/etc/tsortd.gawk" cd /var/tmp rm -f $TRC $DBG $OUT $ERR $DTRACE "lucreate -n $NBE -p $RPOOL -l $ERR -o $OUT" |& tee $DBG $GAWK $TRC >lucreate.${TRC} rm $TRC; mv $DBG lucreate.${DBG}; mv $OUT lucreate.${OUT}; mv $ERR lucreate.${ERR} $DTRACE "lumount -l $ERR -o $OUT $NBE /mnt" |& tee $DBG $GAWK $TRC >lumount.${TRC} rm $TRC; mv $DBG lumount.${DBG}; mv $OUT lumount.${OUT}; mv $ERR lumount.${ERR} $DTRACE "luumount -l $ERR -o $OUT $NBE" |& tee $DBG $GAWK $TRC >luumount.${TRC} rm $TRC; mv $DBG luumount.${DBG}; mv $OUT luumount.${OUT}; mv $ERR luumount.${ERR} $DTRACE "luupgrade -u -n $NBE -s $CD -j /var/tmp/profile.$SNVR
Patch the Boot Environment 1.5 Activate the new BE 2 LU for ZFS/UFS Migration 3 MIRROR AFTER UFS TO ZFS 4 LU to a mirror 5 LU using a Mirror preserving DATA 6 Issues LiveUpgrade You will nedd some special patches, see InfoDoc 206844 (formerly 72099) Prepair the server # pkgrm SUNWlucfg SUNWluu SUNWlur [SUNWluzone] # cd