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.

  • Skull giver@popplesburger.hilciferous.nl
    2·
    1 year ago

    The error log you posted shows a corrupted disk getting repaired. If you see it every time, you probably need a good offline fsck.

    The hang is probably the missing swap partition. Remove it from /etc/fstab and possible the resume= parameter in your bootloader. The resume parameter tells the system to try to resume a hibernated system from a specific partition, and it may get stuck searching for that.

    • nestEggParrot@lemmy.sdf.orgOP
      2·
      1 year ago

      Tried checking for systemd-boot config file to look for resume=.

      This is the most relevant config file I found and didn’t find resume on it. Am I looking at the right place ?

      ❯ sudo cat /boot/efi/loader/entries/Pop_OS-current.conf 
title Pop!_OS
linux /EFI/Pop_OS-f5a850fb-0b54-49f7-b84c-09d05b7d910e/vmlinuz.efi
initrd /EFI/Pop_OS-f5a850fb-0b54-49f7-b84c-09d05b7d910e/initrd.img
options root=UUID=f5a850fb-0b54-49f7-b84c-09d05b7d910e ro quiet loglevel=0 systemd.show_status=false splash

      And yes the disk repair was only one off. Didn’t get it subsequent boots.

      • Skull giver@popplesburger.hilciferous.nl
        2·
        1 year ago

        That would be the right place where you would find the resume parameter, yes. Looks like it’s not hibernation after all!

        Something else that may cause the issue: you say you’ve edited fstab, but you may also need to run sudo update-initramfs -u -k all to make the change propagate through the early boot process. That command will run for a while but I think that might fix the issue.

          • Skull giver@popplesburger.hilciferous.nl
            5·
            1 year ago

            Last thing I can think of crypttab. You seem to have encrypted your swap, so you may have an entry in /etc/crypttab that’s causing this issue. Remove it from there and update the initramfs again.

            If that’s not the problem either, I would just run sudo grep -r c0a6e61d /etc and see what files still reference the partition.

            • nestEggParrot@lemmy.sdf.orgOP
              6·
              1 year ago

              This fixed it. Commented the crypttab entry and no more wait on boot. Thanks for your time and the clear instructions to follow. Much appreciated.

  • regalia@literature.cafe
    2·
    1 year ago

    The issue here is that you’re clearly running an orphanage here and keep killing off the children (processes)

  • BaroqueInMind@kbin.social
    12·
    1 year ago

    PopOS

    There’s your problem. The solution here is to rather remind literally every single human that is capable of sapient thought that you run Arch, then install Arch. The more people you inform that you use Arch, the more stable the OS becomes. /s

    Edit: yes, also I am running Arch.