This is really just an FYI since I've worked around this myself. I have a machine running snv_42 that I'm trying to upgrade to snv_44. I added the liveupgrade packages from snv_44, deleted my old second BE (did some resizing or partitions in format(1m)) and attempted to create the new BE:
ardbeg:pts/4# lucreate -n snv_44 -m /:c1t0d0s3:ufs Discovering physical storage devices Discovering logical storage devices Cross referencing storage devices with boot environment configurations Determining types of file systems supported Validating file system requests The device name <c1t0d0s3> expands to device path </dev/dsk/c1t0d0s3> Preparing logical storage devices Preparing physical storage devices Configuring physical storage devices Configuring logical storage devices Analyzing system configuration. Comparing source boot environment <snv_42> 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. Searching /dev for possible boot environment filesystem devices Updating system configuration files. The device </dev/dsk/c1t0d0s3> is not a root device for any boot environment. Creating configuration for boot environment <snv_44>. Source boot environment is <snv_42>. Creating boot environment <snv_44>. Checking for GRUB menu on boot environment <snv_44>. The boot environment <snv_44> does not contain the GRUB menu. Creating file systems on boot environment <snv_44>. Creating <ufs> file system for </> on </dev/dsk/c1t0d0s3>. Mounting file systems for boot environment <snv_44>. Calculating required sizes of file systems for boot environment <snv_44>. Populating file systems on boot environment <snv_44>. Checking selection integrity. Integrity check OK. Populating contents of mount point </>. Copying. cp: cannot create /.alt.tmp.b-FK.mnt/lib/libc.so.1: No such file or directory WARNING: The file </tmp/lucopy.errors.2284> contains a list of <1> potential problems (issues) that were encountered while populating boot environment <snv_44>. INFORMATION: You must review the issues listed in </tmp/lucopy.errors.2284> 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 <snv_44>. Creating shared file system mount points. Creating compare databases for boot environment <snv_44>. Creating compare database for file system </var>. Creating compare database for file system </>. Making boot environment <snv_44> bootable. The update of the vfstab file on the ABE failed. ERROR: Unable to configure /etc/vfstab file on ABE <snv_44>: cannot make ABE bootable. Making the ABE <snv_44> bootable FAILED. ERROR: Unable to make boot environment <snv_44> bootable. ERROR: Unable to populate file systems on boot environment <snv_44>. ERROR: Cannot make file systems for boot environment <snv_44>. ardbeg:pts/4# lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ ---------- snv_42 yes yes yes no - snv_44 no no no yes - ardbeg:pts/4# lufslist snv_44 ERROR: No such file or directory: cannot open </etc/lu/ICF.2> mode <r> ERROR: individual boot environment configuration file does not exist - the specified boot environment is not configured properly ERROR: cannot access local configuration file for boot environment <snv_44> ERROR: cannot determine file system configuration for boot environment <snv_44> ERROR: cannot determine file system list of boot environment <snv_44> ardbeg:pts/4# ludelete snv_44 ERROR: No such file or directory: cannot stat </etc/lu/ICF.2> ERROR: cannot use </etc/lu/ICF.2> as an icf file ERROR: Cannot mount BE <snv_44>. Unable to delete boot environment. ardbeg:pts/4# lucreate -n snv_44 -m /:c1t0d0s3:ufs ERROR: new boot environment <snv_44> already exists ERROR: cannot create new boot environment using options provided As you can see the lucreate failed, then the ludelete won't work and lucreate won't work either so it is stuck in limboland. I got out of the can't create can't delete cycle by manually creating an /etc/lu/ICF.2 file with the content for what would have been the snv_44 BE in it. That allowed me to run ludelete and then lucreate again. It seems that from the error messages this was yet again caused by the lofs mounts of libc - which I still maintain was a REALLY bad solution to this problem ( ere have been so many issues in various parts of the system as a result of this). -- Darren J Moffat
