From owner-freebsd-questions Mon Aug 18 21:49:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA09786 for questions-outgoing; Mon, 18 Aug 1997 21:49:47 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts13-line12.uoregon.edu [128.223.150.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09781 for ; Mon, 18 Aug 1997 21:49:42 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id VAA02591; Mon, 18 Aug 1997 21:49:36 -0700 (PDT) Date: Mon, 18 Aug 1997 21:49:35 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: lamaster@george.arc.nasa.gov cc: freebsd-questions@FreeBSD.ORG Subject: Re: Failure to mount / after successful boot on wd2 In-Reply-To: <199708182029.NAA03536@george.arc.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997 lamaster@george.arc.nasa.gov wrote: > > I am attempting to get FreeBSD (2.2.2, although I could use 3.0-current > if that would solve it), to boot off of a second EIDE disk which is > master on the second EIDE controller. Win95 owns the disk on the > first controller. > > I installed the Booteasy MBR on both disks, it seems to work fine, > I point it at the second disk, it boots, it does everything perfectly > correctly and happily until it wants to go multiuser and mount /, > then, it can't mount root from "wd1" (why is "wd1" here, I thought > we were using wd0 and wd2?) and then it dies. The following should fix you up. If you get the message: panic: Cannot mount root At the end of the probe sequence you should either: 1. Have the line: config kernel root on wd2 in your kernel config, OR: 2. Rename the second disk to wd1 in the kernel config (comment out the original wd1 line and change the wd2 line to read wd1, leaving all other parameters unchanged). > If I take the exact > same disk, edit /etc/fstab (boot from floppy, mount using fixit), > to point at wd0 instead of wd2, and disconnect the w95 disk > at wd0 and reconnect the freebsd disk there, it works fine. > Why can't it mount root on wd2, and what is pointing at "wd1" > since /etc/fstab is set to mount filesystems on wd2? As I said, > changing only /etc/fstab entries to wd0, everything works fine > if the disk is the master disk on the primary controller. This is because the boot blocks are good at counting but not good at looking at IDE controllers. It notices that you have two IDE disks and assumes you have then connected to the primary controller, thus making their designations wd0 and wd1. Of course, the kernel, which knows about IDE controllers, thinks otherwise and thus the 'can't mount root' message. The method above will fix this permanently. Hope this helps! Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo