From owner-freebsd-current Wed Dec 2 16:39:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29397 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:39:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29372 for ; Wed, 2 Dec 1998 16:39:37 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id LAA18351; Thu, 3 Dec 1998 11:39:23 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma018347; Thu, 3 Dec 98 11:39:10 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id LAA12468 for ; Thu, 3 Dec 1998 11:39:10 +1100 From: "John Saunders" To: "FreeBSD current" Subject: Booting 3.0-RELEASE in a non-standard setup Date: Thu, 3 Dec 1998 11:39:10 +1100 Message-ID: <000d01be1e55$577177a0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having some problems getting 3.0-CURRENT to boot. My setp...2 EIDE drives, wd0 and wd2. wd0 is Windows only. wd2 has 4 partitions, 1 is FreeBSD 2.2.8, 2 was empty, 3 and 4 are linux and linux swap. What I did...Booted from the CD and selected slice 2 (which was empty) to install to. Using the disk label editor I created / swap /usr /var in slice 2. I selected to not touch the MBR when installing boot blocks. The installation process went OK and I was able to see the files being installed in the right place (I can boot 2.2.8 and mount the partitions on wd2s2). What happens...Using the FreeBSD boot manager I press F5 to switch to drive wd2, then F2 to boot the wd2s2 slice. However it seems that the boot block in wd2s2 decided to load the 2.2.8 kernel from wd2s1 and I end up booting into 2.2.8 OK. So I decide to try the new boot blocks, from 2.2.8 I mount the slice 2 partitions and using the 2.2.8 disklabel I go... disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 wd2s2 ...which appears to update the right boot blocks. So now I use the F5 F1 proceedure and I get a different boot manager with a ? key for command list (BTW help doesn't work because the boot.help file got installed in the wrong place). However if I let the auto boot timeout go the 3.0-RELEASE kernel starts but dies with "unable to mount root wd1a" message. I tried typing "boot kernel" from the boot manager with the same panic. Listing the boot variables show 2 interesting variables (name escapes me now) and both were set to disk2s2a (I think the a was there). Question...After all that, does anybody have a 2xFreeBSD on 1xDisk config working? If so then how? I could probably do some hackery with the partition table each time I want to boot 3.0 but it _should_ work without that. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message