From 9e2087b7614137ca270a959e25acce2e506c835d Mon Sep 17 00:00:00 2001 From: Sven Vermeulen Date: Wed, 2 Aug 2006 17:10:19 +0000 Subject: Some files svn path=/; revision=2 --- content/xml/rootfs-unknown00.xml | 84 +++++++++++++++++++++++++++++++++++++ content/xml/rootfs-unknownXY.xml | 89 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 173 insertions(+) create mode 100644 content/xml/rootfs-unknown00.xml create mode 100644 content/xml/rootfs-unknownXY.xml diff --git a/content/xml/rootfs-unknown00.xml b/content/xml/rootfs-unknown00.xml new file mode 100644 index 0000000..ad8a266 --- /dev/null +++ b/content/xml/rootfs-unknown00.xml @@ -0,0 +1,84 @@ + + + +Unable to mount root fs on unknown-block(0,0) + + swift + + + boot + kernel + kernel panic + + + +

+When you boot up your Gentoo system, you receive the following error before you +receive the Gentoo-specific start-up: +

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

+This occurs when booting a new kernel or after a change in the bootloader +configuration. +

+ + + + +

+When the Linux kernel has been booted and finished all its initial +configuration, it tries to mount the root filesystem. It uses the root boot +parameter to find out what the root filesystem is: +

+ +
+(Example from a grub.conf):
+kernel /kernel-2.6.10-gentoo-r5 root=/dev/hda3
+
+ +

+As the Linux kernel doesn't understand a string like "/dev/hda3" it translates +it to a set of numbers, called a major and minor number. In this error, the +major is zero, which is an illegal value. This occurs when the kernel has not +detected any hardware that can be called after the root device you told it to +boot (in the example: /dev/hda3). +

+ +

+The error occurs when the kernel did not load the support driver it needs. +

+ + + + +

+There are three possible reasons for this issue to occur: you did not select the +correct support when configuring the kernel, the support for your disk is built +as a module and you are not using an initial root device or your hardware does +not identify itself as /dev/hda3. +

+ +

+Make sure that your kernel configuration has support for the correct controller +(which governs your disk) and that it is built in the kernel, not as a module. +Otherwise your kernel would need to be able to mount the disk to find the module +to ... mount the disk. +

+ +

+If all that fails, double check if your controller really identifies the disk as +you think it does. Some Serial ATA controllers identify disks as IDE (hd), +others as SCSI (sd). +

+ + + diff --git a/content/xml/rootfs-unknownXY.xml b/content/xml/rootfs-unknownXY.xml new file mode 100644 index 0000000..085a6dd --- /dev/null +++ b/content/xml/rootfs-unknownXY.xml @@ -0,0 +1,89 @@ + + + +Unable to mount root fs on unknown-block(X,Y) + + swift + + + boot + kernel + kernel panic + + + +

+When you boot up your Gentoo system, you receive the following error before you +receive the Gentoo-specific start-up: +

+ +
+VFS: Cannot open root device "hda3" or unknow-block(8,3)
+Please append a correct "root=" boot option
+Kernel Panic: VFS: Unable to mount root fs on unknown-block(8,3)
+
+ +

+The numbers in the unknown-block(X,Y) can be different; the X-value is non-zero. +

+ + + + +

+This occurs when booting a new kernel or after a change in the bootloader +configuration. +

+ + + + +

+When the Linux kernel has been booted and finished all its initial +configuration, it tries to mount the root filesystem. It uses the root boot +parameter to find out what the root filesystem is: +

+ +
+(Example from a grub.conf):
+kernel /kernel-2.6.10-gentoo-r5 root=/dev/hda3
+
+ +

+As the Linux kernel doesn't understand a string like "/dev/hda3" it translates +it to a set of numbers, called a major and minor number. In this error, the +major and minor are known. This occurs when the kernel has succesfully detected +the hardware but is not able to understand the file system that it found on it. +

+ +

+In other words, the kernel does not have support for the file system on it +built-in. +

+ + + + +

+There are four possible reasons for this issue to occur: you did not select the +correct file system support when configuring the kernel, the support for the +file system is built as a module and you are not using an initial root device, +the file system is corrupted and does not identify itself as that particular +file system anymore, or there is no file system on it. +

+ +

+Make sure that your kernel configuration has support for the correct file +system and that it is built in the kernel, not as a module. +Otherwise your kernel would need to be able to mount the disk to find the module +to ... mount the disk. +

+ +

+Also, verify if the root parameter you've set is indeed pointing to the right +partition. If that fails too, see if you can mount this partition from a rescue +CD. +

+ + + -- cgit v1.2.3-65-gdbad