From owner-freebsd-questions@FreeBSD.ORG Tue Sep 23 19:07:18 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 753CA16A4B3 for ; Tue, 23 Sep 2003 19:07:18 -0700 (PDT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80AEF43FE0 for ; Tue, 23 Sep 2003 19:07:16 -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 2BEAE2BD56 for ; Wed, 24 Sep 2003 12:07:14 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id E6F4151835; Wed, 24 Sep 2003 11:37:34 +0930 (CST) Date: Wed, 24 Sep 2003 11:37:34 +0930 From: Greg 'groggy' Lehey To: John Fox Message-ID: <20030924020734.GB10009@wantadilla.lemis.com> References: <20030923182149.GK53128@mind.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <20030923182149.GK53128@mind.net> 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: vinum crashed disk error 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: Wed, 24 Sep 2003 02:07:18 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 23 September 2003 at 11:21:49 -0700, John Fox wrote: > Hello, > > Three IDE drives multiplexed together to make one large "partition" > (for mounting as /usr/local). > > We were messing with hardware in the box and when we rebooted > vinum spat out errors about defective objects and the boot > came to a halt. We figured we had left something loose or > unplugged on the motherboard, so we shut it down and took > a look. Sure enough, the plug in the mobo's secondary IDE > channel was loose, so we reseated it and powered the machine > up again. > > We saw that the kernel found all the IDE drives and figured > the problem was over. But vinum had the same problem. It > said (loose quotation): "/dev/ mounted read-only. vinum config > not being rebuilt". And then spit out the same errors it had > the first time. These messages have a purpose. You shouldn't just ignore them. > Unfortunately, the vinum.org domain is having problems of some sort, What sort? More error messages? I have no problem accessing it (and no, it's not here, it's at the other end of the world). > and the vinum help pages on lemis.com are redirected to the > vinum.org site, They're on the same server. > so I am deprived of a great trouble-shooting resource. There are still the man pages. > output of 'vinum start': > ---------------------------------------------------------------------------- > Warning: defective objects > > V bigdisk State: down Plexes: 1 Size: 23 GB > P big_plex C State: faulty Subdisks: 3 Size: 23 GB > S drive0 State: down PO: 0 B Size: 8063 MB > S drive2 State: crashed PO: 8063 MB Size: 8063 MB > S drive3 State: crashed PO: 15 GB Size: 8063 MB > ---------------------------------------------------------------------------- > Any suggestions as to fixing this problem would be greatly > appreciated, as we do make production use of this box. Do these objects have any relationship to each other? The naming is confusing to say the least. In general, though, if your drives are up again, and the volume only has one plex, you can use the 'vinum setupstate' command to explicitly set the state to up. You'll then need to save the configuration with saveconfig after you've confirmed that the data is OK. 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 --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/cPxmIubykFB6QiMRAlUdAKCKpgJNst9gS9hEAbDxOtLehD9B0wCdEqUf MKNGd46YAxhuU2dn7Xsxqwg= =xApD -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP--