From owner-freebsd-current Wed Nov 11 11:08:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21424 for freebsd-current-outgoing; Wed, 11 Nov 1998 11:08:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kstreet.interlog.com (kstreet.interlog.com [198.53.146.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21419 for ; Wed, 11 Nov 1998 11:08:17 -0800 (PST) (envelope-from kws@kstreet.interlog.com) Received: (from kws@localhost) by kstreet.interlog.com (8.9.1/8.9.1) id OAA00441; Sat, 31 Oct 1998 14:07:54 -0500 (EST) (envelope-from kws) From: Kevin Street MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13883.24586.614752.970999@kstreet.interlog.com> Date: Sat, 31 Oct 1998 14:07:54 -0500 (EST) To: current@FreeBSD.ORG Subject: boot loader problems with mix of wd and da X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some difficulties using the new boot blocks and loader in some configurations. I have a backup copy of my root partition on another drive that causes the loader some problems. kernel is aout disks are wd0, wd1, da0, da1 (removable) I boot through Partition Magic's Boot Manager which lives on wd0. The normal root is on wd1s2a. The backup root is on da0s2a. I've done (after a Nov 10 make world): disklabel -B -b /boot/boot1 -s /boot/boot2 wd1 disklabel -B -b /boot/boot1 -s /boot/boot2 da0 The normal boot through wd1 is fine. If I want to boot my backup root on da0 then the results vary: 1) If I don't have a /boot.config on da0 then it autoboots into /boot/loader, currdev is set to disk3s2. It finds /boot/boot.conf ok, loads the kernel but the kernel boot fails with "changing root device to da2s2a". (there is no da2). 2) If I do have a /boot.config on da0 with: 2:da(0,a)/boot/loader Then it finds and loads the loader, but currdev is set to disk1s2 so it can't find /boot/boot.conf or anything else. disk1s2 would actually be the Boot Manager on wd0. If I manually change currdev to disk3s2, then I can load the kernel but boot fails as above. 3) If I interrupt the loading of /boot/loader and instead type in: 2:da(0,a)kernel Then everything is fine. The kernel boot succeeds and correctly does "changing root device to da0s2a". (The kernel is compiled with root on wd1s2a since that's its normal spot). I suspect this won't work if I go to an elf kernel since I need to use /boot/loader for elf, right? So, why is currdev set differently in case 1 and case 2? Why does /boot/loader confuse the kernel into thinking there's a da2 on which it might find root? -- Kevin Street street@iName.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message