Re: vinum problems with todays current

On Friday,  8 August 2003 at 16:04:05 +0200, Rob wrote:
> Greg 'groggy' Lehey wrote:
>> On Tuesday,  5 August 2003 at 22:21:41 +0200, Rob wrote:
>>> Poul-Henning Kamp wrote:
>>>> In message <3F300441.1040904_at_debank.tv>, Rob writes:
>>>>
>>>>> Hi all,
>>>>>
>>>>> After cvs'upping (about 12 hours ago) and building world/kernel vinum
>>>>> stopped working. It does show my two disks but nothing more. I also
>>>>> get an error message right after the bootloader:
>>>>
>>>> Can you try this patch:
>>>
>>> I noticed I had an older version of spec_vnops.c (1.205), so I
>>> cvsupped again and build kernel, this gave me the same msgbuf error,
>>> but with different values. Then I applied your patch and the error
>>> messgae disapeared, but still my vinum doesn't come up.
>>
>> Can I assume that this is related to GEOM, and not to Vinum?
>
> After investigating a little further today, I found the config info
> on the drives to be mangled.
>
> ----------------------------------------------------------------------
> # rm -f log
> # for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
> (dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) >> log
> done
> # cat log
> IN VINOx-server.debank.tvbC<>c3??Z${m5?
> IN VINOx-server.debank.tvaC<><3?WPZ${m5?
> ----------------------------------------------------------------------
>
> I guess the drives can't be started again unless I have the
> parameters which I used during install (please say I'm wrong).

Hmm.  That doesn't look good.  No trace of the original config?

Greg
--
See complete headers for address and phone numbers