Hey, I'm also affected by this bug. By now, just workarounding it booting with "noresume".
But, I'm wondering why /usr/share/initramfs-tools/hooks/resume uses blkid to translate a configuration variable set by the user (e.g. /dev/mapper/vg0-swap) to a UUID=... form. Couldn't just let the RESUME variable be what the user set in the first place? Another question, how would lvchange handle UUIDs? I've skimmed the manpage and there is absolutely no reference on how activate a LV using its UUID. Thanks everyone, -- L. Alberto Giménez JabberID [email protected] GnuPG key ID 0x3BAABDE1 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
