From owner-freebsd-current@FreeBSD.ORG Mon May 5 10:42:07 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 0522F37B401 for ; Mon, 5 May 2003 10:42:07 -0700 (PDT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A09443F75 for ; Mon, 5 May 2003 10:42:06 -0700 (PDT) (envelope-from wa1ter@myrealbox.com) Received: from myrealbox.com (adsl-64-175-105-23.dsl.lsan03.pacbell.net [64.175.105.23])h45Hg3Uk039612; Mon, 5 May 2003 13:42:04 -0400 Message-ID: <3EB6B081.6090004@myrealbox.com> Date: Mon, 05 May 2003 11:42:09 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030502 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Blackman , freebsd-current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.0-current kernel (May 4) devfs not picking up slices from 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:42:07 -0000 Mark Blackman wrote: > 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' Ouch, you picked just the wrong moment to update :-( If you can, try to update your sources again and make a new kernel. The problem was just fixed a short while ago, in a temporary sort of way. It most likely will be changing again shortly, so beware. Mysterious errors are not your necessarily your fault (except when they are).