From owner-freebsd-current@FreeBSD.ORG Mon May 5 10:46:24 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 8F71037B401 for ; Mon, 5 May 2003 10:46:24 -0700 (PDT) Received: from mailhost1.dircon.co.uk (mailhost1.dircon.co.uk [194.112.32.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD97143F3F for ; Mon, 5 May 2003 10:46:23 -0700 (PDT) (envelope-from mark@blackmans.org) Received: from blackmans.org (unknown [195.157.223.200]) by mailhost1.dircon.co.uk (Postfix) with ESMTP id 00E3D59B60; Mon, 5 May 2003 18:46:23 +0100 (BST) Message-ID: <3EB6A36E.30809@blackmans.org> Date: Mon, 05 May 2003 18:46:22 +0100 From: Mark Blackman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030426 X-Accept-Language: en-us, en MIME-Version: 1.0 To: walt References: <3EB6B081.6090004@myrealbox.com> In-Reply-To: <3EB6B081.6090004@myrealbox.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org 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:46:24 -0000 walt wrote: > 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). > Thanks. will try that. Cheers, Mark