Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Jan 2004 14:42:42 -0800 (PST)
From:      Doug White <dwhite@gumbysoft.com>
To:        Cy Schubert <Cy.Schubert@komquats.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: -STABLE Won't Boot On A Multidisk System
Message-ID:  <20040112144117.U54897@carver.gumbysoft.com>
In-Reply-To: <200401111619.i0BGJAr7075479@cwsys.cwsent.com>
References:  <200401111619.i0BGJAr7075479@cwsys.cwsent.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 11 Jan 2004, Cy Schubert wrote:

> I have a system which usually runs a recent copy of -CURRENT. I have one
> ATA disk and four SCSI disks in this system. My -CURRENT root device is
> /dev/ad0s1a while my -STABLE (4.9R) boot device is /dev/da1s1a. No problems
> booting -CURRENT however I haven't used my -STABLE system in a while and as
> I need to do some testing on it, I tried booting it this morning. It
> responded with a "Root mount failed:22" message.

Error 22 is EINVAL.  Which disk did you get loader off of?

My first shot at this would be that somehow a -stable kernel is trying to
mount a ufs2 filesystem, but everything *seems* to be in order.

Are you using boot0?

I have a machine with 2 ide disks and boot0 that seems to keep everything
straight. Combined IDE/SCSI systems can be a bit tempermental.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040112144117.U54897>