diff options
| -rw-r--r-- | content/xml/rootfs-unknown00.xml | 84 | ||||
| -rw-r--r-- | content/xml/rootfs-unknownXY.xml | 89 |
2 files changed, 173 insertions, 0 deletions
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 @@ +<!DOCTYPE issue SYSTEM "/dtd/kbase.dtd"> + +<issue id="1"> +<title>Unable to mount root fs on unknown-block(0,0)</title> +<maintainers> + <dev>swift</dev> +</maintainers> +<keywords> + <key>boot</key> + <key>kernel</key> + <key>kernel panic</key> +</keywords> +<synopsis> + +<p> +When you boot up your Gentoo system, you receive the following error before you +receive the Gentoo-specific start-up: +</p> + +<pre> +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) +</pre> + +</synopsis> +<environment> + +<p> +This occurs when booting a new kernel or after a change in the bootloader +configuration. +</p> + +</environment> +<analysis> + +<p> +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: +</p> + +<pre> +(Example from a grub.conf): +kernel /kernel-2.6.10-gentoo-r5 root=/dev/hda3 +</pre> + +<p> +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). +</p> + +<p> +The error occurs when the kernel did not load the support driver it needs. +</p> + +</analysis> +<solution> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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). +</p> + +</solution> +</issue> 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 @@ +<!DOCTYPE issue SYSTEM "/dtd/kbase.dtd"> + +<issue id="2"> +<title>Unable to mount root fs on unknown-block(X,Y)</title> +<maintainers> + <dev>swift</dev> +</maintainers> +<keywords> + <key>boot</key> + <key>kernel</key> + <key>kernel panic</key> +</keywords> +<synopsis> + +<p> +When you boot up your Gentoo system, you receive the following error before you +receive the Gentoo-specific start-up: +</p> + +<pre> +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) +</pre> + +<p> +The numbers in the unknown-block(X,Y) can be different; the X-value is non-zero. +</p> + +</synopsis> +<environment> + +<p> +This occurs when booting a new kernel or after a change in the bootloader +configuration. +</p> + +</environment> +<analysis> + +<p> +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: +</p> + +<pre> +(Example from a grub.conf): +kernel /kernel-2.6.10-gentoo-r5 root=/dev/hda3 +</pre> + +<p> +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. +</p> + +<p> +In other words, the kernel does not have support for the file system on it +built-in. +</p> + +</analysis> +<solution> + +<p> +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. +</p> + +<p> +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. +</p> + +<p> +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. +</p> + +</solution> +</issue> |