Question 120
In a Linux incident, an engineer reports: A storage upgrade leaves /boot full and a new kernel installation fails. What is the MOST directly supported cause?
Explanation
Correct Answer
Cleaning random system logs does not free a separate full /boot partition. This mechanism fits the stated evidence. Validate it by checking that the new kernel and its initramfs fit under /boot.
Incorrect Answers
The alternative describes logical-volume size and filesystem size must both be extended, which is relevant when an LVM volume has enough VG free space but the database filesystem remains full. It does not explain this case because cleaning random system logs does not free a separate full /boot partition.
It would account for the kernel prints VFS unable to mount root fs after a storage controller change, not the current evidence. For this incident, cleaning random system logs does not free a separate full /boot partition; the alternative mechanism leaves that distinction unexplained.
A stale boot menu cannot load a nonexistent kernel. That can explain why a GRUB update left a boot entry pointing to a kernel image that was removed, whereas the current evidence supports a full /boot filesystem prevents writing kernel and initramfs images.





CompTIA Linux+ (XK0-006) Practice Tests