I think I’m going to have to dual boot. My current Fedora 32 is good, and I don’t really want to touch it, but it’s sitting on a 256 gb nvme drive. I know that’s not enough to house windows and my linux install so…
My board has a second nvme slot (aorus elite x570 wifi/3700x) and I could probably swing a new 512gb nvme drive.
Am I starting from scratch or is there a way forward without reinstalling my fedora install? maybe clone my current install to the new drive and then install windows on the 256? I’m worried about the boot loader though. I don’t want windows windowsing my linux.
I dual boot with two Nvme SSD’s. All is working fine here, I’ve really never had any issues dual booting from separate drives. When I would dual boot on one shared drive, sometimes Windows update would overrun grub and boot into the Windows bootloader making grub inaccessible. As grub is now nstalled on the Linux Nvme, and Windows on it’s own, I haven’t had any issues since. Also grub finds the Windows installation just fine.
One more thing “clone fedora” means usually cloning 2 partitions. EFI (fat32) and Fedora install (Ext4).
Generally you have to clone all partitions from old disk to new and resize ext4 one that contains Fedora.
EFI partition mounts usually into /boot/efi in newer distros.
Boot partition is something else, and usually extX. It is used when boot loader (i.e. grub) doesn’t directly recognize your OS filesystem.
Yes, if your filesystem is recognized by bootloader its easier to just go straight into it. Regardless of EFI.
However EFI partition is needed for UEFI bios to get loader from, based on EFIVARS. And it has to be fat32 according to rfc.
Of course if you dont have UEFI bios then its not needed , because bootloader is in MBR instead of EFI partition. However I would still suggest to make one on new installs, in case if you upgrade motherboard later.
Of course additionally its connected to MBR/GPT partition tables, but its another topic, and Linux is not really affected by this much, unless you’re dual booting and your disks are bigger than 2TB.
That reminds me, @TheF1sh, if your old drive is still MBR, it would be good idea to partition new disk with EFI on GPT partiton, and clone partitions instead of whole disk.
It’s bit more complicated, as it involves reinstalling bootloader from chroot, however since you have backup of your system anyway, you can try it without any consequences
I was in a similar situation sometime back. I just installed Windows on a new media device and ran the existing Linux installation as a VM by using passthrough. It worked pretty well and I still can dual boot the other one with minimal modifications. You can go through my blog post if you are interested.
Well, fwupdmgr is right
But if its about microcode update I cannot elaborate. I know principle, but not practice. So maybe someone else will explain. Also embedded systems have their own quirks, and I don’t have T495 laying around, so I don’t want to mislead you.
All I can say that on my E580 (yey thinkpads ) and Manjaro I have UEFI enabled, disk with GPT, and fwupdmgr doesnt warn me about anything Also I have 2 mounts extra compared to MBR boots(usually called CSM in new bioses):
/dev/nvme0n1p1 on /boot/efi type vfat
efivarfs on /sys/firmware/efi/efivars type efivarfs
As luck would have it, with a black friday deal on the 970 1tb nvme and a side job that paid quicker than expected I’m going to go that route for my linux drive and then have the 256 for windows alone.
One question about swap space. Does it need to be on the same drive as the root? I’ve been running the 3 partition swap-root-home. would there be any advantage to going root-home on the new drive and swap on the other m.2 through the chipset? I have 32gb ram and honestly have never seen the swap even hit while monitoring it. Isn’t it more for low ram situations?
Swap is there for when you run out of system ram for tasks, as well as being there for when/if you hibernate your PC. To save power without losing your work it compresses your session all in to the swap space for a quick bounce-back when you press the power button or space bar, since the system ram is also powered down during hibernate.
I’d add the warning that if you clone a partition exactly, it has the same UUID as the original, and booting with both present can cause confusion, both to OS and user. (Confused the hell out of me when I did it.) If you really want to have both present, gparted can put a new UUID on one of them, but that messes with grub and /etc/fstab if they use UUIDs.