fixed by @skullgiver : it was an entry in /etc/crypttab.

Thanks for all the help everyone. This was an awesome experience.

I don’t know how stupid this was to do but many articles suggested it should be fine.

I resized my mouted root partition. Showed a bunch of warnings on resizing a mounted drive but it worked. Also did a sudo resize2fs /dev/sdaX to complete it.

Went from: winEFI, Win11, EFI, root, swap, data1, data2, win-recovery

To : winEFI, Win11, EFI, root, new-data1, win-recovery

But now every boot takes an additional 60-90 seconds with a blank screen. Pressing ESC shows the above log.

I am unsure of how to fix this or even what caused this. The root partition still starts from the same and only grew to right. Is this because of the deleted swap ?

The operations were performed via GParted but I followed this : https://askubuntu.com/questions/24027/how-can-i-resize-an-ext-root-partition-at-runtime

PS: Pop 22.04 Nvidia. Relatively fresh (~3mo) install but severely miscalculated how much size I needed.

  • tal@kbin.social
    41·
    1 year ago

    But now every boot takes an additional 60-90 seconds with a blank screen.

    Hmm.

    Maybe whatever changes gparted did altered the root partition UUID; after it doesn’t come up, maybe your distro has some sort of fallback to find the partition?

    In /etc/fstab, you may have a line that looks something like this:

    UUID=3aafadcd-1d21-4c82-97f8-f872f341bbe2 /           ext4    errors=remount=ro        0       1

    If you run blkid, you can check and make sure that the UUID matches.

    Or, as someone else mentions, maybe it’s waiting for the deleted swap partition. Should be in the same file. Can comment out the reference to said swap partition.

    EDIT: Wait, I’m being silly. The reference to the root partition that you’re gonna care about is gonna be in the grub config file, not /etc/fstab. On my Debian system, that’s at /boot/grub/grub.cfg.