According to the guidance document LFS7.2, completed the compilation system installation steps, and finally there was the following problem at boot time:
Kernel play similar to the following passage, then crashes:
VFS: Cannot open root device "hda0" or unknown-block(0,0) Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
By google that this is due to the hard drive is not compiled into the kernel, even my main reference data networks, I use vmware8.0 version of the virtual machine to solve the problem by way of collecting data network as follows:
As for the network search solutions, the original address http://blog.csdn.net/q472599451/article/details/7992647 :
The study analysis, that is driving a hard disk drive module is not added to the Linux kernel.
The solution is straightforward: find the type of hard disk controller, and then the appropriate driver compiled into the kernel. More detailed resolution steps are:
1, on the host system LFS build, run lspci command to list the hardware information devices.
2, the hardware information, look for the IDE interface or SATA Controller or SAS Controller and other keywords, to get to the hard disk controller model
3, the kernel configuration, the corresponding driver is compiled into the kernel (ie not as modules). For IDE hard disk driver DeviceDrivers - looking> the ATA / ATAPI / MFM / RLL configuration item; SATA hard for the driver in DeviceDriver - looking> the SCSI low-level drivers CI -> SCSI device support.
4, recompile the kernel, copy to the appropriate / boot folder, restart the machine, under the new kernel LFS, the problem is solved.
This is a method two, the original address: http://blog.csdn.net/qihuanfengyun/article/details/5189789
Before selecting module, first find out the type of hardware VMware virtual machines, the following table is given the configuration when VMware6 custom virtual machine configuration, easy to find when you use the wizard gives VMware recommended configuration, the actual use a SCSI-type device LSI Logic device. A place to note here is that since there are two SCSI devices can for their choice, then how to judge it? Simply because he is the kernel major version number to the division. To interested friends can Other Linux2.6.X kernel and Other Linux2.4.X kernel by creating a new virtual machine Custom-Linux under the Version list. Before use BusLogic 2.4 kernel, 2.6 kernel is LSI Logic.
6.0 the VMware:
the I / O Adapter Types
the IDE Adapter: the ATAPI
the SCSI Adapter: the BusLogic
the LSI Logic
This is Other Linux2.6.X kernel of the system information
00: 10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 01)
this is a system information Other Linux2.4.X kernel
00: 10.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10] (rev 01)
Now select the path modules were introduced
this is a SCSI disk device module must be selected.
The Configuration Kernel linux
-> the Drivers Device
-> the SCSI Device Support
-> the SCSI Disk Support
This is BusLogic device driver modules. Using this equipment need to select a friend.
The Configuration Kernel linux
-> the Drivers Device
-> the SCSI Device Support
-> the SCSI Low-Level Drivers
-> the BusLogic the SCSI Support
This is the LSI Logic device driver modules. Using this equipment need to select a friend.
The Configuration Kernel linux
-> the Drivers Device
-> the MPT the Fusion Device Support
-> the Fusion the MPT (Base + ScsiHost) Drivers
VFS: root of Can not Open Device "sda" or unknow-Block (0, 0)
Please correct the append A "root =" the Option the Boot
Kernel panic: VFS: Unable to Mount root FS-ON Unknown Block (0, 0)
This makes upset error.
Also, if something prompts "No file system" without a file system like that you did not file kernel drivers compiled into the kernel.
Linux Kernel Configuration
->File Systems
-> Inside choose what ext2, ext3, ext4, xfs and the like can be elected on. (Much less can not)