Home » LPI » 117-201 » What most likely is the cause?
You have compiled and installed a new kernel on your SCSI based machine. After installing the new kernel, the boot process stops at a point with the error “VFS PANIC: Unable to mount root FS.” You can boot again off the old kernel without any problems. Given that /etc/modules.conf is correct and that the SCSI controller is selected as a module in the kernel, what most likely is the cause?
A. The module failed to build.
B. The new kernel can’t initialize the SCSI controller.
C. There is no initrd image for the new kernel.
D. SCSI disk support isn’t enabled in the kernel.
E. SCSI generic support isn’t enabled in the kernel.
Correct Answer: C
Explanation/Reference:
Explanation: The question states that that the machine is SCSI based and you can boot to the old kernel.
This indicates that the system is successfully booting from the SCSI drive (when using the old kernel). The SCSI controller module needs to be loaded at boot time before the system is able to mount the root file system. To load the SCSI controller module at boot time, you need an initrd image for the new kernel.
Reference: http://www.linuxhelp.co.za/RedHat61/rhref/s1-sysadmin-build-kernel.htm#S2-SYSADMIN-INITRD
Incorrect Answers
A:It is unlikely that the module failed to build.
B:The new kernel can’t initialize the SCSI controller. However, the reason for this is most likely to be that there is no initrd image for the new kernel.
D:SCSI support can be loaded as a module if an initrd image exists. It does not have to be enabled (compiled) in the kernel.
E:SCSI support can be loaded as a module if an initrd image exists. It does not have to be enabled (compiled) in the kernel.
|
Download Printable PDF. VALID exam to help you PASS.
|
 |
