On Wed, 13 Feb 2002 14:33:37 -0500, Bob Thibodeau wrote: > >I know this has been coming up, but the solutions I've seen offered >haven't worked for me. > >I'm trying to upgrade to 2.4.17 and getting the "vfs: cannot mount >root" error. > >I've tried with and without initrd support. The only difference being >whether the kernel can't mount root at 1:x or 3:x > >I've tried with and without make-kpg > >my 2.2 kernel still boots -- my lilo.conf is correct > >What have I missed?
I recently had the same problem. Here is the solution for mine, and maybe yours, too. Thanks to Thomas Shemanske. >To: Gary Turner <[EMAIL PROTECTED]> >Subject: Re: kernel panic---operator panic too >From: "Thomas R. Shemanske" <[EMAIL PROTECTED]> >Date: Thu, 07 Feb 2002 14:47:14 -0500 > >I think your initrd line is misplaced. Since some kernels do not need >the line, you probably want it with each lilo entry > >For example from http://rute.sourceforge.net/node34.html, we see a lilo >entry of the form: > > >boot=/dev/sda >prompt >timeout = 50 >compact >vga = extended >linear >image = /boot/vmlinuz-2.2.17 > initrd = /boot/initrd-2.2.17 > label = linux > root = /dev/sda1 > read-only > > > > >so I would change your lilo entry to from > > > image=/vmlinuz > > label=Linux > > read-only > > # restricted > > # alias=1 > >to > >image=/vmlinuz > label=Linux > initrd = /initrd.img > root=/dev/hda3 > read-only > >in which each entry specifies the root (so you can eliminate the append >statement), and if needed the initrd entry. THen you can get rid of the >initrd lines at the bottom of your file. > >Then of course after changing the file, don't forget to rerun lilo > gt Yes I fear I am living beyond my mental means--Nash
