From owner-freebsd-questions Thu Dec 5 09:43:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA20187 for questions-outgoing; Thu, 5 Dec 1996 09:43:30 -0800 (PST) Received: from antonios.Stanford.EDU (antonios.Stanford.EDU [171.64.96.57]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA20182 for ; Thu, 5 Dec 1996 09:43:27 -0800 (PST) Received: from localhost (yergeau@localhost) by antonios.Stanford.EDU (8.8.4/8.7.1) with ESMTP id JAA17473 for ; Thu, 5 Dec 1996 09:43:13 -0800 (PST) Message-Id: <199612051743.JAA17473@antonios.Stanford.EDU> To: questions@freebsd.org Subject: hardwiring second-level boot to load 1:sd(0,a)/kernel by default Reply-To: yergeau@gloworm.Stanford.EDU Date: Thu, 05 Dec 1996 09:43:13 -0800 From: Dan Yergeau Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there any way to hardwire the second-level boot loader to default loading the kernel from a specific device? Or, is it necessary to change the SCSI ID of the boot drive and/or wire the target in the kernel config and modify/etc/fstab and verify that the appropriate slices for sd1 are in /dev? I've got one of those systems with an IDE drive and a SCSI drive. The IDE drive was added after FreeBSD was installed on the SCSI drive (if that matters). As documented, BIOS maps the the IDE to 0x80 and the SCSI to 0x81, but the second-level boot loader passes sd(1,a) (the "1" comes from the BIOS number) into the kernel instead of the correct SCSI device/partition. The system panics and reboots because it can't mount root. You can boot it with user interaction (i.e. by typing in the magical "1:sd(0,a)/kernel" at the "boot: " prompt), but I'd prefer not to have to do that. I'm running 2.2-ALPHA if that matters. Thanks in advance, Dan