Re: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")

[Matt Mackall]

On Wed, Feb 23, 2005 at 03:03:33PM -0800, Andrew Morton wrote:
> Steven Cole <elenstev@xxxxxxxxxxx> wrote:
> >
> > Andrew Morton wrote:
> > > Steven Cole <elenstev@xxxxxxxxxxx> wrote:
> > 
> > >> I am having trouble getting recent -mm kernels to boot on my test box.
> > >> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
> > >>
> > >> VFS: Cannot open root device "301" or unknown-block(3,1)
> > >> Please append a correct "root=" boot option
> > >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
> > >>
> > [snipped]
> > > 
> > > Please set CONFIG_BASE_FULL=y.  Check that this causes CONFIG_BASE_SMALL=0,
> > > then retest.
> > 
> > Yes, that worked.
> 
> hmm, OK.  Matt, we have a block major enumeration problem.  It appears that
> base-small-shrink-chrdevs-hash.patch has the same problem which
> base-small-shrink-major_names-hash.patch had.

Hard to see how that could happen.
 
> >  2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing.
> > 
> > [root@spc1 steven]# uname -r
> > 2.6.11-rc4-mm1-GX110
> > [root@spc1 steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing
> > mount: special device /dev/hdb1 does not exist
> 
> It would seem that your /dev/hdb1 block-special device node isn't present. 
> Try `mknod /dev/hdb1 3 65'.

He's got devfs. Something change there recently?

-- 
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/