Cloned AlmaLinux 10 Fails to Mount /home

[Ray Fong]

Hi:

I am attempting to clone an AlmaLinux 10.2 machine with a SSD drive using Clonezilla v3.3.3-15. I have tried both cloning to an image and cloning disk to disk. Both times, the resulting cloned machine fails to mount /home. Failed output from journalctl -xb:

Jul 16 06:22:14 systemd[1]: dev-disk-by\x2duuid-a7a95c0e\x2d2e92\x2d4219\x2db0d7\x2dcb104762814b.device: Job dev-disk-by\x2duuid-a7a95c0e\x2d2e92\x2d4219\x2db0d7\x2dcb104762814b.device/start timed out.
Jul 16 06:22:14 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-a7a95c0e\x2d2e92\x2d4219\x2db0d7\x2dcb104762814b.device - /dev/disk/by-uuid/a7a95c0e-2e92-4219-b0d7-cb104762814b.
░░ Subject: A start job for unit dev-disk-by\x2duuid-a7a95c0e\x2d2e92\x2d4219\x2db0d7\x2dcb104762814b.device has failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit dev-disk-by\x2duuid-a7a95c0e\x2d2e92\x2d4219\x2db0d7\x2dcb104762814b.device has finished with a failure.
░░
░░ The job identifier is 226 and the job result is timeout.
Jul 16 06:22:14 systemd[1]: Dependency failed for home.mount - /home.
░░ Subject: A start job for unit home.mount has failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit home.mount has finished with a failure.
░░
░░ The job identifier is 225 and the job result is dependency.
Jul 16 06:22:14 systemd[1]: Dependency failed for local-fs.target - Local File Systems.
░░ Subject: A start job for unit local-fs.target has failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit local-fs.target has finished with a failure.
░░
░░ The job identifier is 221 and the job result is dependency.

After logging in while in emergency mode, I comment out /home from fstab and the machine boots up successfully. Output from lsblk:

NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1            259:0    0 931.5G  0 disk 
├─nvme0n1p1        259:1    0   600M  0 part 
├─nvme0n1p2        259:2    0     2G  0 part /boot
└─nvme0n1p3        259:3    0 928.9G  0 part 
  ├─almalinux-root 253:0    0    70G  0 lvm  /
  └─almalinux-swap 253:1    0  15.4G  0 lvm  [SWAP]

I see that there is no "almalinux-home" lvm. But more surprising, there is NO output from pvdisplay, vgdisplay, or lvdisplay. It's like the clone did not re-create these items.

Any suggestions on how to proceed?

Thanks for your help.

[Ray Fong]

In case someone else is having this problem, I received a fix from the Almalinux forum:

This is a known RHEL 10.2 issue caused by the cloned LVM system.devices file.

In emergency mode, run:

rm -f /etc/lvm/devices/system.devices
vgimportdevices -a
reboot

[Steven Shiau]

Thanks for reporting this issue. We have added a mechanism to clean the hardware whitelist in the LVM configuration.
Please give testing Clonezilla live >= 3.3.3-16 or 20260718-* a try:
https://clonezilla.org/downloads.php
Please let us know the result if you test it. Thanks.

[Ray Fong]

I tested clonezilla-live-20260718-resolute-amd64 and it works, thanks!

[Steven Shiau]

Great. Thanks for confirming that.