i forgot an essential env var: BE_PRINT_ERR, that gives me the solution: # BE_PRINT_ERR=true beadm create opensolaris-b134 be_get_uuid: failed to get uuid property from BE root dataset user properties. be_find_active_zone_root: failed to find active zone root in zonepath dataset rpool/zones/template_zone be_copy_zones: failed to find active zone root for zone template_zone in BE opensolaris-2 be_copy: failed to process zones be_copy: destroying partially created boot environment be_destroy_zone_roots: failed to destroy zone root container dataset (rpool/zones/template_zone/ROOT): Invalid argument Unable to create opensolaris-b134. no active zone root
the problem is related to a broken zone. After deleting it, everything works fine don't forget BE_PRINT_ERR in case of problem! 2010/12/23 gerard henry <solar...@gmail.com> > that's what i tried, and it failed, due to the fllowing bug: > *Zones Cloned by Using zoneadm clone Can Cause a Snapshot Name Collision > When You Activate a Boot Environment (10990) > > The use of the zoneadm clone command to create zones can cause a snapshot > name collision, which can lead to a failure or an infinite loop when you > activate a boot environment. Although this bug has been fixed in this > release, you may encounter this issue while upgrading from OpenSolaris > 2009.06 to the Oracle Solaris 11 Express release. > > Workaround: Before using image-update to update your system to the Oracle > Solaris 11 Express release, run the zoneadm detach command for each zone in > the OpenSolaris 2009.06 boot environment. > > To reattach the zones: > > 1. > > Update the image. > > # pkg image-update > > 2. > > Boot into the boot environment that was created by image-update. > 3. > > Run the zoneadm attach -u command for each zone in the new boot > environment. > > Note > > After using this workaround, the boot environment you updated from no > longer has zones attached to it. * > > > now, even with the zones re-attached, and booted (and working fine), i'm > unable to create a new be. > > > 2010/12/23 Paul van der Zwan <pa...@vanderzwan.org> > > >> On 23 dec 2010, at 18:59, gerard henry wrote: >> >> hello all, >> i've os2009.06, and i'm in the process to migrate to b134->s11X. As i've >> zones, i detached them and ran "pkg image-update". But it failed without >> reason: >> pkg: Unable to clone the current boot environment. >> >> >> Do not detach them before running pkg image-update but detach/attach -u >> them after rebooting the new be. >> The documentation ( >> http://docs.sun.com/app/docs/doc/821-1460/gclkx?l=en&a=view ) says: >> Currently, ipkg zones employ manual syncing. The zones do not >> automatically update when pkg image-update is executed on the system. You >> must manually update the zones after rebooting to keep them in sync with the >> global zone. >> To manually update zones after rebooting, use thezoneadm detach and attach >> commands with the -u option. >> Run pkg image-update and reboot onto the new image, then detach the zone >> and use zoneadm attach with the -u option. See “About Migrating a Zone” >> on page 294 for more information on these commands. >> >> >> >> Paul >> >> i tried to create a new BE, and it failed too: >> he...@antigone:/# beadm create opensolaris-b134 >> Unable to create opensolaris-b134. >> no active zone root >> >> The machine is in production, so i don't understand the message "no active >> zone root" ? >> Filesystem Size Used Avail Use% Mounted on >> rpool/ROOT/opensolaris-2 >> 22G 6.6G 16G 31% / >> swap 5.7G 352K 5.7G 1% /etc/svc/volatile >> /usr/lib/libc/libc_hwcap1.so.1 >> 22G 6.6G 16G 31% /lib/libc.so.1 >> swap 5.7G 20K 5.7G 1% /tmp >> swap 5.7G 44K 5.7G 1% /var/run >> rpool/export 16G 48K 16G 1% /export >> >> >> thanks in advance for help, >> >> gerard >> _______________________________________________ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org >> >> >> >
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
