From owner-freebsd-questions Thu Feb 10 18: 8:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 9B7CD465A for ; Thu, 10 Feb 2000 18:07:54 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA76976; Fri, 11 Feb 2000 12:15:58 +1030 (CST) Date: Fri, 11 Feb 2000 12:15:58 +1030 From: Greg Lehey To: Dan Langille Cc: freebsd-questions@FreeBSD.ORG Subject: Re: vinum volume dies. fsck can help? Message-ID: <20000211121558.E76521@freebie.lemis.com> References: <200002102051.JAA20685@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002102051.JAA20685@ducky.nz.freebsd.org> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 11 February 2000 at 9:51:06 +1300, Dan Langille wrote: > I have a box with three SCSI drives (da0 - da2). da1 and da2 are a > single vinum volume > > vinum: loaded > Can't open history file /var/tmp/vinum_history: No such file or directory > (2) > vinum: reading configuration from /dev/da2s1e > vium: updating configuration from /dev/da1s1e > vium: /dev is mounted read-only, not rebuilding /dev/vinum > Waring defective object > > p nzmirror.p0 S State: corrupt Subdisk: 2 Size: 2002MB > S nzmirrot.p0.s1 State: stale Po: 256 kB Size: 1001MB > swapon: adding /dev/da0s1b as swap device > Automatic reboot in progress... > > [stuff about /dev/rda0s1* snipped] > > /dev/vinum/nzmirror: CANNOT READ: BLK 1247904 > /dev/vinum/nzmirror: UNEPECTED INCONSISTENCY: run fsck > MANUALLY. > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED > INCONSISTENCY: > /dev/vinum/rnzmirror (/nsmirror) > > It then drops to single user mode. > > Should I be running fsck -y /nzmirror or fsck -y > /dev/vinum/rnzmirror ? /dev/vinum/rnzmirror, if you're running 3.x.. > Offhand, It sounds to me like the disk is dead. Yes, or it died. Do a 'camcontrol devlist' to see if it's even recognized. 'vinum l -V nzmirrot.p0.s1' will tell you which device should be up. If it's there, you're going to have to start the drive and the subdisk. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message