Multiple EFI partitions suggests this machine has had a second drive added to it from an different machine. Peculiar, but not necessarily a bad thing. The NTFS recovery partition on nvme0np1 tells me that this drive is the main boot drive for Windows. You can verify this by cross-referencing this disk layout against what diskmgmt.msc shows when you boot into Windows. One of either nvme0n1p4 or nvme0n1p5 will be the C: drive and I suspect the other will be a recovery partition, too. Recovery partitions are a good thing to have in general, but you don't strictly need them. Fortunately, you can delete and recreate them pretty easily.Code:
$ lsblk -fsdc ├─sdc1│ vfat FAT32 EFI-SYSTEM│ 782B-8DC7 471.5M 0% /boot/efi└─sdc2 btrfs homeMX f4296384-30d1-42a1-9ad5-e403e9ce4695 149G 35% /home ├─nvme0n1p1│ ntfs Recovery│ BA2811C428118095 ├─nvme0n1p2│ vfat FAT32 BOOT EFI│ 1814-70CD ├─nvme0n1p3│ ├─nvme0n1p4│ ntfs 869204D19204C81F ├─nvme0n1p5│ ntfs 228CEA538CEA20D1 └─nvme0n1p6 btrfs rootMX23 1200a831-9c79-4104-8867-15d8744c0cc8 101.7G 8% /
What I would do is backup my data, use the "resize/move" option in gparted from a live USB to push the MX root partition to the end of the drive, run MX Boot Repair to make sure I'll still be able to boot to it, and then verify it still works. If I didn't break anything relocating the MX partition, then I'd boot back into Windows, disable and remove the recovery partition(s), resize the Windows partition with diskpart, leaving enough space to re-enable a recovery partition, make a new recovery partition, and activate it. I'd also physically disconnect the other drives in the machine before doing any of this so they can't be touched by any of the safety-not-guaranteed repartitioning actions I just outlined.What I'd like to do is to expand the windoze partition and push the MXlinux partition later into the drive, if that makes sense.
But I have no idea how to do that.
Statistics: Posted by DukeComposed — Sat Sep 28, 2024 5:21 pm