> Seems like upgrading from b126 to b127 will have the
> same problem.
Yes, good point. I provided a blurb about this issue, here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Live_Upgrade_Problem_.28Starting_in_Nevada.2C_build_125.29
Its a good idea to review this pa
Seems like upgrading from b126 to b127 will have the same problem.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>On Thu, 5 Nov 2009, Chris Du wrote:
>
>> I think I finally see what you mean.
>>
>> # luactivate b126
>> System has findroot enabled GRUB
>> ERROR: Unable to determine the configuration of the current boot environment
>> .
>
>Hmm. Does this mean that lupgrading from b121 to b126 will also fail
I just finished the upgrade.
detach one disk from the mirror, then luactivate b126 and init 6, after it
reboots, attach the disk to the mirror again, all went smoothly.
Thanks a lot.
--
This message posted from opensolaris.org
___
zfs-discuss mailing
On Thu, Nov 05, 2009 at 03:39:56PM -0800, Rich Teer wrote:
> On Thu, 5 Nov 2009, Chris Du wrote:
>
> > I think I finally see what you mean.
> >
> > # luactivate b126
> > System has findroot enabled GRUB
> > ERROR: Unable to determine the configuration of the current boot
> > environment .
>
> H
steps
for modifying LU scripts. Or, you detach your secondary mirrored disk,
run the LU operation, reattach the secondary mirrored disk.
The CR is 6894189.
Cindy
- Original Message -
From: Rich Teer
Date: Thursday, November 5, 2009 4:47 pm
Subject: Re: [zfs-discuss] heads up on SXCE bui
On Thu, Nov 05, 2009 at 01:01:54PM -0800, Chris Du wrote:
> I think I finally see what you mean.
>
> # luactivate b126
> System has findroot enabled GRUB
> ERROR: Unable to determine the configuration of the current boot environment
> .
A possible solution was posted in the thread:
http://open
On Thu, 5 Nov 2009, Chris Du wrote:
> I think I finally see what you mean.
>
> # luactivate b126
> System has findroot enabled GRUB
> ERROR: Unable to determine the configuration of the current boot environment
> .
Hmm. Does this mean that lupgrading from b121 to b126 will also fail,
or is the
I think I finally see what you mean.
# luactivate b126
System has findroot enabled GRUB
ERROR: Unable to determine the configuration of the current boot environment
.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@
What luupgrade do you use?
I uninstall lu package in current build first, then install new lu package in
the verion to upgrade.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.
Hi,
On Mon, Oct 19, 2009 at 05:03:18PM -0600, Cindy Swearingen wrote:
> Currently, the device naming changes in build 125 mean that you cannot
> use Solaris Live Upgrade to upgrade or patch a ZFS root dataset in a
> mirrored root pool.
> [...]
Just ran into this yesterday... The change to get thin
Probably if you try to use any LU operation after you have upgraded to
build 125.
cs
On 10/23/09 16:18, Chris Du wrote:
Sorry, do you mean luupgrade from previous versions or from 125 to future
versions?
I luupgrade from 124 to 125 with mirrored root pool and everything is working
fine.
___
Sorry, do you mean luupgrade from previous versions or from 125 to future
versions?
I luupgrade from 124 to 125 with mirrored root pool and everything is working
fine.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discus
Is there a CR yet for this?
Thanks
Karl
Cindy Swearingen wrote:
Hi everyone,
Currently, the device naming changes in build 125 mean that you cannot
use Solaris Live Upgrade to upgrade or patch a ZFS root dataset in a
mirrored root pool.
If you are considering this release for the ZFS log dev
14 matches
Mail list logo
