From owner-freebsd-current Sat Feb 22 3:32: 2 2003 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 D2A9C37B401 for ; Sat, 22 Feb 2003 03:32:01 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3CCD43F75 for ; Sat, 22 Feb 2003 03:32:00 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h1MBVvlI018519; Sat, 22 Feb 2003 12:31:58 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Michael Class Cc: Christian Gusenbauer , freebsd-current@FreeBSD.ORG Subject: Re: Mounting Root fails with error 22 (EINVAL) From: phk@phk.freebsd.dk In-Reply-To: Your message of "Sat, 22 Feb 2003 10:10:26 +0100." <3E573E82.7050908@gmx.net> Date: Sat, 22 Feb 2003 12:31:57 +0100 Message-ID: <18518.1045913517@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3E573E82.7050908@gmx.net>, Michael Class writes: >Hello, > >just as a data-point. I am seeing the same behaviour. It started with a >kernel from Feb 21th. The kernel from Feb. 20th works o.k. > >Enclosed is the dmesg out, if that helps. Please try "boot -v" and send dmesg. Also, please try entering "?" to root device prompt to see what devices are available. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message