All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: VFS Kernel Panic in 2.4.0-10(11)
Date: Fri, 17 Nov 2000 18:02:02 -0700	[thread overview]
Message-ID: <3A15D50A.6818516A@timpanogas.org> (raw)

	
This is probably a configuration mismatch of some kind, but I just
finished building my 2.4.0 RPM skeletons and am installting them from
our latest CD burn, and I am seeing the following 
problem when I upgrade our 2.2.17 kernel versions with 2.4.0-test10,
then reboot them under 2.4:

request_module[block-major-3]:  Root fs not mounted
VFS cannot open root device "301" or 03:01
Please append a correct "root=" boot option 
Kernel panic: VFS: Unable to mount root fs on 03:01.

The system was running Ute-Linux under 2.2.17 then was upgraded to
2.4.0-10 (with IPVS and pre-11 patches).
The disk is a 20GB device with 

/dev/hda1        Linux     (/,/boot)                               at
3,1
/dev/hda2        Extended  (contains a swap partition /dev/hda5)   at
3,2
/dev/hda3        Linux     (/usr)                                  at
3,3
/dev/hda4        Linux     (/archive)                              at
3,4
/dev/hda5        Swap       Swap                                   at
3,5

Lilo is configured in linear mode.  The device it's complaining about is
present 
(03:01) and lilo does append a root=/dev/hda1 statement.

Any ideas?

Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-18  1:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  1:02 Jeff V. Merkey [this message]
2000-11-18  1:25 ` VFS Kernel Panic in 2.4.0-10(11) Jeff V. Merkey
2000-11-18  1:30 ` Alexander Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A15D50A.6818516A@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.