Date: Thu, 17 Oct 2002 21:43:27 -0400 From: Tom Parquette <tparquet@twcny.rr.com> To: questions@FreeBSD.org Cc: "Greg 'groggy' Lehey" <grog@FreeBSD.org>, ahl@austclear.com.au Subject: Re: First time Vinum user. Setup problems Message-ID: <3DAF673F.5050006@twcny.rr.com> References: <3DAF5B95.9030905@twcny.rr.com> <20021018010848.GH20173@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK. Thanks to Greg and Tony for clearing up a couple of things. I just learned something about the boot process. Continuing: I recreated my error and this is what I got: vinum Vinum -> concat -n public -v /dev/ad5s1e /dev/ad6s1e /dev/ad7s1e volume public plex name public.p0 org concat drive vinumdrive0 device /dev/ad5s1e Can't create drive vinumdrive0, device /dev/ad5s1e: invalid argument (22) vinum -> Oct 17 21:24:11 Callimachus /kernel: vinum: public.p0 is up Oct 17 21:24:11 Callimachus /kernel: vinum: public is up (I didn't get a command prompt after the last message until I hit enter.) I'm somewhat confused on what should be listed for the -v values. I've seen a couple of different things in the various articles and man pages. I concluded from my reading, possibly incorrectly, that I had to allocate filesystems on the disks for vinum to use. e.g. ad5s1e. TIA for any help. Cheers... Greg 'groggy' Lehey wrote: > On Thursday, 17 October 2002 at 20:53:41 -0400, Tom Parquette wrote: > >>This is the first time I have tried to do anything with Vinum. >>This is on a 4.7-RELEASE machine. >>I'm doing a "minimal" installation over the Internet using the two >>floppy disk install method. >> >>I have several IDE volumes that I am trying to concatenate. >>After I complete the install I'm editing rc.conf to add the Vinum >>startup command. >> >>At boot, I get the following: >>vinum: loaded >>vinum: /dev is mounted read-only not rebuilding /dev/vinum >> > > This always happens when you start Vinum at boot time. It's harmless. > > >>Can't open /dev/vinum/Control read only file system >> > > This will only happen if you have never run Vinum before. It's > particularly harmless. > > >>When I look at fstab, "/" indicates it should be read/write. >> > > That's later. When you start Vinum at boot time, the root file system > is still mounted read only. > > >>If I enter vinum from root after the boot is complete, it prompts me >>with "vinum ->" so I'm pretty sure the klm is loaded. >> > > Correct. > > >>I get some other errors when I try to use the simplified method of >>creating a 3 disk concatenation. I suspect my symptoms will change >>once I figure out the /dev messages. >> > > I don't. This may possibly be a real problem, though I suspect it's a > misunderstanding. > > >>A more basic question. Are IDE drives supported by Vinum? >> > > Yes. > > 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 > > 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?3DAF673F.5050006>