On 6/23/10 4:29 AM, Brian Nitz wrote:
I saw a problem while upgrading from build 140 to 141 where beadm
activate {build141BE} failed because installgrub failed:
# BE_PRINT_ERR=true beadm activate opensolarismigi-4
be_do_installgrub: installgrub failed for device c5t0d0s0.
Unable to activate open
On 5/5/10 10:22 AM, Christian Thalinger wrote:
On Wed, 2010-05-05 at 09:45 -0600, Evan Layton wrote:
No that doesn't appear like an EFI label. So it appears that ZFS
is seeing something there that it's interpreting as an EFI label.
Then the command to set the bootfs property is fail
On 5/5/10 1:44 AM, Christian Thalinger wrote:
On Tue, 2010-05-04 at 16:19 -0600, Evan Layton wrote:
Can you try the following and see if it really thinks it's an EFI lable?
# dd if=/dev/dsk/c12t0d0s2 of=x skip=512 bs=1 count=10
# cat x
This may help us determine if this is another instan
It turns out that the problem that was being hit by Kristin was bug
10990 which is caused by using zoneadm cone to clone a zone. This
causes a snapshot name collision that we where not catching due to
bug 11062.
To work around this issue there are two possibilites:
1) delete zones that have been
Hi Luca,
The bootfs entry is needed if you have more than one BE and wish to boot to a
BE
that is not the default BE set in the "bootfs" property of the root pool. This
is why beadm adds this entry, it enables booting to BE's other than the default
by overriding the "bootfs" property of the ro
Evan Layton wrote:
> Rob McMahon wrote:
>> Evan Layton wrote:
>>> Can you set BE_PRINT_ERR to see if we can get a bit more information
>>> on what going on here? (export BE_PRINT_ERR=true)
>>> It would also be helpful to see what "zpool status&
Rob McMahon wrote:
> Evan Layton wrote:
>> Can you set BE_PRINT_ERR to see if we can get a bit more information
>> on what going on here? (export BE_PRINT_ERR=true)
>> It would also be helpful to see what "zpool status" shows as well as
>> what's in
