Date: Sun, 09 Apr 2000 22:51:48 -0700 From: tomb <tomb@cgf.net> To: cjclark@home.com, freebsd-questions@freebsd.org Subject: Re: vinum causes fatal double fault kernel panic Message-ID: <38F16BF4.905477CE@cgf.net> References: <38F0359F.E45937FC@cgf.net> <38F0C358.D120908@cgf.net> <20000409212525.B25406@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Err not what I was expecting! This is after having used the disklabel -e /dev/da0 command. (see my reply to Greg Lehey) I'm going to poke around disklabel and see what I can find about the failure. su-2.03# disklabel -r /dev/da0 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) su-2.03# disklabel -r /dev/da1 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) "Crist J. Clark" wrote: > On Sun, Apr 09, 2000 at 10:52:24AM -0700, tomb wrote: > > Additional: > > > > So I decided to reformat the drives using the scsi adaptors format utility > > (which completed with success). I modified the vinum config file to the > > following: > > > > drive a device /dev/da0s1 > > drive b device /dev/da1s1 > > volume mirror > > plex org concat > > sd length 4141m drive a > > plex org concat > > sd length 4141m drive b > > > > Now I start vinum with the following command.... > > > > su-2.03# vinum create config > > 1: drive a device /dev/da0s1 > > ** 1 : Invalid argument > > 2: drive b device /dev/da1s1 > > ** 2 : Invalid argument > > [snip] > > What is the disklabel(8) output for each of these drives? > -- > Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38F16BF4.905477CE>