From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Make the new filesystem, rsync the old SSD to the new one (making sure to use rsync -ax to copy everything properly, also add -H if you use hardlinks), update fstab UUID, regenerate GRUB configuration and you're good to go.
I have a 10 year old install that's survived moving several disks and computers, it works just fine.
-x (alias --one-file-system) means "don't cross filesystem boundaries"; is that what you meant? Or did you mean -X | --xattrs?
Edited because I wrote some things before that were incorrect.
Don't forget to change the fstab filesystem type when updating the UUID as well (yes, I've made this oops before).
And maybe also -ASX for ACLs, sparse files and xattrs
This is likely what I will do now that I have given it some thought. This will bring over all of my installed apt and snap packages, right? And they will both be aware and know how to update from there?
I have the NVMe prepped. It has a fresh Ubuntu install of the same version, but on btrfs. I could probably even snapshot it before I get started to make sure I can roll back and try again if I fuck up. And worst case, I can just reinstall the OS on that partition, as it would touch my existing install. It feels pretty safe to try. Worst thing that can go wrong is I waste my time.
The amount of changes you’d need to make to get Linux to boot on a different partition format and drive would be a lot of work. It would be much faster to install a new copy of Linux to the nvme drive and copy the files from the ssd post install before decommissioning the old drive.
It's really not that bad, unlike Windows you can pretty much just rsync the data over, update fstab and it's good to go.
I disagree, you usually just need to get /boot and your EFI things right on the new disk, rsync stuff over and fix any references to old disks in /etc/fstab and maybe your grub config and you are done. I have done this migration>10 times over the years onto different filesystems, partition Layout and raid configurations and it's never been particularly hard.
What's the magic that's needed to make EFI happy?
Most of the time, it's enough to copy the whole EFI partition to the new machine and update whatever boot entries are in there to point to the right new partitions.
In case of a switch to something like zfs, it's a bit more involved and you need to boot a live Linux, chroot into the new "/" with /boot mounted and /dev, /proc, /sys bind mounted into the chroot.
Then you can run the distro-appropriate command to reinstall/ update grub into the EFI partition and they will usually take care of adding the right drivers.
That’s true if everything is supported on the current kernel. I might just be very out of touch/date here but is btrfs built in to the kernel? I was thinking he’d need to have a different kernel/loaded modules on it
Btrfs is in the mainline kernel since 2.6.29, that's 14 years ago my friend 😃
It's included in every major distro for a long long time.
Well dang it’s been a while since I tried it then! I keep hearing how it’s unstable in comments so I tend to assume its fairly new even when I should know better lol