How to Manually Boot CloudLinux 8.10 from GRUB Shell Print

  • 0

When your CloudLinux 8.10 server fails to boot and drops into the GRUB shell, follow this step-by-step guide to manually boot the system.

Step 1: Access the GRUB Shell

If your server is stuck at the GRUB rescue or command prompt, you will see a screen similar to this:

shell
grub>

At this point, you need to manually specify the root partition and load the Linux kernel.


Step 2: Identify Available Disks and Partitions

First, list the available disks and partitions:

 
ls

You will see output similar to:

(hd0) (hd0,gpt1) (hd0,gpt2) (hd0,gpt3) (hd0,gpt4)

Each (hd0,gptX) represents a partition on the disk.


Step 3: Find the Root Partition

Check the contents of each partition to find where your root filesystem (/) is located:

ls (hd0,gpt3)/

If you see directories like:

bin/ boot/ dev/ etc/ home/ root/ usr/ var/

This means (hd0,gpt3) is your root partition.


Step 4: Find the Boot Partition

Since /boot is on a separate partition, check (hd0,gpt2):

ls (hd0,gpt2)/

If you see kernel files such as:

vmlinuz-4.18.0-553.34.1.lve.el8.x86_64 initramfs-4.18.0-553.34.1.lve.el8.x86_64.img

Then (hd0,gpt2) is your boot partition.


Step 5: Manually Boot the Server

Now, execute the following commands:

1. Set the Root Partition

set root=(hd0,gpt3)

2. Load the Linux Kernel

linux (hd0,gpt2)/vmlinuz-4.18.0-553.34.1.lve.el8.x86_64 root=UUID=e9bc4ed0-0f48-4433-9a3a-5f7d56243a0c ro

Explanation:

  • (hd0,gpt2)/vmlinuz-4.18.0-553.34.1.lve.el8.x86_64 → The kernel file in the /boot partition.
  • root=UUID=e9bc4ed0-0f48-4433-9a3a-5f7d56243a0c → Specifies the root partition.
  • ro → Mounts the root filesystem as read-only for initial boot.

3. Load the Initramfs

initrd (hd0,gpt2)/initramfs-4.18.0-553.34.1.lve.el8.x86_64.img

4. Boot the System

boot

Step 6: Fix GRUB to Prevent Future Issues

Once the server boots successfully, follow these steps to repair GRUB permanently.

1. Navigate to the EFI Directory

cd /boot/efi/EFI

You should see two folders: almalinux and centos.

2. Identify the Correct Bootloader

Check which folder contains the required GRUB and bootloader files:

ls -l almalinux/ ls -l centos/

If centos/ contains the files grub.cfg and shimx64.efi, it is likely being used as the bootloader.

3. Regenerate the GRUB Configuration

If the grub.cfg file inside centos/ is missing or empty, regenerate it:

grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

4. Verify EFI Boot Entries

After fixing the GRUB configuration, check the EFI boot entries:

efibootmgr -v

If needed, manually add a CloudLinux boot entry:

efibootmgr --create --disk /dev/nvme0n1 --part 1 --loader \\EFI\\centos\\shimx64.efi --label "CloudLinux" --verbose

5. Reboot the Server

reboot

Conclusion

This guide helps you manually boot a CloudLinux 8.10 server from the GRUB shell and then permanently fix GRUB to avoid future issues.


Was this answer helpful?

« Back