Linux не выходит из спящего режима с зашифрованным разделом подкачки ⇐ Linux
Linux не выходит из спящего режима с зашифрованным разделом подкачки
I have a LUKS setup with an encrypted swap partition. I have no intention to use the hibernation / suspend-to-disk feature so I set up the encrypted swap partition without such support. Reference documentation.
My understanding is that the encrypted swap partition is encrypted with a random key which is overwritten on every boot, so resuming from hibernation is impossible in this setup.
A few days ago I accidentally used systemctl hibernate command to put the system into hibernation. When I try to resume from hibernation, there is a 120s timer before a timeout happens and the resume process fails. The system just boots into a fresh start.
The error in systemd journal:
dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device: Job dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device/start timed out. Timed out waiting for device /dev/disk/by-uuid/4e9d677c-42d1-4072-91d6-456a25d34d52. Dependency failed for Resume from hibernation. systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'. dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device: Job dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device/start failed with result 'timeout'. I try to reboot multiple times, but each time there is always a 120s timeout followed by the error that the device timed out. The device with that UUID 4e9d677c-... does not actually exist as it is the the UUID belongs to the transient encrypted swap partition.
I assume that the suspend flag is set somewhere so the system always tries to resume when booting but the process failed due to some other reasons.
Is there a way to clear / reset the suspend flag, so that it directly boots freshly without trying to resuming (and failing)?
Источник: https://stackoverflow.com/questions/781 ... -partition
I have a LUKS setup with an encrypted swap partition. I have no intention to use the hibernation / suspend-to-disk feature so I set up the encrypted swap partition without such support. Reference documentation.
My understanding is that the encrypted swap partition is encrypted with a random key which is overwritten on every boot, so resuming from hibernation is impossible in this setup.
A few days ago I accidentally used systemctl hibernate command to put the system into hibernation. When I try to resume from hibernation, there is a 120s timer before a timeout happens and the resume process fails. The system just boots into a fresh start.
The error in systemd journal:
dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device: Job dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device/start timed out. Timed out waiting for device /dev/disk/by-uuid/4e9d677c-42d1-4072-91d6-456a25d34d52. Dependency failed for Resume from hibernation. systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'. dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device: Job dev-disk-by\x2duuid-4e9d677c\x2d42d1\x2d4072\x2d91d6\x2d456a25d34d52.device/start failed with result 'timeout'. I try to reboot multiple times, but each time there is always a 120s timeout followed by the error that the device timed out. The device with that UUID 4e9d677c-... does not actually exist as it is the the UUID belongs to the transient encrypted swap partition.
I assume that the suspend flag is set somewhere so the system always tries to resume when booting but the process failed due to some other reasons.
Is there a way to clear / reset the suspend flag, so that it directly boots freshly without trying to resuming (and failing)?
Источник: https://stackoverflow.com/questions/781 ... -partition
-
- Похожие темы
- Ответы
- Просмотры
- Последнее сообщение
-
-
Вход в систему Использование спящего режима для получения имени пользователя и пароля
Anonymous » » в форуме JAVA - 0 Ответы
- 35 Просмотры
-
Последнее сообщение Anonymous
-