Ok, that sounds like a good plan, thanks.
I disabled the swap, but when I try to delete the LV, it says the device is in use even though free seems to indicate otherwise:
Code:
Logical volume OSs/Swap is used by another device.
I tried this suggestion next: https://askubuntu.com/a/109961/491784, but it gives a similar error:
Code:
Device /dev/mapper/OSs-Swap is still in use.
I was also confused by the output of sudo fdisk -l:
Code:
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectorsDisk model: SAMSUNG ************-******
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EB5E32A4-E0CE-49B9-9DBF-066016079B80
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1048575 1046528 511M EFI System
/dev/nvme0n1p3 5769216 500117503 494348288 235.7G Linux LVM
Disk /dev/mapper/OSs-Swap: 12 GiB, 12884901888 bytes, 25165824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/OSs-Pop: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/cryptswap: 12 GiB, 12884377600 bytes, 25164800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I see /dev/mapper/OSs-Swap and also /dev/mapper/cryptswap.
PopOS uses systemd so I think I'll need to do bootctl update instead of update-grub when we can reach that step.
EDIT:
I tried the other suggestion here: https://askubuntu.com/a/109961/491784 and commented out the swap in /etc/fstab and /etc/crypttab and then after rebooting, I was able to remove the volume and both entries are gone from fdisk's output.
I ran sudo update-initramfs -u and bootctl update which gave:
Code:
Skipping "/boot/efi/EFI/systemd/systemd-bootx64.efi", since a newer boot loader version exists already.
Skipping "/boot/efi/EFI/BOOT/BOOTX64.EFI", since a newer boot loader version exists already.
I still was not able to boot with the current kernel, but still can with the old one.
Bookmarks