On Oct 10, 2011, at 2:45 PM, Seth Goldberg wrote: > >>> The beadm command tries to clean up after itself. Try mounting the root >>> dataset for the solaris-1 BE directly, then, i.e.: >>> >>> zfs mount -o mountpoint=/a rpool/ROOT/solaris-1 >> >> There is no solaris-1 BE, >> >> % beadm list >> BE Active Mountpoint Space Policy Created >> -- ------ ---------- ----- ------ ------- >> solaris NR / 18.32G static 2011-10-07 10:17 >> >> % zfs mount -o mountpoint=/a rpool/ROOT/solaris-1 >> cannot open 'rpool/ROOT/solaris-1': dataset does not exist >> >> If you would like to examine the system I can send you a pointer offline. > > Sorry about that -- beadm removed the solaris-1 BE due to that error. You > can try manually creating a new BE (named whatever you want),
Not working, same error - % beadm create testBE be_mount_callback: failed to mount dataset rpool/ROOT/testBE/var at /tmp/.be.U4ayqj/var: directory is not empty be_mount: failed to mount BE (testBE) on /tmp/.be.U4ayqj be_copy: failed to mount newly created BE be_copy: destroying partially created boot environment be_get_uuid: failed to get uuid property from BE root dataset user properties. Unable to create testBE. Unable to find message for error code: 1 Any other ideas? thanks Dave > THEN mounting its root dataset and examining /var (since that's effectively > what pkg will be doing when doing the installation). > > Thanks, > --S --- David Sechrest Phone: (408)276-5800 x15800 Systems Management Email: [email protected] Oracle Corporation _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
