vinum root issue on 5.3-Beta2
Chad Ziccardi
ziccardi at digitalfreaks.org
Wed Sep 1 08:32:30 PDT 2004
begin quote from Chad Ziccardi <ziccardi at digitalfreaks.org> written
2004-08-31:
Problem fixed using geom_vinum instead of the vinum module, and switching
everything over to gvinum.
> just an additional note to this, if I boot it the 1st way, and add a new set
> of drives (mirror -n m-usr -v /dev/ad0s1d /dev/ad2s1d) it does that one
> correctly, again.. until I reboot using that setup, which the vinumdriveX
> associated with /dev/ad2 all show referenced.
>
> begin quote from Chad Ziccardi <ziccardi at digitalfreaks.org> written
> 2004-08-31:
>
>>
>> I'm working on setting up a mirrored root filesystem as explained in:
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html
>>
>> I've gotten it to boot then noticed something broken about it on my setup.
>>
>> More info on my setup is at the bottom of this message.
>>
>> If it boots to the vinum partition it does not properly load vinum.
>> How to explain that better..
>> booting normal as described in the handbook (loader.conf settings)
>> it appears to only read ad0s1h for data, thus never fully comes up.
>>
>> I get among the various warnings (a slice is missing!)
>>
>> vinum: incompatible sector sizes. m-root.p1 has 0, m-root has 512.
>> Ignored.
>> Mounting root from ufs:/dev/vinum/m-root
>> vinum -> ld
>> D vinumdrive0 State: up /dev/ad0s1h A: 0/1023 MB (0%)
>> D vinumdrive1 State: referenced unknown A: 0/0 MB
>> since it can't see vinumdrive1 the plex and subdisks are faulty.
>>
>>
>>
>>
>> However booting to the a slice without using vinum (removed from
>> loader.conf)
>> booted up on ad0s1a(or ad0s1h)(half of the mirror)
>>
>> then doing vinum start after logging in I get:
>>
>> vinum: reading configuration from /dev/ad2s1h
>> vinum: updating configuration from /dev/ad0s1h
>> Aug 31 05:55:06 kernel: vinum: reading configuration from /dev/ad2s1h
>> Aug 31 05:55:06 kernel: vinum: updating configuration from /dev/ad0s1h
>>
>> vinum -> ld
>> D vinumdrive1 State: up /dev/ad2s1h A: 0/1023 MB (0%)
>> D vinumdrive0 State: up /dev/ad0s1h A: 0/1023 MB (0%)
>>
>>
>>
>> Is this a known issue? Is there something wrong with how I've set it up?
--
Chad Ziccardi, Professional Slacker cz at digitalfreaks.org
"Some cause happiness wherever they go; others whenever they go."
More information about the freebsd-current
mailing list