Cloned disk with Clonezilla, error at boot

Cloned from my Hard Disk to a new NVMe SSD, and yet when trying to boot from it, I’m given the error “Reboot and Select proper Boot device”

Which tool should I use to move everything from my hard disk to my SSD? They’re both 2TB, and yet I haven’t been able to boot from it no matter which cloning method I use. It’s weird, seen as the NVMe is partitioned correctly; 500M for the /boot/efi mount, 1.8TB for the root mount, and 33.5GB for Swap, since I have 32GB RAM.

What should I do now? Try a different cloning method? Meddle with the boot files? I’m at a loss for what to do!

Were you using grub before? Or was it systemd-boot?

Edit: I guess what I’m asking also. Are you cloning the whole disk that was previously bootable?

Hiya, the hard disk is still bootable, and I cloned the entire thing with the device-to-device feature of Clonezilla. I then tried to boot from the SSD, but it had mounted the SSD’s partitions except for root. I discovered that this was caused by cloned UUIDs of the partitions, so I generated new ones and assigned the three NVMe partitions a new UUID, then updated /etc/fstab

Using grub rather than systemd-boot, and yes I cloned grub too. As far as I know, it was a block-by-block duplication of my hard disk, which is still bootable.

Was the previous device NVMe SSD? I would assume if it is not I had copied something to cause it. What should I do now? Try a different cloning method? Meddle with the boot files? I’m at a loss for what to do!
i would honestly back up whats important and re-install. (saves headaches)

1 Like

My entire system is a botch, it has a patched kernel, VR stuff, and generally it’d be a bigger headache to reinstall.
P.S. No, my previous system was (and still is) on a slow hard disk, the SSD was an upgrade I needed as accessing files got way too slow on the hard disk.

I was able to boot into what seemed to be the SSD, but running lsblk shows that I’m still mounting on the hard disk, despite selecting the SSD in the boot menu and despite editing the /etc/fstab file on the SSD’s system.

Seems a re-install/backup would still save headaches

Is it or isn’t it? none of us are on your machine

As I said in my previous message, running lsblk shows that I’m still mounting on the hard disk, despite selecting the SSD in the boot menu.

Yer someone more useful than me may chime in, just trying to save you a headache later on

Sorry, I know it’d be better to reinstall, but I’ve made so many changes to my system that thinking what it would take to move everything again just makes me shiver.

Have you considered this is what is causing issues?

Literally takes me 30 minutes tops to re-install and reset things to how I like (this is including the downloads) just what have you changed that makes this an unacceptable answer (you may have a very valid one which is why I ask)

Did you try to boot without the harddrive connected ?

I have not, but update: I somehow booted from the SSD, but it couldn’t find the devices because the UUIDs of the partitions are wrong and outdated in grub. How do I update them?

That makes sence because the UUIds are still the ones from your harddrive I guess.
You have to findout what the new ones are and add them to fstab following the method mentioned in this link https://discovery.endeavouros.com/storage-and-partitions/how-to-permanently-mount-external-internal-drives-in-linux/2022/02/ and go to point 5.

I solved it! I updated the UUIDs manually by generating new ones and assigning them to the various partitions with tools such as fatlabel and swaplabel, and I then updated the /etc/fstab file.
Then, booting into the SSD (not selecting the raw SSD in the boot menu of my motherboard but selecting the voice that also had eother “UEFI OS” or “endeavouros” in it together with the SSD’s name), and it let me to a black background grub.
Editing the grub commands showed the old UUIDs, so I booted back into my hard disk, arch-chrooted into the mounted SSD, ran grub-mkconfig and then booted into the right voice of the SSD in the boot menu, and it worked!
Running lsblk shows the mounted system is all on the SSD!

1 Like

Great stuff time to raise the purple flag
:enos_flag:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.