No subject

Sat Mar 5 19:55:20 UTC 2022

a newbie error. The initrd support at boot time was not enabled in my kernel.

So, thanks for help to everyone and particularily to roadrunner on the IRC
channel who give much time on-line to help me and Andreas Dilger.

My system is not fully functionnal yet, however, the LVM problem is solved.

My target configuration is a Linux From Scratch system, mostly based on V 3.0
instructions. But, instead of gcc 2.95.3 it is based on gcc 3.0.2 and glibc
2.2.4 with kernel 2.4.13. My remaining errors are with the initialization
scripts for the LFS, this is off topic on this dist list.

So, if I can help in the future with testing. Let me know.


Daniel Savard
Internet: dsavard at

Le ven, 16 nov 2001, Andreas Dilger a écrit :
> On Nov 16, 2001  17:19 -0500, Daniel Savard wrote:
> > While booting I am ending with a kernel panic message. The few last lines of
> > the boot message are as follow:
> > 
> > VFS: Cannot open root device "3a01" or 3a:01
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 3a:01
> Hmm, you only get that message when the initial boot is done, so two 
> possibilities (I'm not an initrd guru, mind you):
> 1) you need to change the root= line in your lilo.conf to say "root=/dev/ram0"
>    so that it will boot into the initrd.  Then do the real-root-dev trick
>    (or try pivot_root if running a 2.4 kernel) after configuring the LVM
>    stuff via vgscan; vgchange -a y.
> 2) You didn't re-run lilo after changing lilo.conf (yes, you probably did,
>    but you can never tell from here, and always safe to ask).
> > I also tested with ramdisk_size=X, where X is the size returned by the
> > lvmcreate_initrd script for the ramdisk.
> As long as this is larger than the size of the uncompressed ramdisk, you
> should be OK.
> Cheers, Andreas
> --
> Andreas Dilger

More information about the linux-lvm mailing list