From owner-freebsd-questions@FreeBSD.ORG Fri Oct 24 09:49:45 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 276DF16A4BF for ; Fri, 24 Oct 2003 09:49:45 -0700 (PDT) Received: from kosh.oneofum.net (mail.oneofum.net [66.11.163.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4A5C43FCB for ; Fri, 24 Oct 2003 09:49:43 -0700 (PDT) (envelope-from gunkel@oneofum.net) Received: by kosh.oneofum.net (Postfix, from userid 2001) id EEB8ADC7F8; Fri, 24 Oct 2003 12:47:56 -0400 (EDT) Received: from kosh.oneofum.net (kosh.oneofum.net [66.11.163.245]) by kosh.oneofum.net (Postfix) with SMTP id 945C2DC7D6; Fri, 24 Oct 2003 12:47:52 -0400 (EDT) Received: from 198.151.13.15 (SquirrelMail authenticated user gunkel) by mail.oneofum.net with HTTP; Fri, 24 Oct 2003 12:47:52 -0400 (EDT) Message-ID: <41018.198.151.13.15.1067014072.squirrel@mail.oneofum.net> In-Reply-To: References: <20031024073656.GR6073@wantadilla.lemis.com> Date: Fri, 24 Oct 2003 12:47:52 -0400 (EDT) From: "Alvin Gunkel" To: "Roland Wells" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on kosh.oneofum.net X-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,PRIORITY_NO_NAME autolearn=no version=2.60 X-Spam-Level: cc: freebsd-questions@freebsd.org Subject: RE: vinum concatenated raid setup problems - SOLVED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Oct 2003 16:49:45 -0000 I see this has been solved, but i'll throw one more gotcha to watch for out there. Use of 'vinum saveconfig' is a good thing. From the vinum man page: saveconfig Save the current configuration to disk. Normally this is not necessary, since vinum automatically saves any change in configu- ration. If an error occurs on startup, updates will be disabled. When you reenable them with the setdaemon command, vinum does not automatically save the configuration to disk. Use this command to save the configuration. As I was learning to use vinum I made frequent mistakes, disabling updates, then built the system, rebooted, and nothing survived ;) Had to rtfm a couple of times before I caught that. Alvin > Mike, > Thanks for the pointers on the fstab file, they solved that part of the > puzzle. (and trying to help with the other issues) > > Greg, > Thanks for pointing me to the right part of the vinum manpage...it was > indeed the simple fact that I was trying to build the configuration on > disk's rather than partitions that was sabotaging the mission!