Re: hibernation fails

[Stefan Monnier <monnier@iro.umontreal.ca>]

> Originally everything was on HD, and hibernation worked flawlessly. Then
> I converted it to a hybrid system (/, /boot, /usr, /home, swap on SSD; other
> filesystems on HD), and hibernation would not even pretend to start unless
> I enabled swap on the HD.   Now it's all SSD, and since the conversion
> hibernation fails.  It will appear to hibernate (suspend to disk) and power
> off, but then boot normally.  Here's the suspension from last night from the
> journal:

My crystal ball tells me that the indication about which partition holds
the hibernated data (usually your swap partition) is the culprit.

This info is copied into the `/boot/initrd.img-<VERS>` file (so that
during the boot Linux can check the partition to see if it holds
hibernation data, in which case it proceeds to resume from it), so you
need to make sure this is rebuilt when the swap partition is changed.

There's also the issue of how this partition is guessed when rebuilding
the initrd.  I think you can specify it explicitly with
a RESUME=/dev/... in /etc/initramfs-tools/initramfs.conf, but normally
it's auto-guessed as "the sap partition" (assuming you have one and only
one).

IOW, I'd try

    update-initramfs -u

and check what it says.  For me, if I don't specify
RESUME=... explicitly in the conf file it says:

    # update-initramfs -u
    update-initramfs: Generating /boot/initrd.img-6.16.3+deb14-amd64
    I: The initramfs will attempt to resume from /dev/dm-1
    I: (/dev/mapper/VG1-swap)
    I: Set the RESUME variable to override this.
    #

where `/dev/mapper/VG1-swap` is indeed the appropriate device, so it
guessed correctly.


        Stefan