I've already done a dnf upgrade to F33 on my system that hasn't had a "clean" install since at least F24, but at some point I'd like to migrate to btrfs w/o LVM.
My current plan is to replace my current SSD (500GB Samsung EVO 970 m.2) to a 1GB version with the process being loosely:
1. Add the new m.2 disk (via PCIE adapter) 2. Perform a clean install to it 3. Capture all the RPMs I have installed and install them on the new install 4. Migrate /etc and /var (where appropriate) 5. Move the new SSD to the MB m.2 slot and remove the old SSD and adapter (save for another system).
Any better options? /home is already a separate 3TB spinning disk so that won't change for now.
Thanks, Richard
On Fri, 6 Nov 2020 09:02:06 -0600 Richard Shaw wrote:
- Perform a clean install to it
You don't necessarily need a clean install. You can partition and format the new ssd then just rsync everything to it and use grub2-install to make it bootable and edit all the grub.conf, grub env files, fstabs, etc to change the UUID to the new UUID strings.
Don't know if you'd consider that a better option or not :-).
It is the way I always do installs by first installing to a virtual machine then using guestmount and rsync to get the install off the virtual machine and onto the partition I'm installing (then I use the configfile option from a stand alone grub partition which is the only one that actually boots).
On Fri, Nov 6, 2020 at 9:21 AM Tom Horsley horsley1953@gmail.com wrote:
On Fri, 6 Nov 2020 09:02:06 -0600 Richard Shaw wrote:
- Perform a clean install to it
You don't necessarily need a clean install. You can partition and format the new ssd then just rsync everything to it and use grub2-install to make it bootable and edit all the grub.conf, grub env files, fstabs, etc to change the UUID to the new UUID strings.
Don't know if you'd consider that a better option or not :-).
I kinda wanted to see how the installer setup the new btrfs subvolumes but guess I could do it manually :)
Also, I wanted to try going without dedicated swap (easy enough not to copy over) with swap on zram and standard OOM setup.
It is the way I always do installs by first installing to a virtual machine then using guestmount and rsync to get the install off the virtual machine and onto the partition I'm installing (then I use the configfile option from a stand alone grub partition which is the only one that actually boots).
Interesting method!
Thanks, Richard
I currently don't know if the installer could be forced to install grub to an destined disk/ssd when two are in the box: so I would place the new ssd in the right place *before* installation.
I also don't know if "over-provisioning" is (still) necessary. is that on your radar ?
hint: I'm used to tag the edited files under /etc with # <my-name> to find them all quickly with fgrep -R <my-name> /etc/*
On 11/6/20 11:00 AM, sixpack13 wrote:
I currently don't know if the installer could be forced to install grub to an destined disk/ssd when two are in the box: so I would place the new ssd in the right place *before* installation.
There is an option, somewhat obscure, to set the boot loader device.
thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards.
On Fri, Nov 6, 2020 at 1:27 PM sixpack13 sixpack13@online.de wrote:
thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards.
For EFI, won't the bios find the EFI partition anyway?
Thanks, Richard
On 11/6/20 11:48 AM, Richard Shaw wrote:
On Fri, Nov 6, 2020 at 1:27 PM sixpack13 <sixpack13@online.de mailto:sixpack13@online.de> wrote:
thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards.For EFI, won't the bios find the EFI partition anyway?
That too, but it can get complicated if you end up with more than one disk with an EFI partition on it.
On Fri, Nov 6, 2020 at 1:56 PM Samuel Sieb samuel@sieb.net wrote:
On 11/6/20 11:48 AM, Richard Shaw wrote:
On Fri, Nov 6, 2020 at 1:27 PM sixpack13 <sixpack13@online.de mailto:sixpack13@online.de> wrote:
thanks for clarification. I wasn't sure. It want hurt to put the disks in the right place even it is planed to do so in any case afterwards.For EFI, won't the bios find the EFI partition anyway?
That too, but it can get complicated if you end up with more than one disk with an EFI partition on it.
For the EFI partition I was going to use gparted and "move" it to the new disk. I could also just remove the EFI flag (or whatever it's called) and leave it alone.
Thanks, Richard
On 11/6/20 11:59 AM, Richard Shaw wrote:
On Fri, Nov 6, 2020 at 1:56 PM Samuel Sieb <samuel@sieb.net mailto:samuel@sieb.net> wrote:
On 11/6/20 11:48 AM, Richard Shaw wrote: > On Fri, Nov 6, 2020 at 1:27 PM sixpack13 <sixpack13@online.de <mailto:sixpack13@online.de> > <mailto:sixpack13@online.de <mailto:sixpack13@online.de>>> wrote: > > thanks for clarification. > I wasn't sure. > It want hurt to put the disks in the right place even it is planed > to do so in any case afterwards. > > > For EFI, won't the bios find the EFI partition anyway? That too, but it can get complicated if you end up with more than one disk with an EFI partition on it.For the EFI partition I was going to use gparted and "move" it to the new disk. I could also just remove the EFI flag (or whatever it's called) and leave it alone.
Yes, either of those would work.
-
Richard Shaw -
Samuel Sieb -
sixpack13 -
Tom Horsley