From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 16:37:10 2005 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 A3E7416A4CE for ; Fri, 22 Apr 2005 16:37:10 +0000 (GMT) Received: from mail1.flncs.com (ns1.flncs.com [204.0.142.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0695843D46 for ; Fri, 22 Apr 2005 16:37:10 +0000 (GMT) (envelope-from tradigan@newrevolutions.net) Received: (qmail 52785 invoked by uid 98); 22 Apr 2005 16:37:09 -0000 Received: from 66.166.153.82 by beastie.flncs.com (envelope-from , uid 89) with qmail-scanner-1.25 (clamdscan: 0.82/795. spamassassin: 3.0.2. Clear:RC:1(66.166.153.82):. Processed in 0.216137 secs); 22 Apr 2005 16:37:09 -0000 X-Qmail-Scanner-Mail-From: tradigan@newrevolutions.net via beastie.flncs.com X-Qmail-Scanner: 1.25 (Clear:RC:1(66.166.153.82):. Processed in 0.216137 secs) Received: from h-66-166-153-82.phlapafg.covad.net (HELO l03ptradigan) (tradigan@newrevolutions.net@66.166.153.82) by 0 with SMTP; 22 Apr 2005 16:37:09 -0000 From: "Timothy Radigan" To: Date: Fri, 22 Apr 2005 12:37:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcVHWY6a5vbfE4HPROWutb1tY77AqQ== X-Qmail-Scanner-Message-ID: <111418782970452778@beastie.flncs.com> Message-Id: <20050422163710.0695843D46@mx1.FreeBSD.org> Subject: Vinum 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, 22 Apr 2005 16:37:10 -0000 I know this topic has come up before, but how in the world do you get vinum to load AND start itself at boot time so I don't have to repair my mirrored volumes every reboot? I have tried to add start_vinum="YES" to /etc/rc.conf but that ends in a 'panic dangling node' error. I also tried to add vinum_load="YES" to /boot/loader.conf and that will load vinum at boot without panicing on me, but it doesn't start vinum and bring the mirrored devices up. I have to physically log into the server and type vinum start to bring up vinum. What I want, is that on a reboot, vinum is loaded at boot and is started so that I can mount my vinum drive through /etc/fstab Any ideas/suggestions? --Tim