Bug#412210: [Pkg-cryptsetup-devel] Bug#412210: cryptsetup: fails to handle suspend filesystem in swap

Leonard Norrgård vinsci at refactor.fi
Wed Feb 28 21:43:18 CET 2007


> Could you provide me with the contents of /conf/conf.d/cryptroot from the
> initramfs image?

conf/conf.d/cryptroot:
target=VG00-root_crypt,source=/dev/mapper/VG00-root,key=none
target=VG00-swap_crypt,source=/dev/mapper/VG00-swap,key=none

> Also, what behaviour do you get when you boot after the suspend? Does it
> try to setup the swap partition but fails? Does it print error messages?
> Is the swap partition silently ignored?

Here is a manually copied selection of relevant messages on the screen:

[...]
| Setting up cryptographic volume VG00-swap_crypt (based on /dev/mapper/VG00-swap)
| Enter LUKS passphrase:
| key slot 0 unlocked.
| Command successful.
| cryptsetup: unknown fstype, bad password or options?
| Enter LUKS passphrase:

(repeats, I then intentionally gave the wrong passphrase a couple of times)

| Enter LUKS passphrase:
| Command failed.
| cryptsetup: cryptsetup failed, bad password or options?
| cryptsetup: maximum number of tries exceeded
| resume: libgcrypt version: 1.2.3
| resume: Could not stat the resume device file.
|         Please type in the file name to try again     or press ENTER to boot the system:

(I suppose I did hit enter)

| INIT: version 2.06 booting
[...]
| Starting early crypto disks... VG00-home_crypt(starting)
| Enter LUKS passphrase:
| key slot 0 unlocked.
| Command successful.
|  VG00-root(running) VG00-swap_crypt(starting)
| Enter LUKS passphrase:

(intentionally typed wrong phrase to get ahead)

| Command failed.
| done.
| Setting up LVM Volume Groups...
[...]
| Starting remaining crypto disks...VG00-home_crypt(running) VG00-root_crypt(running) VG00-swap_crypt(starting)
| Enter LUKS passphrase:
| key slot 0 unlocked.
| Command successful.
|  - The device /dev/mapper/VG00-swap_crypt contains a valid filesystem of type suspend.
| the check for '/dev/mapper/VG00-swap_crypt' failed. /dev/mapper/VG00-swap_crypt contains data.
| removing the crypto device VG00-swap_crypt
|  VG00-var_crypt(starting)
[...]

The swap remains inactive.

Sorry for omitting the above messages in the original report.

> What arguments do you use when booting? (cat /proc/cmdline)

root=/dev/mapper/VG00-root_crypt ro vga=791 quiet

-- Leonard




More information about the Pkg-cryptsetup-devel mailing list