Bobcares

Resolved: CentOS 8 virtual servers won’t boot after OS upgrade

PDF Header PDF Footer

Wondering what to do if CentOS 8 virtual servers won’t boot after OS upgrade? You are in luck. Our Support Engineers have an easy fix for your problem.

Trouble after an OS upgrade is more common than you thought. It occurs when the new boot scheme is no longer supported by the hypervisor grub boot image. Read on to find out how we resolved this issue for our customer recently, via our Server Management Services.

What to do if CentOS 8 virtual servers won’t boot after OS upgrade?

Have you run into a bit of trouble after an OS upgrade? Do you find yourself looking at the screen below?

Worry not, this often occurs when the new boot scheme is not supported by your hypervisor grub boot image. The new upgrade results in overwriting the bootloader option as well as the config files in order to support the BLS. In other words, you need to disable it as well as regenerate the bootloader’s main configuration file.

An easy solution

Although this is a common issue, there is no news of a permeant fix. So you will notice this issue each time you upgrade your OS. Our Support Engineers recommend following these steps for an easy fix.

Reboot VM in Recovery mode

  • First, log in to client portal. Then click the recovery button.
  • After that, go to server details section.
  • Then, click the recovery button.

You will get the following screen:

This puts the VM in Recovery mode.

After that, log in to the server as root via console or SSH.
We would like to remind you that password in the recovery mode is the same as the password for root log in via console or SSH. Click the show button in the interface to get the password.

After this, follow these steps:

  • Run the following command if the primary VM disk is recognized as /dev/vda. It prepares the chroot environment.
    #mount /dev/vda1 /mnt && mount –bind /proc /mnt/proc/ && mount –bind /dev /mnt/dev&& mount –bind /sys /mnt/sys && chroot /mnt /bin/bash -l
  • Next, run the following command to change the bootloader option as well as regenerate configuration file.
    #sed -i ‘s/GRUB_ENABLE_BLSCFG.*/GRUB_ENABLE_BLSCFG=false/’ /etc/default/grub
    #grub2-mkconfig -o /boot/grub2/grub.cfg
  • In case the last command in the previous step is successful, exit chroot environment. After that, reboot the virtual server in normal mode with the command:
    #exit
    #cd / && umount /mnt/proc && umount /mnt/dev && umount /mnt/sys && umount /mnt
  • Then click reboot in the client portal to reboot. We would like to remind you that rebooting in ssh will again boot you in recovery mode.

[Looking for assistance with Server Management? Give us a call.]

Conclusion

At the end of the day, we learned what to do if your CentOS 8 virtual servers won’t boot after OS upgrade.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF