From owner-freebsd-questions@FreeBSD.ORG Sat Jun 18 14:50:00 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 1902E16A41C for ; Sat, 18 Jun 2005 14:49:59 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: from pearl.ibctech.ca (dev.eagle.ca [209.167.58.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CADC43D1F for ; Sat, 18 Jun 2005 14:49:59 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: (qmail 538 invoked by uid 1002); 18 Jun 2005 14:49:55 -0000 Received: from iaccounts@ibctech.ca by pearl.ibctech.ca by uid 89 with qmail-scanner-1.22 (clamscan: 0.73. spamassassin: 2.64. Clear:RC:1(209.167.16.15):. Processed in 1.383813 secs); 18 Jun 2005 14:49:55 -0000 Received: from unknown (HELO fuze) (209.167.16.15) by dev.eagle.ca with SMTP; 18 Jun 2005 14:49:53 -0000 From: "Steve Bertrand" To: "'Titus von Boxberg'" Date: Sat, 18 Jun 2005 10:47:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcVzhNstj6toRwH+SPuz1shMQltMfAAj0Kgw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <42B34293.6050300@bhi-hamburg.de> X-Qmail-Scanner-Message-ID: <1119106194675532@pearl.ibctech.ca> Message-Id: <20050618144959.6CADC43D1F@mx1.FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: RE: Booting with multiple RAID1 configs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jun 2005 14:50:00 -0000 > You might use loader(8) to set the root device ("rootdev" > variable) explicitly to ar1s1a. Then you should also update > fstab to reflect the numbering change. > I don't know of any way to change the ata numbering scheme. > Mainboard controllers always seem to be probed (and numbered) > first. I think there is no way to get your original raid back > to ar0 if you also use your mainboard controllers. Thank you so, so much. After trying to mount / to ufs:/dev/ar1s1a at the MountRoot prompt and it failing, I thought something more serious was the problem, so: - I added kern.rootdev=/dev/ar1s1a to sysctl.conf - Changed the / fs in /etc/fstab to point to /dev/ar1s1a At that point, the system loaded the root filesystem, but since that was the only one I changed, it errored out mounting the rest (which was expected). I simply mounted them manually /dev/ar1s1N to /usr /var and /home, remounted the / filesystem rw, ee the /etc/fstab and changed all the mountpoints to ar1, rebooted, and all is well! I now have 2 RAID1 configs on the same box, and am successfully booting off of the promise raid properly before the motherboard disks!! Thanks to all who provided feedback! I hope this situation can help someone else who wants to boot off of an arbitrary disk before the motherboard disk in the future! Steve > > Cheers > Titus >