Alan Coopersmith wrote: > Shawn Walker wrote: >> On Jun 26, 2009, at 2:01 PM, Malte Hahlbeck wrote: >>> Hi, >>> >>> after the update from 2009.06 to snv_117 succeeded, the new boot >>> environment is still mounted to tmp (see below) and can not be activated. >>> >>> When I try to activate it, I got the following error: >>> >>> $> pfexec beadm activate opensolaris-6 >>> Unable to activate opensolaris-6. >>> Unknown external error. >> >> First, you'll want to try unmounting it. >> >> Then, try: >> BE_PRINT_ERR=true pfexec beadm activate opensolaris-6 > > I'm seeing a similar problem - pkg image-update from 111b to 117 > reported that it was unable to activate the new be, and left it mounted. > > I then got: > > also% env BE_PRINT_ERR=true pfexec beadm umount opensolaris-117 > also% env BE_PRINT_ERR=true pfexec beadm activate opensolaris-117 > be_do_installgrub: installgrub failed for device c8t0d0s0. > Unable to activate opensolaris-117. > Unknown external error. > > This machine is setup to dual boot, and I recently reinstalled the other > side with Fedora 11, so it installed it's own grub and made it's partition > active - I've listed opensolaris in Fedora's grub to chainload. Is that > blocking the installgrub? > >
Do you have a mirrored root? If so one side of it may not be set up correctly for installgrub to work. You can try running installgrub by itself and see what that gives you but it looks like it's a device configuration problem. As for the abysmal error reporting when installgrub fails that's bug 6495 which I hope to have fixed in the near future. -evan
