Problem with luactivate going from S10 x86 u6 back to S10 x86 u5 ...

Question

Solaris wizards:
I recently used Live Upgrade to migrate from Solaris 10 x86 u5 (May 08) to Solaris 10 x86 u6 (Oct 08).
That seemed to work without a hitch .... but now I'd like to go back to the other boot environment and am encountering problems.
While I'm using the s10Oct08 boot environment, lustatus returns:
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
s10May08 yes no no yes -
s10Oct08 yes yes yes no -
Then, when I issue the command:
luactivate s10May08
I get:
System has findroot enabled GRUB
Generating boot-sign, partition and slice information for PBE <s10Oct08>
WARNING: <3> packages failed to install properly on boot environment <s10May08>.INFORMATION: </var/sadm/system/data/upgrade_failed_pkgadds> on boot
environment <s10May08> contains a list of packages that failed to upgrade
or install properly. Review the file before you reboot the system to
determine if any additional system maintenance is required.
Generating boot-sign for ABE <s10May08>
/dev/rdks/c3t2d0s0: No such file or directory
Unknown_fstyp (no matches)
ERROR: Failed to get fstype for BE <s10May08>. Cannot operate on file </etc/bootsign>
/dev/rdks/c3t2d0s0: No such file or directory
Unknown_fstyp (no matches)
ERROR: Failed to get fstype for BE <s10May08>. Cannot operate on file </etc/bootsign>
ERROR: Failed to create boot sign backup for BE <s10May08>
/dev/rdks/c3t2d0s0: No such file or directory
Unknown_fstyp (no matches)
ERROR: Failed to get fstype for BE <s10May08>. Cannot operate on file </boot/grub/bootsign/BE_s10May08>
ERROR: Failed to write boot signature </boot/grub/bootsign/BE_s10May08> to top level dataset in BE <s10May08>
ERROR: Cannot generate boot signature for ABE <s10May08>
ERROR: Unable to determine the configuration of the target boot environment <s10May08>.
It seems clear that the problem is that it is looking for /dev/rdks/c3t2d0s0 as the new boot environment
and I'm guessing that it should be /dev/rdsk/c3t2d0s0 ...
While that was likely a typo of mine in during the original 'lucreate' or 'luupgrade' commands .... I can't find the file where that is stored.
The closest that I can determine by myself is looking in the luactivate script ...
It appears to me that I am getting the wrong value of gac_beMntpt when I try to determine the new mount points. The relevant portion (I think) of the luactivate script is:
# Get the BE block boot device for the ABE.
forceFlag=""
[ -n "${flag_u}" ] && forceFlag="-f"
gac_beMntpt="`LU_OUTPUT_FORMAT=text ${LUBIN}/lumount ${forceFlag} \"${gac_beName}\" 2>${TMP_RESULT_FILE}`"
if [ "$?" -ne "0" -o -z "${gac_beMntpt}" ] ; then
[ -s "${TMP_RESULT_FILE}" ] && ${LUPRINTF} -elp2 '%R' < "${TMP_RESULT_FILE}"
/bin/rm -f "${TMP_RESULT_FILE}"
return 1
fi
/bin/rm -f "${TMP_RESULT_FILE}"
${LUPRINTF} -lp2D - "`gettext 'Mounted ABE <%s> at <%s>.'`" "${gac_beName}" "${gac_beMntpt}"
I'm guessing that 'lumount ${gac_beName} looks in a file to determine what mount point should be mounted ...
but I can't seem to get further than that.
Does anyone know where I should look to find where luactivate looks to find the mount point of the alternate boot environment because, I think, it has /dev/rdks/something instead of /dev/rdsk/something ....
Thanks for any insights or suggestions ...
John

Answer 1

Sun Solaris Community:
I believe that I have found my ow problem, but thought that I'd share what I learned that was preventing my "luactivate" from working.
It turns out that I had put an entry in /etc/vfstab that mounted my Alternate Boot Environment as /ABE. It was that entry in /etc/vfstab that had the typo .... but apparently also confused the luactivate script.
My erroneous entry was:
/dev/dsk/c3/t2d0s0 /dev/rdks/c3t2d0s0 /ABE ....
So, while I couldn't actually mount that partition as my alternate boot environment on /ABE (because /dev/rdks/... doesn't exist) I had failed to notice this error on this machine.
In any event, correcting that entry both allows me to mount the alternative boot environment on the running system as /ABE if I wish ...
More importantly, 'luactivate Other_Boot_Environment" now works. Of course, for this to work properly, the alternate boot enviroment can't be currently mounted as /ABE ... that entry is just a convenience if I occasionally need to compare things between the current and the alternate boot environments and I'd need to do a 'umount /ABE' before doing the 'luactivate Other_Boot_Environment".
Thanks,
John