Elevate: Leapp upgrade failed to mount filesystems special device /dev/md0

Symptoms

During Elevate, the leapp upgrade returns the following failure messages:

[ERROR] # Upgrade process failed at stage=3 ; Running: tail -f /var/log/elevate-cpanel.log
* 2025-05-15 05:22:38 (9939) [ERROR] Last Error:
* 2025-05-15 05:22:38 (9939) [ERROR]
* 2025-05-15 05:22:38 (9939) [ERROR] Server is currently running CentOS 7 after distro upgrade.
* 2025-05-15 05:22:38 (9939) [ERROR] Upgrade to AlmaLinux 8 did not succeed.
* 2025-05-15 05:22:38 (9939) [ERROR]
* 2025-05-15 05:22:38 (9939) [ERROR] Please review your upgrade logs and correct the problem.
* 2025-05-15 05:22:38 (9939) [ERROR] `leapp` logs are located at:
* 2025-05-15 05:22:38 (9939) [ERROR] /var/log/leapp/leapp-report.txt
* 2025-05-15 05:22:38 (9939) [ERROR] /var/log/leapp/leapp-report.json
* 2025-05-15 05:22:38 (9939) [ERROR]

When checking the leapp report log, it shows failure to mount devices:

Command ['/bin/mount', '-a'] failed with exit code 32.

Additionally, the system log messages file shows more information:

May 15 06:01:15 localhost upgrade[1]: mount: special device /dev/md0 does not exist

Description

The Leapp upgrade doesn't support loading software raid during in-place upgrades. This failure usually appears when the fstab loads a device as "/dev/md0", most commonly. It will cause the Leapp upgrade process to fail right before it transitions to stage 4.

We've opened an internal case for our development team to investigate this further. For reference, the case number is CPANEL-47288. Follow this article to receive an email notification when a solution is published in the product. 

Workaround

1. Obtain the block device ID for md0:

blkid /dev/md0 

2. Change /dev/md0 in "/etc/fstab" to the block device ID UUID name via text editor ( vi, vim, nano ):

From: "/dev/md0"

To: UUID="XXXXXX-XXXXX-XXXX-XXXXXXXXXXXX"

3. Save the /etc/fstab file

4. Restart cPanel elevate

/scripts/elevate-cpanel --continue