Thanx,
Prevention has to be made before boot and with no prior configuration before hibernation. If I know in advance I just shut down instead and things are safe.
The scenario is that I have a laptop running linux, I put it in to hibernation as usual with no plans to remove the disks. Later the disk is anyway removed and mounted from another Linux where changes are made. The hibernated information is now out of date. When I later insert the disk and boots on it I must make sure that it never restores the hibernation image - it is no longer valid.
In my case I have a swap partion.
@CwF are right, clearing the swap will work.
Clearing the swap can be done by booting on a USB and regenerate the swap partition using mkswap. There are some implications though. UUID references is the common practise today and UUID will change when swap is regenerated so I need to enter the environment and fix fstab and possibly some other settings (e.g. /etc/default/grub) . This is not a very handy operation in general, however it can easily be done when I anyhow have the disk mounted from another linux.
What I still wish for is a option that is considered by kernel or systemd to just ignore any existing hibernation images so the question remains open.
Prevention has to be made before boot and with no prior configuration before hibernation. If I know in advance I just shut down instead and things are safe.
The scenario is that I have a laptop running linux, I put it in to hibernation as usual with no plans to remove the disks. Later the disk is anyway removed and mounted from another Linux where changes are made. The hibernated information is now out of date. When I later insert the disk and boots on it I must make sure that it never restores the hibernation image - it is no longer valid.
In my case I have a swap partion.
@CwF are right, clearing the swap will work.
Clearing the swap can be done by booting on a USB and regenerate the swap partition using mkswap. There are some implications though. UUID references is the common practise today and UUID will change when swap is regenerated so I need to enter the environment and fix fstab and possibly some other settings (e.g. /etc/default/grub) . This is not a very handy operation in general, however it can easily be done when I anyhow have the disk mounted from another linux.
What I still wish for is a option that is considered by kernel or systemd to just ignore any existing hibernation images so the question remains open.
Statistics: Posted by Paddlaren — 2024-01-30 07:38