From owner-freebsd-stable Sat Jun 2 10:14: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D75CE37B422 for ; Sat, 2 Jun 2001 10:13:56 -0700 (PDT) (envelope-from steve@havk.org) Received: from bsd.havk.org (user-24-214-92-252.knology.net [24.214.92.252]) by mail.hiwaay.net (8.11.3/8.11.3) with ESMTP id f52HDtH25768 for ; Sat, 2 Jun 2001 12:13:55 -0500 (CDT) Received: by bsd.havk.org (Postfix, from userid 1001) id 08FE71A821; Sat, 2 Jun 2001 12:13:53 -0500 (CDT) Date: Sat, 2 Jun 2001 12:13:53 -0500 From: Steve Price To: freebsd-stable@freebsd.org Subject: vinum panic Message-ID: <20010602121353.N688@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.3-RC i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been trying for several days now to get a RAID5 volume setup on a new box and no matter what I've tried it always ends up panic'ing the kernel where I try to create the volume. Here's my configuration file: drive d1 device /dev/da1s1e drive d2 device /dev/da2s1e drive d3 device /dev/da3s1e drive d4 device /dev/da4s1e drive d5 device /dev/da5s1e volume raid plex org raid5 512k sd length 17626m drive d1 sd length 17626m drive d2 sd length 17626m drive d3 sd length 17626m drive d4 sd length 17626m drive d5 I've decided that I would skip RAID5 and do RAID10 instead because I've had success with it before. So after the crash here's what I did. vinum vinum -> resetconfig vinum -> saveconfig vinum -> stop newfs /dev/da1s1e newfs /dev/da2s1e newfs /dev/da3s1e newfs /dev/da4s1e newfs /dev/da5s1e disklabel -e /dev/da1s1e # change 4.2BSD to vinum for 'e' disklabel -e /dev/da2s1e disklabel -e /dev/da3s1e disklabel -e /dev/da4s1e disklabel -e /dev/da5s1e vinum vinum -> mirror -v -n raid10 -s /dev/da2s1e /dev/da3s1e /dev/da4s1e /dev/da5s1e drive vinumdrive0 device /dev/da2s1e vinum: drive vinumdrive0 is up Can't create drive vinumdrive0, device /dev/da2s1e: Invalid argument (22) vinum -> printconfig # Vinum configuration of , saved at Sat Jun 2 07:09:00 2001 vinum -> ls vinum -> ld vinum -> lv vinum -> lp vinum -> quit How can vinumdrive0 be up when it isn't defined? Anyone have any pointers to help down the road to vinum nirvana? Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message