From owner-freebsd-questions@FreeBSD.ORG Tue Feb 10 18:20:40 2004 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 6E69B16A4CE for ; Tue, 10 Feb 2004 18:20:40 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4447F43D1D for ; Tue, 10 Feb 2004 18:20:40 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id A298A2BDBF for ; Wed, 11 Feb 2004 13:20:37 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id D426D51205; Wed, 11 Feb 2004 12:50:25 +1030 (CST) Date: Wed, 11 Feb 2004 12:50:25 +1030 From: Greg 'groggy' Lehey To: Ole Voss Message-ID: <20040211022025.GU2628@wantadilla.lemis.com> References: <6.0.2.0.0.20040205063057.01b0b300@213.131.227.50> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NBQMqqtZQBFxm+aD" Content-Disposition: inline In-Reply-To: <6.0.2.0.0.20040205063057.01b0b300@213.131.227.50> User-Agent: Mutt/1.4.1i 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: Grave vinum problem (at least for me) 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, 11 Feb 2004 02:20:40 -0000 --NBQMqqtZQBFxm+aD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 5 February 2004 at 6:48:18 +0100, Ole Voss wrote: > > Last night I reinstalled freebsd and obviously somewhere along the way my > 400GB concat vinum volume wasn't unmounted (at least that's what freebsd > told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss' > > I get this: > > titan# fsck -t ufs /dev/vinum/abyss > ** /dev/vinum/abyss > > CANNOT READ BLK: 843781344 > CONTINUE? [yn] y > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 843781344, 843781345, > 843781346, 843781347, > /dev/vinum/abyss: CANNOT FIGURE OUT FILE SYSTEM PARTITION > > It mounted fine last night and everything looked perfect. Then I did a > reboot and ... well, this is it now. > > Can anybody help me out? We need more information than this. This message alone could mean that one of your disks is defective, or that some component of the Vinum array is down. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html and supply the info I ask for there. 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. --NBQMqqtZQBFxm+aD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAKZFpIubykFB6QiMRAmCvAJ48xaW0dpwPRgHDJdou+3QQAe4GPACeNP2Y rr6y/L6xZtFTYRp8BfTmhyM= =vvrO -----END PGP SIGNATURE----- --NBQMqqtZQBFxm+aD--