I have a build machine with snv_100a, and I want to upgrade it to
snv_104. It's UFS root, but it does have a ZFS pool with some ZFS
filesystems on it.
I first installed the snv_104 LU packages, then tried to rename an old BE:
# lurename -e snv_89 -n snv_104
This produced
Renaming boot environment <snv_89> to <snv_104>.
Changing the name of BE in the BE definition file.
Changing the name of BE in configuration file.
Updating compare databases on boot environment <snv_104>.
INFORMATION: Skipping update of boot environment <snv_104>: not configured
properly.
Changing the name of BE in Internal Configuration Files.
Propagating the boot environment name change to all BEs.
Boot environment <snv_89> renamed to <snv_104>.
I didn't like the looks of that INFORMATION line, so I thought I would
delete the BE and recreate it. But that doesn't work:
# ludelete snv_104
ERROR: mount: /builds/akolb/nitro-gate: No such file or directory
ERROR: cannot mount mount point
</.alt.tmp.b-J9b.mnt/builds/akolb/nitro-gate> device </builds/akolb/nitro-gate>
ERROR: failed to mount file system </builds/akolb/nitro-gate> on
</.alt.tmp.b-J9b.mnt/builds/akolb/nitro-gate>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.1>
ERROR: Cannot mount BE <snv_104>.
Unable to delete boot environment.
I think there used to be a ZFS filesystem /builds/akolb/nitro-gate, but
it is gone ("zfs list" does not show it, nor does "mount").
"lumount snv_104" works.
What do I do now? The system is stomper.sfbay, in case anyone internal
wants to poke at it.
thanks,
mike
