Migrate EndeavourOS installation to new NVME disk

My new NVMe SSD has just been delivered! Yay!
I want to migrate my existing installations of EndeavourOS and Ubuntu to the new disk.
Is it better to install EndeavourOS from scratch and then migrate user directories and the install apps etc as required,
or would copying partitions from the existing hard disk to the new disk work?
There are a bunch of ext4 partitions and one btrfs partition.

There is always a way to do ANYTHING on Linux, but which is easiest/most effective is not always as obvious. For one thing, size matters - how big is what is to be ‘moved’? How large is the m.2 disk? How many partitions are involved here, and do they all move?

Possibilities that come to my mind quickly include setting up the partitions, and rsync’ing them across - or ensuring they match in size, and dd’ing them across - or (what I would probably do) - make sure things are backed up with TImeshift, reinstall to the best setup you know of (partition-wise) and then restore your current setup to the new install.

I’m sure there are more ways - and perhaps others have better ideas (probable) but to me the reinstall/timeshift seems like the surest way NOT to mess up and lose stuff (dd has an annoying habit of doing what you tell it, not what you meant :grin: )


1 Like

many many ways to do this… clonezilla dd e.t.c. but mostly needs some changes to work fully afterwords like uuid’s for partitions

1 Like

I did some reading up and I will probably I use e2image for ext4 partitions.
btrfs has send and receive so I might just give that a shot.
@joekamprad yes if I copy images I will have to change uuids as well as matching fstab entries.
The bit that I am not sure about is the /boot/efi partition.
After “copying” the partitions I think I can boot in the systemrescue usb and from there to the EndeavourOS partition copied to the nvme.
After that I’m hoping that

grub-mkconfig -o /boot/grub/grub.cfg
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS

will fix things.

You could bypass grub entirely if you wanted - rEFInd for instance will direct boot your kernel, meaning you don’t need grub to get going. We have a wiki entry on it now (cough, cough) if you’re not familiar with it… :grinning:


Finally someone with intelligence. rEFind is the way to go Grub is just so so yesterday. :sunglasses:

You only need a EFI partition of 200 MB.




You left one out… :grin:

And there’s more on the end of it, too
1 Like

I just run refind-install script and without any efforts on my part it allows me to boot into linux, bsd and grub :scream_cat: The names of the entries are wrong, but I guess it is configurable.
I wonder why I was torturing myself with grub configuration…

edit: well, I should probably say non-intuitive as to the entries names rather than wrong

Thank you for the wiki, @freebird54 :slight_smile:

Yeah - it’s amazing what it’ll do on its own. You might want to check on the microcode front if you have an Intel or an AMD processor though. Arch-based distros like to add it in the boot process as described in the wiki - but at least it’s a one-time config in the auto-generated conf file co-located with the kernel files… one thing rEFInd skips!

1 Like