Re: vinum root issue on 5.3-Beta2

From: Chad Ziccardi <ziccardi_at_digitalfreaks.org>
Date: Tue, 31 Aug 2004 21:18:53 -0400 (EDT)
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?
>
>
>
>
> info from dmesg:
> ----------------
> FreeBSD 5.3-BETA2 #0: Tue Aug 31 01:21:06 UTC 2004
>    root_at_:/usr/obj/usr/src/sys/ARBITOR
> ...
> ad0: 157066MB <HDS722516VLAT80/V34OA63A> [319120/16/63] at ata0-master UDMA66
> ATAPI_RESET time = 34920us
> ata1-master: DMA limited to UDMA33, non-ATA66 cable or device
> ad2: 157066MB <HDS722516VLAT80/V34OA63A> [319120/16/63] at ata1-master UDMA33
> acd0: CDROM <CD-ROM CDU701/1.0f> at ata1-slave PIO4
>
>
>
> disklabels:
> -----------
> # /dev/ad0s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>  a:  2096871      281    4.2BSD     2048 16384 11761
>  b:  4999480 316669952      swap
>  c: 321669432        0    unused        0     0         # "raw" part, don't 
> edit
>  d: 16777216  2097152    4.2BSD     2048 16384 28552
>  e:  4194304 18874368    4.2BSD        0     0     0
>  f: 188743680 23068672    4.2BSD        0     0     0
>  g: 104857600 211812352    4.2BSD        0     0     0
>  h:  2097136       16     vinum
>
> # /dev/ad2s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>  a:  2096871      281    4.2BSD     2048 16384 11761
>  b:  4999480 316669952      swap
>  c: 321669432        0    unused        0     0         # "raw" part, don't 
> edit
>  d: 16777216  2097152    4.2BSD     2048 16384 28552
>  e:  4194304 18874368    4.2BSD        0     0     0
>  f: 188743680 23068672    4.2BSD        0     0     0
>  g: 104857600 211812352    4.2BSD        0     0     0
>  h:  2097136       16     vinum
>
>
>
>

-- 
Chad Ziccardi, Professional Slacker          cz_at_digitalfreaks.org
"Some cause happiness wherever they go; others whenever they go."
Received on Tue Aug 31 2004 - 23:19:14 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:09 UTC