Corrupt initramfs after kernel update
When logged into WHM there was a message on the top right hand side of the screen that said
"You must reboot the server to apply kernel updates and apply software updates."
After the reboot, the server was inaccessible. My support guys were able to access it in Emergency Mode via the IDRAC virtual console. They found that initramfs was corrupt.
They rebuilt initramfs and the server is now back up running Cloudlinux 7.4 Standard with WHM v66.0.18 but I don't know what versions it was running beforehand. Previously the server had been up for 287 days.
I am naturally concerned about what will happen when the server is next rebooted. Is there any way to find out what went wrong?
-
Test by console to update the system packages running yum upgrade, if you fail some package there you will notice if something is missing at the time the kernel was updated. Otherwise you can run the following two commands to regenerate the parameters you lost. grub2-set-default 0 grub2-mkconfig -o /boot/grub2/grub.cfg And finally, reboot the server. In case the problem persists it is ideal to reinstall the kernel next to the damaged packages or directly contact through some ticket to the Cloudlinux team. 0 -
Hi, When logged into WHM there was a message on the top right hand side of the screen that said "You must reboot the server to apply kernel updates and apply software updates." After the reboot, the server was inaccessible. My support guys were able to access it in Emergency Mode via the IDRAC virtual console. They found that initramfs was corrupt. They rebuilt initramfs and the server is now back up running Cloudlinux 7.4 Standard with WHM v66.0.18 but I don't know what versions it was running beforehand. Previously the server had been up for 287 days. I am naturally concerned about what will happen when the server is next rebooted. Is there any way to find out what went wrong?
A proper update of package has to be done before you reboot.. Usually they are all dependent packages when the kernel is updated. Check if you have not excluded any of those in the yum.conf.. If you want to check what kernel version you were having previously, you can check the grub configuration file in the /boot and subfolders..0 -
Hello, You may also want to consult with a system administrator if you are concerned the filesystem might become corrupt again, as this is outside the scope of the support we can offer: System Administration Services | cPanel Forums Thank you. 0
Please sign in to leave a comment.
Comments
3 comments