Changed Swap Disk, but swap.target still trys and fails to load old swap disk

Recently changed my swap disk because i was sick of my swap disk being encrypted and having to type 2 passwords upon boot… removed the luks entry from my systemd-boot entry, but something is still trying to mount the old disk even after removing it from the fstab as well… where might i have to go to clean this up?

Apr 04 18:18:58 EVA-01 systemd[1]: Reached target Block Device Preparation for /dev/mapper/luks-e09a9cf8-7f41-4c28-8904-fd810dd5e1fb.
Apr 04 18:18:58 EVA-01 systemd[1]: dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.device: Job dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.device/start failed with result 'timeout'.
Apr 04 18:18:58 EVA-01 systemd[1]: dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.swap: Job dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.swap/start failed with result 'dependency'.
Apr 04 18:18:58 EVA-01 systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Apr 04 18:18:58 EVA-01 systemd[1]: Dependency failed for Swaps.
Apr 04 18:18:58 EVA-01 systemd[1]: Dependency failed for /dev/disk/by-uuid/058ae665-3b9d-4406-9890-1a9817caab1d.
Apr 04 18:18:58 EVA-01 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/058ae665-3b9d-4406-9890-1a9817caab1d.
Apr 04 18:18:58 EVA-01 systemd[1]: dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.device: Job dev-disk-by\x2duuid-058ae665\x2d3b9d\x2d4406\x2d9890\x2d1a9817caab1d.device/start timed out.
Apr 04 18:18:58 EVA-01 systemd[1]: dev-disk-by\x2duuid-e09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.device: Job dev-disk-by\x2duuid-e09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.device/start failed with result 'timeout'.
Apr 04 18:18:58 EVA-01 systemd[1]: systemd-cryptsetup@luks\x2de09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.service: Job systemd-cryptsetup@luks\x2de09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.service/start failed with result 'dependency'.
Apr 04 18:18:58 EVA-01 systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 04 18:18:58 EVA-01 systemd[1]: Dependency failed for Local Encrypted Volumes.
Apr 04 18:18:58 EVA-01 systemd[1]: Dependency failed for Cryptography Setup for luks-e09a9cf8-7f41-4c28-8904-fd810dd5e1fb.
Apr 04 18:18:58 EVA-01 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/e09a9cf8-7f41-4c28-8904-fd810dd5e1fb.
Apr 04 18:18:58 EVA-01 systemd[1]: dev-disk-by\x2duuid-e09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.device: Job dev-disk-by\x2duuid-e09a9cf8\x2d7f41\x2d4c28\x2d8904\x2dfd810dd5e1fb.device/start timed out.

Did you run sudo dracut-rebuild after making those changes?

nope… running now then gonna reboot to verify.

Well, that made it worse… stuck in emergency mode

Here is what I see before getting kicked to emergency mode…

Seems like my changes to systemd boot parameters didn’t stick… after editing before boot using the e key, I can boot again, but same issue persists.

Those files are generated. You need to make the changes in /etc/kernel/cmdline

Yes, I did that before running the command you mentioned, but it didn’t seem to stick.

You need to run sudo reinstall-kernels after changing /etc/kernel/cmdline

Ok… will run that and try again

System boots, but still stuck on “a start job is running for /dev/disk/by-uuid/” until it times out… the uuids it’s waiting on aren’t even in my fstab so I don’t know where they are getting pulled from

/etc/crypttab?

1 Like

It was in there, removed that entry and am testing again

That also requires either sudo reinstall-kernels or sudo dracut-rebuild to take effect.

Still have another entry it’s getting tripped on that is not in either of those files, is there a 3rd spot that has disk uuids to mount? It’s this one here

```

Apr 04 18:18:58 EVA-01 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/058ae665-3b9d-4406-9890-1a9817caab1d

```

EDIT, it was in fstab, but it was indented differently so i missed it… maybe i got the uuid wrong, where do i find a uuid for a partition to put in fstab cause obviously the way i found it didn’t work

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.