* root cause of VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
@ 2004-04-28 15:43 Mark Frazer
0 siblings, 0 replies; only message in thread
From: Mark Frazer @ 2004-04-28 15:43 UTC (permalink / raw)
To: Linux Kernel List
'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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-04-28 15:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-28 15:43 root cause of VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) Mark Frazer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox