From owner-freebsd-current@FreeBSD.ORG Fri Oct 7 06:56:10 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 26FC916A41F; Fri, 7 Oct 2005 06:56:10 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from imap1u.univie.ac.at (imap1.unet.univie.ac.at [131.130.1.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9299943D45; Fri, 7 Oct 2005 06:56:09 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben (le.vpn.univie.ac.at [131.130.222.177]) by imap1u.univie.ac.at (8.12.10/8.12.10) with ESMTP id j976t7eK036849 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 7 Oct 2005 08:55:10 +0200 (CEST) Date: Fri, 7 Oct 2005 08:55:01 +0200 From: Lukas Ertl To: Daniel Eriksson In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A605F55D@royal64.emp.zapto.org> Message-ID: References: <4F9C9299A10AE74E89EA580D14AA10A605F55D@royal64.emp.zapto.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: gvinum startup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Oct 2005 06:56:10 -0000 On Fri, 7 Oct 2005, Daniel Eriksson wrote: > One of my servers boot off of SCSI, and has a gvinum array consisting of > 4 x 120GB ATA disks in RAID-0 configuration. When loading gvinum through > "/boot/loader.conf", the tasting of providers seems to be out of whack, > and the array always comes up broken with one subdisk missing. When > loading gvinum manually, the array always comes up properly without any > problems. > > All the individual disks are probed properly during startup, but for > some reason gvinum does not taste all 4 disks if it loads through > "/boot/loader.conf". Interesting... on a fresh CURRENT, the problem should be the other way round... :-) Have you tried setting kern.geom.debugflags=1 at the loader prompt? It might give a hint as to why one disk is missing. thanks, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/