Date: Sat, 22 Feb 2003 18:48:07 +0100 From: Christian Gusenbauer <c47g@gmx.at> To: phk@phk.freebsd.dk, Michael Class <michael_class@gmx.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting Root fails with error 22 (EINVAL) Message-ID: <200302221848.07600.c47g@gmx.at> In-Reply-To: <18518.1045913517@critter.freebsd.dk> References: <18518.1045913517@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 22. February 2003 12:31, phk@phk.freebsd.dk wrote: > 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. Unfortunately, I can't send you the requested output, because I've no serial console here to be able to trace the boot infos, and further, I can't get the kernel to create a crash dump. I do have a line saying 'dumpdev="ad0s3b"' in my loader.conf but the kernel seems to ignore my wishes when it panics :-(. Christian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302221848.07600.c47g>