You are not logged in.
Pages: 1
In my vanity I tried some tool where I was in one case required to deactivate my swap file, being under the impression that it would be reactivated next time I would reboot. Well it didn't...
Boot times now take considerably longer.
Output of journalctl -b:
Mai 29 01:01:03 arch systemd[1]: dev-disk-by\x2duuid-0b009dfd\x2d3b1d\x2d42f3\x2d9df5\x2de36b98a01156.device: Job dev-disk-by\x2duuid-0b009dfd\x2d3b1d\x2d42f3\x2d9df5\x2de>
Mai 29 01:01:03 arch systemd[1]: Timed out waiting for device /dev/disk/by-uuid/0b009dfd-3b1d-42f3-9df5-e36b98a01156.
Mai 29 01:01:03 arch systemd[1]: Dependency failed for /dev/disk/by-uuid/0b009dfd-3b1d-42f3-9df5-e36b98a01156.
Mai 29 01:01:03 arch systemd[1]: Dependency failed for Swaps.When I tried "sudo swapon /dev/vg1/swap" I got an error that the Swap-Header could not be read.
Im using LVM on LUKS and have a 16GB swap partition. How do I reactivate the thing? Thx for any hints on where to look
Last edited by Der Chefkoch (2022-05-29 13:51:23)
Offline
Try preparing the file again prior to swapon
#mkswap /dev/vg1/swapTry preparing the file again prior to swapon
#mkswap /dev/vg1/swap
And thats how easy it goes, these things always make me nervous that it wont boot anymore. This did the trick, including using the -U option and renaming it to the same uuid it had before (as crypttab uses it).
Thanks for that.
Offline
Pages: 1