From owner-freebsd-bugs Sun Nov 26 2:20: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7F1BC37B4D7 for ; Sun, 26 Nov 2000 02:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA76100; Sun, 26 Nov 2000 02:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id E089237B4CF for ; Sun, 26 Nov 2000 02:13:52 -0800 (PST) Received: from 149.211.6.64.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sun, 26 Nov 2000 02:12:18 -0800 Received: (from cjc@localhost) by 149.211.6.64.reflexcom.com (8.11.0/8.11.0) id eAQADlR98780; Sun, 26 Nov 2000 02:13:47 -0800 (PST) (envelope-from cjc) Message-Id: <200011261013.eAQADlR98780@149.211.6.64.reflexcom.com> Date: Sun, 26 Nov 2000 02:13:47 -0800 (PST) From: cjclark@reflexnet.net Reply-To: cjclark@alum.mit.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: i386/23108: Boot defaults to wd(4) devices rather than ad(4) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Note: There was a bad value `non-critica' for the field `>Severity:'. It was set to the default value of `serious'. >Number: 23108 >Category: i386 >Synopsis: Boot defaults to wd(4) devices rather than ad(4) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Nov 26 02:20:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: Crist J. Clark >Release: FreeBSD 4.1-STABLE i386 >Organization: >Environment: FreeBSD 4.x on i386 booting from IDE HDD without an fstab(5) file. >Description: When booting without an fstab(5) file, by default, the kernel will try to mount the root device from a wd(4) device. However, since the wd(4) have been depricated for ad(4), it should try to boot from an ad(4) device. >How-To-Repeat: Without any special settings in the /boot/loader.conf or other customizations, # mv /etc/fstab /etc/fstab.hold # reboot . . . (After we go through the boot messages...) atapci0: port 0xfe00-0xfe0f irq 14 at device 8.0 on pci0 ... ad0: 775MB [1575/16/63] at ata0-master WDMA2 Mounting root from ufs:wd0s1a Now, I fall into single-user where I repair the fstab and continue the boot. When up in multi-user, # mount /dev/wd0s1a on / (ufs, local, soft-updates) /dev/ad0s1e on /usr (ufs, local, soft-updates) procfs on /proc (procfs, local) The wd0 is still there. When booted with the fstab, /dev/ad0s1a on / (ufs, local, soft-updates) It appears as intended. >Fix: I had a look in the boot code and found where the mount information is printed from, /usr/src/sys/kern/vfs_conf.c, but trying to track down where all that information comes from... That BIOS stuff is not pretty. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message