Can't clone from SSD to NVME

[Anonymous]

Hi, I'm having trouble when cloning an Alma Linux image from SSD to NVME.
First I tried using Rescuezilla, but I couldn't find anything, then I decided to use Clonezilla and I got this warning.
The system starts in Emergency Mode, what could I do to solve this?

[Rescuezilla]

So Rescuezilla didn't display your drives to create a backup, so you shutdown and booted into a Clonezilla environment directly to conduct a clone?

Then you created a backup image using Clonezilla (titled 2025-01-29-11-imgKDEPlasma in your screenshot, so not likely an image created by Rescuezilla), and restored it to an NVMe disk.

Just noting this is technically not a Rescuezilla question, but a Clonezilla question (especially since you booted into Clonezilla directly)? If so, it should ideally be asked here: https://sourceforge.net/projects/clonezilla/

But I'll provide you an answer: GRUB Rescue Mode is when the GRUB bootloader is unable to find a partition to mount to continue to boot. A similar concept called Systemd Emergency Mode happens when /etc/fstab is unable to mount a partition during bootup. As I wrote on the Rescuezilla FAQ:

Q: I restored my Linux backup using Rescuezilla. It boots past the GRUB bootloader fully, but the Linux boot gets stuck at "Rescue Mode" login prompt. How do I fix this?
A: For modern systemd Linux environments (such as Ubuntu 18.04), the partitions listed in the /etc/fstab file must be present for the system to complete booting. This means if the hard drive environment does not match exactly, the system will enter Rescue Mode until the /etc/fstab is modified to only refer to the drives which are present in the system.

Fixing a machine in this situation requires logging in at the Rescue Mode prompt, remounting the root partition as read/write, modifying /etc/fstab to remove the line of the partition which is no longer present, then remounting the root partition as read-only before hard rebooting the machine. There are plenty of guides on the internet to help fix this particular issue. If you need further help, post on the support forum and you will receive detailed assistance for as long as it takes to fix your issues.

Please note, in some older Linux distributions it's not the partition's UUID that is used by /etc/fstab but the partition's device node (eg. /dev/sdc1). This means the Linux boot is expecting a hard drive connnected to an identical numbered SATA port! But don't worry, any problems can be resolved by modifying /etc/fstab. As mentioned, if you need more help please ask for it on the support forum.

You can see from the final lines of your screenshot Clonezilla is saying it you may need to manually modify /etc/fstab. The solution requires in systemd emergency mode requires manual modification of /etc/fstab.

A similar situation happens for GRUB Rescue Mode (which is sounds like you're stuck in).

[Mateus Lidonis Blanco]

I just created an account here, much better

Q: So Rescuezilla didn't display your drives to create a backup, so you shutdown and booted into a Clonezilla environment directly to conduct a clone?
A: No, I did the whole process in both Rescuezilla and Clonezilla, the end result was the same

I tried Rescuezilla again, but this time, I took some photos, hope it helps you guys to help me :)
I'm kinda new in the Linux environment, edit /etc/fstab, mounting and unmounting disks doesn't seem so easy

[Rescuezilla]

Thanks for all the context. The error in photo8 doesn't appear to be relevant -- it's just saying Rescuezilla couldn't resize a partition to best utilize the space.

But importantly on photo8: you probably can scroll down further, I think you missed an error message displayed in the restore summary.

Here's what I think your issue is. Notice on your original disk sda, you have five partitions: your first two are EFI-related boot partitions, but the final partition is an "LVM" containing three LVM logical volumes, titled root, swap and home. (photos 1 and 2)

But on your destination disk nvme0n1 you have the first two EFI related partitions as intended, but the final partition only has two LVM logical volumes: root and swap (photo11), which your /etc/fstab is correctly pointing to (photo12).

Therefore, I think the restore appears to have failed your your "home" logical volume potentially.

I suspect information should be displayed in photo 8 (first photo of this post), but probably is missing due to not scrolling down further in the summary.

Your backup summary suggests the backup was a success for this partition:

Also side note: GParted Partition Editor isn't the absolute best at navigating and viewing Linux Logical Volumes (and their constitutent physical volumes "PVs", logical groups "LGs" and logical volumes "LVs"). Rescuezilla uses the command-line tools like pvscan, lgscan and lvscan internally. Rescuezilla doesn't yet include a nice graphical advanced LVM-supporting partition editor yet.

[Mateus Lidonis Blanco]

Oh yeah, I missed some messages from restore summary. Here it says that successfully restored all three LVM, right? (home, root and swap)
My issue is related to that GRUB bootloader message?

[Mateus Lidonis Blanco]

Hello, do you have any idea? I'm stuck on this....
And I just tested from a NVME to another NVME (exactly the same model), and it didn't work

[Mateus Lidonis Blanco]

I'm using Alma Linux KDE Plasma. Just saw on the website that it's a live media image, is this a problem? Can I clone live media images?