public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Frazer <mark@mjfrazer.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: root cause of VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Date: Wed, 28 Apr 2004 11:43:37 -0400	[thread overview]
Message-ID: <20040428154337.GC26897@mjfrazer.org> (raw)

'make install' on the Fedora systems will set grub up to use an initrd.
If you do this with a Linus 2.6 kernel, you will often see this error
when trying to use the initrd:

VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

The most common advice given is to change your grub entry to something
like root=/dev/hda2.

What most of the other posts on this topic don't include is the
preceeding messages:
kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
kernel: Freeing initrd memory: 98k freed
kernel: RAMDISK: Compressed image found at block 0
kernel: RAMDISK: incomplete write (-28 != 32768) 4194304

The root of the problem is that the default ramdisk size of 4096 is not
big enough for the initrd used on Fedora.  I presume the same problem
exists on other systems.

Perhaps the default ramdisk size (CONFIG_BLK_DEV_RAM_SIZE) on the linus
kernels could be increased to 8192.

cheers
-mark
-- 
Drugs are for losers. And hypnosis is for losers with big weird
eyebrows. - Fry

                 reply	other threads:[~2004-04-28 15:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040428154337.GC26897@mjfrazer.org \
    --to=mark@mjfrazer.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox