From owner-freebsd-questions Tue May 16 18:47:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id C7D5237B8D5 for ; Tue, 16 May 2000 18:47:39 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id TAA40101; Tue, 16 May 2000 19:48:40 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Tue, 16 May 2000 19:48:40 -0600 (CST) From: Ryan Thompson To: cjclark@home.com Cc: Bastian Marmetschke , questions@FreeBSD.ORG Subject: Re: wd0s1a -> wd2s1a In-Reply-To: <20000516212935.B58707@cc942873-a.ewndsr1.nj.home.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark wrote to Bastian Marmetschke: > On Tue, May 16, 2000 at 10:09:23PM +0200, Bastian Marmetschke wrote: > > Hello, > > > > Still want to know if there is a way on how to "tell" freebsd that it > > is on wd2s1a (secondary master) now ? I installed it for wd0s1a > > (primary master) ages ago... But now I am using a windows hdd with a > > bootmanger (os-bs) as primary master so I have moved the FreeBSD hdd on > > secondary master. > > You will need to edit /etc/fstab. That should be about it. That's an essential step, but not usually enough. Don't forget to make sure that the device nodes for wd2 exist in /dev. cd /dev && ./MAKEDEV wd2s1a should do the trick. I've been bitten by this one before. Also edit /boot/loader.conf and add root_disk_unit="2" and/or add config kernel root on wd2 to your kernel config and recompile/install. And, as Crist mentioned, you need to change references for 'wd0' to 'wd2' as appropriate in /etc/fstab. The easiest way to do the above changes would be ALL AT ONCE, as you will run into problems if you don't get it right the first time. If the boot fails, you might get a kernel panic if the root filesystem can not be found (I have found 3.x to be particularly hard to please at times with a root filesystem not on wd0). And, if those device nodes aren't all present, you will have the unfortunate side effect of a read-only root filesystem that can NOT be re-mounted read/write, because the device node doesn't exist! (Had this happen to me on a 3.4 system. Imagine my delight when I couldn't gain write access to the part. to CREATE the missing nodes. Fixit was my saviour :-) Thus, before you go blindly where some have gone before, carry with you a working fixit floppy, in case of mishaps :-) Hope this helps. -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message