From owner-freebsd-current@FreeBSD.ORG Mon May 5 10:20:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E11637B401 for ; Mon, 5 May 2003 10:20:57 -0700 (PDT) Received: from mailhost1.dircon.co.uk (mailhost1.dircon.co.uk [194.112.32.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 314F143F85 for ; Mon, 5 May 2003 10:20:56 -0700 (PDT) (envelope-from mark@blackmans.org) Received: from mail.blackmans.org (unknown [195.157.223.200]) by mailhost1.dircon.co.uk (Postfix) with ESMTP id AFA5765A5A for ; Mon, 5 May 2003 18:20:54 +0100 (BST) Received: from spampd.localdomain (maddog [127.0.0.1]) by localhost.blackmans.org (Postfix) with ESMTP id 564A012B; Mon, 5 May 2003 18:20:54 +0100 (BST) Received: by mail.blackmans.org (Postfix, from userid 1001) id 9DB2F12A; Mon, 5 May 2003 18:20:53 +0100 (BST) Date: Mon, 5 May 2003 18:20:53 +0100 From: Mark Blackman To: freebsd-current@freebsd.org Message-ID: <20030505172053.GA403@maddog.blackmans.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Spam-Status: No, hits=-1.1 required=5.0 tests=CARRIAGE_RETURNS,SPAM_PHRASE_00_01,SUBJECT_MONTH, USER_AGENT,USER_AGENT_MUTT version=2.43 X-Spam-Level: Subject: 5.0-current kernel (May 4) devfs not picking up slices from 4-STABLE disk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 17:20:57 -0000 Hi, Just started following the instructions in /usr/src/UPDATING to go from 4-STABLE to 5-CURRENT and got stuck when booting the new kernel (a GENERIC kernel). Note that as per instructions, userland is still 4-STABLE at this point. This GENERIC kernel is from about 2300GMT May 3, so fairly up-to-date with an ATA disk. When booting, it claims 'Root mount failed: 22' should be '/dev/ad0s1a' (as in /etc/fstab) using '/dev/ad0s1' succeeds for single-user mode, but examination of /dev (i.e. devfs) indicates no partition devices are being created in the /dev area for ad0s1 (i.e. no ad0s1a, ad0s1b, etc..) The only recent conversation (in -current) about this sort of thing indicated an ata (ata_tag=1) problem, but mine is set to '0' anyway. any ideas or suggestions for fixing this out there? Cheers, Mark