Last post by thepapahippo -
Thanks for the feedback. I now realise that my first post was rather sketchy, leaving me wide open to be patronised. Don't worry; not the first time, probably not the last.
Here's some follow-up/ background info:
I've been using Unix (later linux) since the 1980s and so am quite familiar with the command line tools like less, more, man etc. but I prefer to use a GUI these days (actually since the days of FVWM).
I'm not a full-blooded distro-hopper; more of a distro drifter, slowly drifting over the years (Yggdrasil->Slackware->... Ubuntu ->Mint->MX Linux), always with a good reason. (My Mint installation is primarily to give support to other users here in NL, where Mint is still very popular - whatever distrowatch etc. may say!).
While I was employed as a Linux consultant, I had to follow the local accepted wisdom and 'embrace' systemd. Now that I'm retired, I sometimes like to plough my own furrow; specifically, I want to move away from systemd, and of the several alternatives, runit seems to fit my style and needs best. This gives me a number of options. I'm currently also evaluating antix, which is less polished than Mx Linux (and probably Artix), but means I can use an old - rescued from the dump - laptop for testing, and worry less about trashing existing installations.
Last post by ####### -
If you are doing a UEFI install and don't have a UEFI partition as your lsblk output indicates, there's no partition for grub to be installed into, so that's going to be a problem. The UEFI partition can be located anywhere on the drive. It's got to be the right FS type and flagged correctly as described in the linked wiki page. Alternatively switch to BIOS boot and enable that in your BIOS menu too. I don't think there's any advantage to UEFI except stuff that's probably not relevant to most home use. smartmontools can tell you more about your drive health status if you are concerned about it. That seems unlikely if other distros work though.