From owner-freebsd-stable Mon Mar 27 10: 9: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 3BEC937B8D2 for ; Mon, 27 Mar 2000 10:08:57 -0800 (PST) (envelope-from nasby@shell-1.enteract.com) Received: from shell-1.enteract.com (nasby@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id MAA94001 for ; Mon, 27 Mar 2000 12:08:55 -0600 (CST) (envelope-from nasby@shell-1.enteract.com) Received: (from nasby@localhost) by shell-1.enteract.com (8.9.3/8.9.3) id MAA63974 for freebsd-stable@FreeBSD.ORG; Mon, 27 Mar 2000 12:08:55 -0600 (CST) (envelope-from nasby) Date: Mon, 27 Mar 2000 12:08:55 -0600 From: "Jim C. Nasby" To: freebsd-stable@FreeBSD.ORG Subject: Re: vinum drive is dead Message-ID: <20000327120854.A46955@enteract.com> Reply-To: jim@nasby.net Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-Operating-System: FreeBSD 3.3-STABLE i386 X-Distributed: Join the Effort! http://www.distributed.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are blocks that fsck reports as un-readable. I'm hoping that this is because the dead drive is still attached to the plex. On Mon, Mar 27, 2000 at 02:38:31PM +0200, Thierry.Herbelot@alcatel.fr wrote: > > > Hello, > > I have had a crash on the machine where I have a stripped vinum : > you just have to make a "fsck " and all will be well > > TfH > > > > > "Jim C. Nasby" on 27/03/2000 10:59:56 > > > > To: freebsd-stable@FreeBSD.ORG > > cc: (bcc: Thierry HERBELOT/FR/ALCATEL) > > > > Subject: vinum drive is dead > > > > > > > I just suffered from a kernel panic, and the aftermath is that one of my > disks apparently got obliterated. disklabel -r da1 gives me an error > (don't remember what it is offhand), but the device itself seems ok. The > SCSI controller can read the drive (I had the controller verify the > media, it checked out ok), and the kernel recognizes it (although the > drives now show up in the order da0, da3, da2, da1 upon bootup, where it > used to be da0, 1, 2, 3). > > I'm hoping that I can just re-label the drive and get back up and > running, since most everything lives on vinum raid5 plexes. The problem > is that I don't know what the proper way to do this would be. Should I > detache the affected subdisks, redo the disk, and re-attach? I'm real > hesitant to screw with things since somehow the raid plex that houses > /tmp got corrupted. > > I think Greg is out of town for this week, but I'm hoping that someone > else can give me some pointers here. A vinum recovery page would be most > appreciated!! > > TIA, > dB! > -- > Jim C. Nasby (aka Decibel!) /^\ > jim@nasby.net /___\ > Freelance lighting designer and database developer / | \ > Member: Triangle Fraternity, Sports Car Club of America /___|___\ > > Give your computer some brain candy! www.distributed.net Team #1828 > Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain-candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message