On Sun, Jan 07, 2007 at 08:03:07PM +0100, Marcus Better wrote:
Also, as a workaround, try specifying hash=ripemd160 in the relevant
entry in the /etc/crypttab file and regenerate the initramfs image.
It still doesn't work, but it's closer. It seems to attemt a resume this time.
But then this happens:
kinit: trying to resume from /dev/mapper/swap
...
kinit: no resume image, doing normal boot
And it does a normal boot. Afterwards I have a /dev/mapper/swap node, but I
cannot "swapon" it:
~# swapon /dev/mapper/swap
swapon: /dev/mapper/swap: Invalid argument
Try running fstype on the /dev/mapper/swap device and see what it
reports, just to make sure that it is indeed recognized as a suspend
device. In a running system it's available as /usr/lib/klibc/bin/fstype
If it is, then it is not weird that you can't "swapon" the device since
the suspend signature still is there (and it has overwritten the swap
signature, if the resume had succeeded, the swap signature would have
been written back ontop of the suspend signature).
--
David Härdeman
