On Sat, Jan 22, 2011 at 12:55 AM, Ivan Voras wrote:
> On 21/01/2011 14:22, Andrey V. Elsukov wrote:
>>
>> On 21.01.2011 16:03, Ivan Voras wrote:
>>>
>>> On 21/01/2011 13:56, Johan Hendriks wrote:
Ok the funny thing is, i get the same error on 8.1 Release (the corrupt
error), but it
On 21/01/2011 14:22, Andrey V. Elsukov wrote:
On 21.01.2011 16:03, Ivan Voras wrote:
On 21/01/2011 13:56, Johan Hendriks wrote:
Ok the funny thing is, i get the same error on 8.1 Release (the corrupt error),
but it boots,
and all seems to work.
Maybe the boot process was made to be more stan
On 21.01.2011 16:03, Ivan Voras wrote:
> On 21/01/2011 13:56, Johan Hendriks wrote:
>> Ok the funny thing is, i get the same error on 8.1 Release (the corrupt
>> error), but it boots,
>> and all seems to work.
>
> Maybe the boot process was made to be more standard-compliant :)
The most stranges
On 21/01/2011 13:56, Johan Hendriks wrote:
Ok the funny thing is, i get the same error on 8.1 Release (the corrupt error),
but it boots, and all seems to work.
Maybe the boot process was made to be more standard-compliant :)
___
freebsd-stable@free
[mailto:owner-freebsd-sta...@freebsd.org]
Namens Ivan Voras
Verzonden: vrijdag 21 januari 2011 12:19
Aan: freebsd-stable@freebsd.org
Onderwerp: Re: Gpart and gmirror 8.2 from 18 januari
On 19/01/2011 12:30, Johan Hendriks wrote:
> Hello all, i used to have disk configured with gpart and gmirror.
>
>
> I haven't tried it but I think from the GPT specification that it
> records where the secondary table is, so maybe you could do it the
> other way around: first do a gmirror configuration, then create GPT
> partitions within the gmirror device (i.e. on /dev/mirror/gm0, not
> on /dev/ad4).
I'm u
On 19/01/2011 12:30, Johan Hendriks wrote:
Hello all, i used to have disk configured with gpart and gmirror.
But with the latest 8.2, my server will not boot anymore if i label the
disk with gmirror.
Gpart status
Name Status Components
ad4p1 OK ad4
Then i do a gmirror label -v