Hello everybody! here’s the problem: In my EndeavourOS laptop I had a /swapfile, but couldn’t take snapshots with snapper because of it (if I understood correctly). So, I created a 16Gb swap partition using GParted from a live USB. Then, I edited /etc/fstab to remove the line about the swapfile and to add the newly created swap partition:

UUID=506d48e6-1cc0-4136-ba55-6f2f187bcdb1   swap           swap    defaults   0 0
# /swapfile                                   none           swap    sw         0 0

I took the UUID from

$ sudo blkid  
/dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
...

if I run sudo swapon -a it gets enabled correctly and it all works fine. The problem however is that when I reboot the machine, it gets stuck in the systemd screen saying “a job is running for /dev/disk/etc…” forever, and the only way I have to log in is to boot from a live USB, modify /efi/loader/entries/somethingverylong.conf to add these kernel options:

systemd.swap=0 noresume

and then reboot, and manually enable the swap.

I’m not understanding very well what’s happening here. why is the system stuck if I don’t add these parameters? how can I solve it?

thanks in advance!

    • tubbadu@lemmy.kde.socialOP
      0·
      9 days ago
      A start job is running for /dev/disk/by-uuid/8c53812d-ba43-45e4-b219-8d3ded8548a5

      it’s really strange, I just noticed that it’s the UUID of… the original swap partition (now gone) the entry is still commented in /etc/fstab:

      # UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5 swap             swap    defaults   0 0

      is there another place other than /etc/fstab where I should remove it?

      thanks for the help!

      EDIT: this is the whole output of sudo blkid if needed:

      /dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
/dev/nvme0n1p1: UUID="467B-65A4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="53413c1b-04f0-42cf-bd71-15e2796f002a"
/dev/nvme0n1p2: LABEL="endeavouros" UUID="cf0a3420-51e0-40ba-8b86-ae2cc576e5c1" UUID_SUB="faa47171-fc00-4435-8c8f-0b346682071d" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="endeavouros" PARTUUID="dc12b835-18f9-4937-8a58-07b2600012e9"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="d076884c-6236-4e0a-be36-47df3e28d7a3"
/dev/sda3: LABEL="STORAGE" UUID="6EFB-D6EF" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="381ea0c9-7fdd-4a74-a92e-5b450f2001db"
/dev/sda1: LABEL="WINZOZZ" BLOCK_SIZE="512" UUID="7FC0A0D067B4D0F8" TYPE="ntfs" PARTUUID="e4d431c8-06e8-4fac-93e9-342026cc4ff1"
      • eldavi@lemmy.mlEnglish
        0·
        9 days ago

        it sounds like it unrelated to /etc/fstab and that there’s something in your systemd config that’s expecting it.

        if you don’t have the name of the unit; i think you search through your systemd config in /etc/ to find & disable it. (ie grep -ir $uuid /etc/)

        • tubbadu@lemmy.kde.socialOP
          0·
          9 days ago

          THANK YOU! The grep command you posted showed me that that UUID was still present in /etc/kernel/cmdline as

          resume=UUID=8c53812d-ba43-45e4-b219-8d3ded8548a5

          I changed it with the new one and run sudo reinstall-kernels, and now it works correctly! thank you very much for your help!