From owner-freebsd-current@FreeBSD.ORG Fri Aug 8 07:06:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCA7D37B401; Fri, 8 Aug 2003 07:06:09 -0700 (PDT) Received: from haha.debank.tv (c92069.upc-c.chello.nl [212.187.92.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8655643FD7; Fri, 8 Aug 2003 07:06:03 -0700 (PDT) (envelope-from rob@debank.tv) Received: from debank.tv (X-server.debank.tv [192.168.1.69]) by haha.debank.tv (8.12.9/8.12.9) with ESMTP id h78E5xlf033138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Aug 2003 16:06:01 +0200 (CEST) (envelope-from rob@debank.tv) Message-ID: <3F33ADD5.50607@debank.tv> Date: Fri, 08 Aug 2003 16:04:05 +0200 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <34414.1060112010@critter.freebsd.dk> <3F3011D5.7020306@debank.tv> <20030805230502.GX95375@wantadilla.lemis.com> In-Reply-To: <20030805230502.GX95375@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: Poul-Henning Kamp cc: freebsd-current@FreeBSD.org Subject: Re: vinum problems with todays current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2003 14:06:10 -0000 Greg 'groggy' Lehey wrote: > On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote: > >>Poul-Henning Kamp wrote: >> >>>In message <3F300441.1040904@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? > > Greg > -- > See complete headers for address and phone numbers 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). Rob Evers --