Linux machine can't mount a disk and boot.

Challenge

A Linux machine can't mount a disk and boot.

Cause

A wrong disk label is written in fstab, so the machine can't mount the disk and boot.

Solution

1. Type in your root password and press "Enter" to log in to a maintenance session.

2. Run blkid command to find out the UUID of the boot partition. This partition has the label "hx_lock":

3. Open the /etc/fstab file with a text editor of your choice. The specified boot partition will have a label that does not exist anymore:

4. Replace "LABEL=<label>" with "UUID=<uuid>" using the UUID from the "blkid" output in Step 2:

5. Save your changes and reboot. The system should start normally.

• Related Articles

• Why a Linux machine doesn't boot in the Cloud Site, "dracut" in the console

  Challenge Linux machine doesn't boot in the CS, "dracut" in the console. Cause Linux machine doesn't boot in the CS, enters the dracut debug mode instead: Solution RHEL/CentOS uses a dracut system. By default, dracut-initramfs does not include a qemu ...

• Why a machine fails to boot on target site with the message "Timed out waiting for device"

  Challenge A machine fails to boot with the message "Timed out waiting for device". Cause During a cross-hypervisor replication, storage device names might change (e.g. /dev/sda might become /dev/vda)  Solution Use device paths in /etc/fstab for Linux ...

• Network interface is changed during a failover and network becomes unavailable for a VM running Linux OS

  Challenge Sometimes network interface is changed during a failover and network becomes unavailable. Cause Some Linux machines require additional configuring. Solution To resolve this issue, the source machine can be configured prior to any ...

• Failover machine running Windows 2008R2 doesn't boot on Google Cloud Platform

  Challenge A Windows 2008R2 failover machine doesn't boot on the GCP cloud. Solution Failover machines need certain packages pre-installed on their systems in order to operate on target clouds : Please note that a Windows 2008R2 machine requires ...

• Non-working networking in failover\failback Linux devices.

  Challenge Non-working networking in failover\failback Linux devices. Cause The issue may appear due to the naming of interfaces in Linux. Interface names are based on the NIC type used, so while switching hypervisor (for a Cloud Site or a failback) ...