[OpenIndiana-discuss] Problem with pkg image-update

[Mark Creamer]

Just to finish up with this issue, after a while I looked again, and now
oi151a5 was shown "NR" in beadm list. So I went ahead with the reboot, took
it back to before the upgrade to oi151a6, and now I can access my zones
again. Guess I won't be updating this server again any time
soon...definitely cannot risk not being able to start those zones

Mark

On Thu, Sep 13, 2012 at 11:26 PM, Yuri Pankov <yuri.pankov at gmail.com> wrote:

> On Thu, 13 Sep 2012 23:21:30 -0400, Mark Creamer wrote:
>
>> My server is currently at oi151a5, and it's been about a month, so I ran
>> pkg image-update to check on available updates. As expected, the packages
>> from oi151a6 were available, so I let it run. When the installation was
>> complete, I noticed it said that pkg could not activate the new BE. I ran
>> beadm list, and saw all of the BEs listed, with the one I'm in now marked
>> N, and the new one marked R. The new one shows a mount point under
>> /tmp/.....
>>
>> Because I saw that it said it could not activate the new BE, I decided not
>> to reboot because I wasn't sure what would happen to my old BE. I then
>> attempted beadm activate opensolaris-6 which is my current running BE, the
>> one marked N in beadm list. It said it could not promote the BE.
>>
>> I'm leaving it be until I can get some advice on what to do. For example,
>> should I destroy the latest BE that was just created but could not be
>> activated?
>>
>
> Not really related to your question, but try setting BE_PRINT_ERR
> environment variable to "true" to check why beadm is unable to activate new
> BE.
>
> ______________________________**_________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss at openindiana.org>
> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
>



-- 
Mark