I have now tried beadm to mount the boot environment and I still get the same "pkg: No image rooted at '/<mntdir>/' " message. I did try booting into maintenance mode (by adding -s at the end of the kernel$ .... line in the menu.lst file of GRUB) but pkg cannot 'fix' the image even in the maintenance mode. It still complains and makes the alternate BE suggestion.
I think I have figured out why it says "no image rooted". It is an old version of pkg (belonging to svn_111b) which cannot identify the new image. I tried to use the pkg command inside the /<mntdir>/ root but it failed. So I booted back to the new environment, cloned it, beadm mounted it, and ran pkg fix -R on the clone. That operation seemed to be successful but after the fix it urged me to report this as a bug at defect.opensolaris.org. Thank you for the beadm suggestion! > Robin Axelsson wrote: > > > Does anyone know how to properly run 'pkg fix' from > an 'alternate' boot > > environment? > > beadm mount <be-to-be-fixed> /mnt > pkg -R /mnt fix > beadm unmount /mnt > e, though, that some of the bugs that prevented the > update from being > completely successful will also make the fix > unsuccessful. If you can get > the new BE to boot at least into single user mode, > then you'll probably be > better off running pkg fix from that environment. > Depending on what needs > ixing, you may need to run "beadm create" to clone > off a new BE and fix > that one after mounting it somewhere. > > Danek > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-d > iscuss > -- This message posted from opensolaris.org
