XK0-004 · Question #438
A Linux administrator updated the graphics drivers using a package manager but now the server does not boot. Which of the following is the BEST way to get the server back into an operational state?
The correct answer is B. Reboot the server with an older kernel version.. When a driver update breaks the boot process, selecting an older kernel from GRUB is the fastest non-destructive recovery because the previous kernel retains its original working driver set.
Question
A Linux administrator updated the graphics drivers using a package manager but now the server does not boot. Which of the following is the BEST way to get the server back into an operational state?
Options
- AUse a system recovery disk to copy the server data to a new system.
- BReboot the server with an older kernel version.
- CKickstart the server and restore to the last system backup.
- DBoot a live CD mount and cferoot the boot partition, and run fsck.
How the community answered
(34 responses)- A3% (1)
- B79% (27)
- C6% (2)
- D12% (4)
Why each option
When a driver update breaks the boot process, selecting an older kernel from GRUB is the fastest non-destructive recovery because the previous kernel retains its original working driver set.
Copying data to a new system is a last-resort disaster-recovery measure that does not fix the driver issue and is disproportionate to a single failed package update.
Linux package managers preserve previous kernel versions alongside the new one, and GRUB2 presents all installed kernels at boot time. Selecting an older kernel immediately restores the pre-update driver environment without data loss, reinstallation, or time-consuming backup restoration - directly reversing the impact of the bad graphics driver package.
Kickstarting and restoring from backup performs a full system rebuild, which is far more disruptive and time-consuming than simply booting an older kernel already present on the system.
fsck repairs filesystem consistency errors; a graphics driver update that prevents booting is a driver or kernel module conflict, not a filesystem corruption problem, so fsck does not address the root cause.
Concept tested: Kernel rollback via GRUB for failed driver update recovery
Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/index
Topics
Community Discussion
No community discussion yet for this question.