From owner-freebsd-questions@FreeBSD.ORG Thu Oct 16 00:46:58 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AE7E16A4B3 for ; Thu, 16 Oct 2003 00:46:58 -0700 (PDT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id C87EF43F75 for ; Thu, 16 Oct 2003 00:46:54 -0700 (PDT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id C65BA2BD37 for ; Thu, 16 Oct 2003 17:46:51 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id DE5A3511F9; Thu, 16 Oct 2003 17:16:48 +0930 (CST) Date: Thu, 16 Oct 2003 17:16:48 +0930 From: Greg 'groggy' Lehey To: aarong Message-ID: <20031016074648.GG13080@wantadilla.lemis.com> References: <20031015055546.GK13080@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3JWHCGIvlHPlU6rB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-questions@freebsd.org Subject: Re: volumes crash on reboot [was Re: clearing Vinum configurations] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 07:46:58 -0000 --3JWHCGIvlHPlU6rB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 15 October 2003 at 23:14:18 -0700, aarong wrote: > After some extensive testing, I've come to the conclusion that Vinum > refuses to create any type of volume on the drive I'm having trouble > with. I'll create any number of volumes and/or additional plexes on the > second drive in the system successfully, only to have all the volumes > or plexes that reside on the second drive crash on reboot. Vinum's logs > in /var/log/vinum_history aren't very helpful nor are any of the other > debugging techniques listed in the vinum debug howto. If you don't show them to me, I can't comment. > /var/log/vinum_history is filled with "vinum started", "list", > "dumpconfig", "start usr.p1", and "quit" messages - nothing > descriptive of interest. They would tell me the sequence of what you've done. > The same goes for "vinum list" output, as well as dd'ing > the sixth sector on both drives. I suppose you mean the 8th. But dumpconfig is more useful. > This is a remote box without -DVINUMDEBUG built and such a procedure > is far too prohibitive; Why? But there's no obvious need for it yet. > it's already taken a week to find a competent tech at the datacenter > to work with Vinum and another week to teach him how to setup a > bootable Vinum volume. Needless to say we're far behind schedule. As > much as I'd like to mirror things and leave it at that, it worries > me greatly that something could be physically wrong with the second > hard drive and this software RAID 1 setup is only giving my client a > false sense of security. I'll need some sort of concrete evidence to > ask for a new hard drive to be installed. I don't think it's the drive. > The first drive, known to Vinum as "alpha", is ad0 and has four > perfect volumes which the system runs off of. The second drive, > known to Vinum as "beta", is the slave on the secondary channel and > hence is device ad3. I'm almost sure this has no relevance but as > you can tell I'm completely lost. Both are identical in model, > revision, and size. If I could get a look at the log output, I might be able to help more. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. --3JWHCGIvlHPlU6rB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/jkzoIubykFB6QiMRAgsNAKCLe7QRUhLQGH60vJ7cjGqQtkVPIACfRWc/ SH4MdLEWovhsGto+QbxJAkU= =nbky -----END PGP SIGNATURE----- --3JWHCGIvlHPlU6rB--