From owner-freebsd-questions@FreeBSD.ORG Sat Jun 18 14:53:12 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 9A71816A427 for ; Sat, 18 Jun 2005 14:53:12 +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 A8FEB43D1D for ; Sat, 18 Jun 2005 14:53:11 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: (qmail 787 invoked by uid 1002); 18 Jun 2005 14:53:11 -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.361332 secs); 18 Jun 2005 14:53:11 -0000 Received: from unknown (HELO fuze) (209.167.16.15) by dev.eagle.ca with SMTP; 18 Jun 2005 14:53:09 -0000 From: "Steve Bertrand" To: "'Titus von Boxberg'" Date: Sat, 18 Jun 2005 10:51:08 -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+SPuz1shMQltMfAAj/QzA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <42B34293.6050300@bhi-hamburg.de> X-Qmail-Scanner-Message-ID: <1119106390675781@pearl.ibctech.ca> Message-Id: <20050618145311.A8FEB43D1D@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:53:12 -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. Hence, the aftermath on a properly booted system: pearl# atacontrol status 1 ar1: ATA RAID1 subdisks: ad4 ad6 status: READY pearl# atacontrol status 0 ar0: ATA RAID1 subdisks: ad2 ad0 status: READY pearl# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ar1s1a 246M 185M 41M 82% / /dev/ar1s1g 38G 9.7G 26G 27% /home /dev/ar1s1e 38G 3.3G 32G 9% /usr /dev/ar1s1f 29G 7.9G 19G 30% /var procfs 4.0K 4.0K 0B 100% /proc I must add that atacontrol is such a much simpler RAID manipulation tool than vinum. I haven't done any redundancy checks or anything as of yet, but it almost seems too good to be in the base system :) Steve > > Cheers > Titus >