After problems years ago I always now do a fresh install and as this always goes well I've seen no reason to do anything different.
I have /home on a separate partition. I tend to boot into a live CD, mount my home partition and rename my home folder, e.g. mv martin martin_old. Mount the root partition and copy any config files I want to keep. Then unmount both partitions and install with the same username (making sure I don't format the home partition). Once booted into my new install, if the pid is different (it usually isn't) I recursively change ownership and group of my old folder to my new username. Then I selectively copy what I want from my old home folder to my new - whether that's normal files and folders or configuration files and scripts I've spent years crafting.
Once that's done I delete my old home folder and then re-install any applications I use.
Works well for me. If I want to change partition sizes or types then I use an external hdd as a backup,
Good luck.
Martin
On 19/04/2022 09:37, Mark Rogers wrote:
Over the years I have upgraded my Ubuntu desktop twice a year using do-release-upgrade.
My root drive SSD is nearly full so I've just bought a bigger one, and I'm looking at migrating across to it. But... Ubuntu 22.04 is nearly here, so maybe it would make more sense to clean things up with a fresh 22.04 install on the new SSD instead?
I know lots of people avoid upgrades and just do a clean install retaining /home (or something along those lines) but I've never done it myself. Is it the right way to go?
It's a desktop PC, but 99% of the time I access it via SSH. Over the years it's had all sorts of stuff installed and uninstalled (or installed and no longer used but still there). So a clearout definitely seems like a good idea. So it seems like what I ideally want is a managed migration where I choose which things I have on the old install I migrate and which I leave behind. Is this going to be more hassle than it's worth?