I have seen people who, after building a first kernel (which doesn't boot), forget that they have to mount /boot before the If it doesn't, it is most likelyīecause the kernel doesn't know the device to begin with (so it can'tĬheck if the kernel that is being boot by the boot loader is the correct kernel. Section, only two partitions are found whereas the kernel was Misselected a partition (in the example given at the beginning of this If it does, it might help you identify if you ).Īlso, recent kernels give an overview of the partitions they found Try switching hda with sda (and hdb with sdb, and. This is notīecause kernels are inconsistent with each other, but because of theĭrivers used: older drivers use the hda syntax, newer sda. (configured) kernel is expecting it to be /dev/hda. Kernel, it might list your disks as being /dev/sda whereas your Make sure the file systemĬheck if the kernel parameter for root= is pointing to the correct partition. Module, then you'll get the error you see. Say your root file system uses btrfs (which I definitely don't recommend) but you didn't select it, or selected it to be built as a.Check if you have built in (and not as a module) support for the file system(s) you use.You can type "/" to open the search function, and type in the driver Running the following lscpi command, and paste its output onĭrivers you need to select for your system. Select the HDD controller driver itself (like Intel PIIX). One of the most frequent cases: you selected support for your harddisk controller protocol (IDE, SATA, SCSI. Check if you have built in (and not as a module) support for the HDD controller you use.Most likely this is PCI support, SATA support (which is beneath SCSI device support).Check if you have built in (and not as a module) support for the bus / protocol that your harddisk controller uses.That you can update the kernel configuration accordingly. Open the kernel configuration wizard (the make menuconfig part) so Likely don't, so here's a quick check-up. Resolving the issue is easy if you know what the reason is. the device is misidentified in your root= parameter (cases 2, 3).the kernel configuration is missing drivers for the file system you are using.the kernel configuration is missing drivers for the bus used by your HDD controller.the kernel configuration is missing drivers for your HDD controller (cases 1, 4, 5).Loader configuration) into a real, accessible file system. The problem here is that the kernel that you are booting cannot (like 8), it is unable to identify the file system (but is able to Kernel is unable to identify the hardware. Generally speaking one can say that, if the first digit is 0, then the The device that the kernel tries to access (and which fails). The digits 0,0 or 8,3 can be different in your case - it refers to Please append a correct "root=" boot option here are the available partitions: Or VFS: Cannot open root device "sda3" or unknown-block(8,3) ![]() You most likely are never going to see it again): Unable to mount root fs on unknown-block(0,0) Most likely one of the most occurring issue (but once you solved it, Doing a quick Google search led me to link 1, link 2, link 3įollowing is the excerpt from a link referred to by one of the links above: You haven't provided much information with logs and such to proceed with but I am guessing most probably this error you're facing is because the kernel is confused by a IDE/SATA drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |