From owner-freebsd-questions@FreeBSD.ORG Wed Apr 28 19:39:34 2004 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 8666116A4CE for ; Wed, 28 Apr 2004 19:39:34 -0700 (PDT) Received: from asarian-host.net (mail.asarian-host.net [194.109.160.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id A91C343D41 for ; Wed, 28 Apr 2004 19:39:33 -0700 (PDT) SRS0=/PS1Nbze=HZ=asarian-host.net=admin@asarian-host.net) Comments: To protect the identity of the sender, certain header fields are either not shown, or masked. Anonymous email accounts can be requested by filling in the appropriate form at: https://asarian-host.net/cgi-bin/signup.cgi Received: (from root@localhost) by mail.asarian-host.net (8.12.11/8.12.11) id i3T2dVev058626 for freebsd-questions@freebsd.org; Thu, 29 Apr 2004 04:39:31 +0200 (CEST) (envelope-from admin@asarian-host.net) From: Mark Received-SPF: pass (asarian-host.net: domain of admin@asarian-host.net designates sender IP as SASL permitted sender) Message-Id: <200404290239.I3T2DQQD058608@asarian-host.net> Date: Thu, 29 Apr 2004 02:39:31 GMT X-Authenticated-Sender: admin@asarian-host.net X-Trace: jaB3CxJ2qSTdow8byXqhQku0EHhgOOMlNP48xGnaUJtK6Sv8foquD1X6XKRGDXnElseFQvISlMPnDURZCuRVJA== X-Complaints-To: abuse@asarian-host.net X-Abuse-Info: Please be sure to forward a copy of ALL headers, otherwise we are unable to process your complaint Organization: Asarian-host To: "Matthew Seaman" References: <20040428125933.M1798@collins-ca.com> <20040428143343.GB38741@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Auth: Asarian-host PGP signature iQEVAwUAQJBq4zFqW1BleBN9AQFjywgAg0ad7ULG/dSg3omFR9hlDlvgzYSGL7zm HtxoXKNmpdH38lp5Ir8+U2PS6q85VX+yxts+n7U5efofUL9jac8doRTfH024WtoD EpkzC0kxXAnd5D9OxwboVGI5Q3RGnYOl7TnXC3Rx4O0CkJg/Y26/l0Yfnm+9cOhX 30ZA7cjq06OCwGarqHvMW7GxSI2uT9Sl/3ZepI8bbbr7ZMp8oKxStz+87UX/Y3uL ArU2bsfmtnbRvrgiPcRC7WW7o6YW1SLkj0BPJvasXgBiBemth5NHUFkr0QEvLWk+ um1JqMAmaYyJ7k4YRHCddyuebLPT1warqjspXP2y3WpXQC0uoJAZ5g== =iI4y cc: freebsd-questions@freebsd.org Subject: Re: Installing RAID question. 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: Thu, 29 Apr 2004 02:39:34 -0000 ----- Original Message ----- From: "Matthew Seaman" To: "Chris Collins" Cc: Sent: Wednesday, April 28, 2004 4:34 PM Subject: Re: Installing RAID question. > Yes, this is a well known problem -- it's not just adding new RAID > controllers that can cause it. Even something as simple as plugging > in a USB disk before booting can cause the 'da0' device to be > usurped. In order to prevent it, you can "wire down" your current > root drive to be da0 in your kernel configuration -- see the section > "SCSI DEVICE CONFIGURATION" in LINT for details. Something like > this should do the trick: > > device scbus0 at ahc0 > device da0 at scbus0 target 0 unit 0 I wonder, can the same be done for IDE? For instance, I have a test-environment where I boot from the second IDE port (via BIOS). For WinXP, and such, this is never a problem. But doing so on FreeBSD 4.9R proved problematic. I got a kernel panic, saying it could not boot off /dev/ad0s1a in fstab (drive had become /dev/ad1s1a). So, I was wondering whether I could perhaps "wire down" IDE assignments in a similar fashion. Thanks, - Mark