From owner-freebsd-questions Tue Jul 9 08:36:49 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA16573 for questions-outgoing; Tue, 9 Jul 1996 08:36:49 -0700 (PDT) Received: from bdd.net (bdd.net [207.61.119.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA16568 for ; Tue, 9 Jul 1996 08:36:43 -0700 (PDT) Received: from localhost (matt@localhost) by bdd.net (8.7.5/8.7.3) with SMTP id LAA08830 for ; Tue, 9 Jul 1996 11:36:22 -0400 (EDT) Date: Tue, 9 Jul 1996 11:36:22 -0400 (EDT) From: Matthew Stein To: freebsd-questions@freebsd.org Subject: kernel thinks it's on sd1, when actually sd0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After reinstalling FreeBSD (2.1.0-R, 2.1-Stable-snap, 2.2-Current-snap) the kernel boot sequence determines it's on sd1, and proceeds to try and mount root there. I have no sd1, and the system properly finds the drive during the boot sequence as sd0. I can make the system boot properly by either using the "hd(1,a)/kernel" option at init, or the "-r" option at init. When I boot with hd(1,a)/kernel, the init lines indicates that I'm not booting from sd0, not sd1, as it would default. This doesn't seem to be an option during my kernel build, so what might be wrong? This is an Asus Pentium 133, Triton, 32meg RAM, a Western Digital EIDE drive as 'wd0', and a Quantum Empire 1080s hanging off an NCR 810. -- mat. +-Matthew Stein-------------------------------------------- matt@bdd.net-+ | Network Design phone: +1 519 823-8577 | | ButtonDown Digital fax: +1 519 823-9556 | +------------------------------------------------------------------------+