Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #186634 > unrolled thread

Re: hibernate uses a wrong UUID

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: hibernate uses a wrong UUID Michael Biebl <biebl@debian.org> - 2017-09-09 19:00 +0200
    Re: hibernate uses a wrong UUID Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-09 19:10 +0200
    Re: hibernate uses a wrong UUID Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-09 20:00 +0200
      Re: hibernate uses a wrong UUID Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-09 22:20 +0200
        Re: hibernate uses a wrong UUID Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-10 13:20 +0200
          Re: hibernate uses a wrong UUID "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-10 16:50 +0200
            Re: hibernate uses a wrong UUID Erwan David <erwan@rail.eu.org> - 2017-09-10 17:00 +0200
              Re: hibernate uses a wrong UUID Michael Biebl <biebl@debian.org> - 2017-09-10 17:40 +0200
                Re: hibernate uses a wrong UUID Michael Biebl <biebl@debian.org> - 2017-09-10 17:50 +0200
            Re: hibernate uses a wrong UUID Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-11 10:10 +0200
              Re: hibernate uses a wrong UUID "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-11 11:20 +0200
                Re: hibernate uses a wrong UUID Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-09-11 15:10 +0200

#186634 — Re: hibernate uses a wrong UUID

[Multipart message — attachments visible in raw view] — view raw

Am 09.09.2017 um 18:50 schrieb Pierre Frenkiel:
> I have this in /etc/initramfs-tools/conf.d/resume
>     RESUME=UUID=42b1dc3e-6206-4bd5-9eb4-76e97f94cd65
> which is actually the UUID of the swap partition.
> 
> and after pm-hibernate and reboot, I find in syslog:
>    PM: Checking hibernation image partition
> /dev/disk/by-uuid/2fff8fc5-d304-418f-8d5c-c0ae12b23ac2
> and then, of course, "image not found" (no partition has this UUID)
> 
> Can anybody explain that?

Outdated initramfs?
After modifying /etc/initramfs-tools/conf.d/resume you need to run
update-initramfs


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [next] | [standalone]

#186636

On Sat, 9 Sep 2017, Michael Biebl wrote:

> Outdated initramfs?
> After modifying /etc/initramfs-tools/conf.d/resume you need to run
> update-initramfs
>

   Thank you for the advice.
   I did it once, but may-be it failed. I'll run it again, to be sure.

[toc] | [prev] | [next] | [standalone]

#186638

On Sat, 9 Sep 2017, Michael Biebl wrote:

> Outdated initramfs?
> After modifying /etc/initramfs-tools/conf.d/resume you need to run
> update-initramfs

   I ran it again (update-initramfs -u), and I got the message
   generating .....
   but the problem is still there

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#186642

On 9/9/17, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:
> On Sat, 9 Sep 2017, Michael Biebl wrote:
>
>> Outdated initramfs?
>> After modifying /etc/initramfs-tools/conf.d/resume you need to run
>> update-initramfs
>
>    I ran it again (update-initramfs -u), and I got the message
>    generating .....
>    but the problem is still there


This is my third complete rewrite. There's a CLOSED Bug #861057 (2017.04.26):

TITLE: initramfs-tools: no longer supports RESUME=LABEL|UUID syntax

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861057

That was found because I'm FINALLY trying to address my own hibernate
(suspend?) recovery issues while all of this is almost making sense
today.

Originally, I was writing to ask what's in Pierre's
/etc/initramfs-tools/conf.d/resume file.

My purpose for asking about Pierre's *was* that maybe there's
something too much (like a stray, *invisible* character) or maybe
something too little (like a missing closing character) that's
interfering with success.

BUT... now there's that closed bug #861057 which sounds possibly
similar to Pierre's experience. That pretty much shoves my idea out
the back door. :)

Pierre's bug, he shared that extra bit about how it's checking for a
wrong UUID. It's possible I'm not cognitively grasping that the same
is mentioned in Bug #861057, but right now I'm not seeing that
referenced there. Maybe that was what was going on under the hood on
that closed bug, too..........

Back on that "maybe something too little" character angle... Would
single quotes or double quotes around the UUID value help in this
case?

Everything else I wrote has been deleted while I work on my own issue.
In the meantime, I found these while trying to fix mine:

https://wiki.debian.org/Hibernation
https://wiki.debian.org/Suspend
https://wiki.debian.org/SystemdSuspendSedation

I figured:

* Those look like they could use a refresh from a knowledgeable person...
* I'm surely not the only one who keeps mixing these terms up.. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#186655

On Sat, 9 Sep 2017, Cindy-Sue Causey wrote:

> Pierre's bug, he shared that extra bit about how it's checking for a
> wrong UUID. It's possible I'm not cognitively grasping that the same
> is mentioned in Bug #861057, but right now I'm not seeing that
> referenced there. Maybe that was what was going on under the hood on
> that closed bug, too..........

   I recently increased my swap partition size, and the wrong UUID
   was that of the old swap, and was set in the resume option of grub.cfg.
   After updating grub, this problem disappears, but anyway, the hibernate stuff in Debian
   seems really crazy:
   I found 3 different places where the resume can be defined
       /etc/uswsusp.conf
       /boot/grub.cfg
       /etc/initramfs-tools/conf.d/resume
   I tried all 3 together, with the following result

Sep 10 12:20:08 pfr3 kernel: [    1.186027] PM: Checking hibernation image partition /dev/disk/by-uuid/42b1dc3e-6206-4bd5-9eb4-76e97f94cd65
Sep 10 12:20:08 pfr3 kernel: [    1.201123] PM: Hibernation image not present or could not be loaded.
Sep 10 12:20:08 pfr3 kernel: [    2.728912] PM: Hibernation image partition 8:4 present
Sep 10 12:20:08 pfr3 kernel: [    2.728914] PM: Looking for hibernation image.
Sep 10 12:20:08 pfr3 kernel: [    2.729062] PM: Image not found (code -22)
Sep 10 12:20:08 pfr3 kernel: [    2.729064] PM: Hibernation image not present or could not be loaded.

who can explain that?
It seems that the image was not written on disk when issuing the hibernate-disk command, but why ?

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#186658

You should not use "uswsusp" anymore on recent OS releases. Hibernate
should work "out-of-the-box" assuming swap partition is big enough.
Remove "uswsusp", double check "/etc/fstab" swap entry

    $ sudo blkid | grep swap
    /dev/sdb2: LABEL="swap" UUID="d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8"
TYPE="swap" PARTUUID="88839920-fc62-4f3a-aa7c-e97cd1ed4d5d"

    $ cat /etc/fstab | grep swap
    UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8    none    swap    sw   
0    0

and "/etc/initramfs-tools/conf.d/resume"

    $ cat /etc/initramfs-tools/conf.d/resume
    RESUME=UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8

Check swap is working via "swapon"
After that either reinstall initramfs-tools via

    $ sudo apt-get install --reinstall initramfs-tools

or update initramfs via
   
    $ sudo update-initramfs -u -v | grep "Adding config"

This way you can see all config files and check them if swap
partition\hibernation image is still not found.
Reboot and try to hibernate.


On 10.09.2017 16:13, Pierre Frenkiel wrote:
> On Sat, 9 Sep 2017, Cindy-Sue Causey wrote:
>
>> Pierre's bug, he shared that extra bit about how it's checking for a
>> wrong UUID. It's possible I'm not cognitively grasping that the same
>> is mentioned in Bug #861057, but right now I'm not seeing that
>> referenced there. Maybe that was what was going on under the hood on
>> that closed bug, too..........
>
>   I recently increased my swap partition size, and the wrong UUID
>   was that of the old swap, and was set in the resume option of grub.cfg.
>   After updating grub, this problem disappears, but anyway, the
> hibernate stuff in Debian
>   seems really crazy:
>   I found 3 different places where the resume can be defined
>       /etc/uswsusp.conf
>       /boot/grub.cfg
>       /etc/initramfs-tools/conf.d/resume
>   I tried all 3 together, with the following result
>
> Sep 10 12:20:08 pfr3 kernel: [    1.186027] PM: Checking hibernation
> image partition /dev/disk/by-uuid/42b1dc3e-6206-4bd5-9eb4-76e97f94cd65
> Sep 10 12:20:08 pfr3 kernel: [    1.201123] PM: Hibernation image not
> present or could not be loaded.
> Sep 10 12:20:08 pfr3 kernel: [    2.728912] PM: Hibernation image
> partition 8:4 present
> Sep 10 12:20:08 pfr3 kernel: [    2.728914] PM: Looking for
> hibernation image.
> Sep 10 12:20:08 pfr3 kernel: [    2.729062] PM: Image not found (code
> -22)
> Sep 10 12:20:08 pfr3 kernel: [    2.729064] PM: Hibernation image not
> present or could not be loaded.
>
> who can explain that?
> It seems that the image was not written on disk when issuing the
> hibernate-disk command, but why ?
>
> best regards,

[toc] | [prev] | [next] | [standalone]

#186659

Le 09/10/17 à 16:47, Alexander V. Makartsev a écrit :
> You should not use "uswsusp" anymore on recent OS releases. Hibernate
> should work "out-of-the-box" assuming swap partition is big enough.
> Remove "uswsusp", double check "/etc/fstab" swap entry
> 
"Should" is not an answer when it does not work anymore. Eg you add RAM
and make a bigger swap partition -> stops working, what to do, where to
chheck ?
"should work" is black magic and does not help.

[toc] | [prev] | [next] | [standalone]

#186660

[Multipart message — attachments visible in raw view] — view raw

Am 10.09.2017 um 16:51 schrieb Erwan David:
> Le 09/10/17 à 16:47, Alexander V. Makartsev a écrit :
>> You should not use "uswsusp" anymore on recent OS releases. Hibernate
>> should work "out-of-the-box" assuming swap partition is big enough.
>> Remove "uswsusp", double check "/etc/fstab" swap entry
>>
> "Should" is not an answer when it does not work anymore. Eg you add RAM
> and make a bigger swap partition -> stops working, what to do, where to
> chheck ?

If you "make the swap partition bigger", you most likely changed the
UUID. That's exactly what Alexander described you need to check and
update if necessary.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [next] | [standalone]

#186661

[Multipart message — attachments visible in raw view] — view raw

Am 10.09.2017 um 17:36 schrieb Michael Biebl:
> If you "make the swap partition bigger", you most likely changed the
> UUID. That's exactly what Alexander described you need to check and
> update if necessary.


Running "mkswap" on an existing swap partition will change its UUID.
(unless you specify the old one via the --uuid switch)

What often happens is that users install another distro onto another
partition. The installer usually runs mkswap on existing swap partitions
which breaks existing installations.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[toc] | [prev] | [next] | [standalone]

#186671

On Sun, 10 Sep 2017, Alexander V. Makartsev wrote:

> You should not use "uswsusp" anymore on recent OS releases. Hibernate
> should work "out-of-the-box" assuming swap partition is big enough.
> Remove "uswsusp", double check "/etc/fstab" swap entry
>
>    $ sudo blkid | grep swap
>    /dev/sdb2: LABEL="swap" UUID="d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8"
> TYPE="swap" PARTUUID="88839920-fc62-4f3a-aa7c-e97cd1ed4d5d"
>
>    $ cat /etc/fstab | grep swap
>    UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8    none    swap    sw
> 0    0
>
> and "/etc/initramfs-tools/conf.d/resume"
>
>    $ cat /etc/initramfs-tools/conf.d/resume
>    RESUME=UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8
>
> Check swap is working via "swapon"
> After that either reinstall initramfs-tools via
>
>    $ sudo apt-get install --reinstall initramfs-tools
>
> or update initramfs via
>
>    $ sudo update-initramfs -u -v | grep "Adding config"
>
> This way you can see all config files and check them if swap
> partition\hibernation image is still not found.
> Reboot and try to hibernate.
>
  I already did all that stuff, and increased my swap partition to twice the
  ram size...

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [next] | [standalone]

#186673

Well, in that case, you should start to provide output from "all that
stuff" I mentioned.


On 11.09.2017 13:08, Pierre Frenkiel wrote:
> On Sun, 10 Sep 2017, Alexander V. Makartsev wrote:
>
>> You should not use "uswsusp" anymore on recent OS releases. Hibernate
>> should work "out-of-the-box" assuming swap partition is big enough.
>> Remove "uswsusp", double check "/etc/fstab" swap entry
>>
>>    $ sudo blkid | grep swap
>>    /dev/sdb2: LABEL="swap" UUID="d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8"
>> TYPE="swap" PARTUUID="88839920-fc62-4f3a-aa7c-e97cd1ed4d5d"
>>
>>    $ cat /etc/fstab | grep swap
>>    UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8    none    swap    sw
>> 0    0
>>
>> and "/etc/initramfs-tools/conf.d/resume"
>>
>>    $ cat /etc/initramfs-tools/conf.d/resume
>>    RESUME=UUID=d0331ef1-bc12-473f-bd4a-b4edf0d4d0a8
>>
>> Check swap is working via "swapon"
>> After that either reinstall initramfs-tools via
>>
>>    $ sudo apt-get install --reinstall initramfs-tools
>>
>> or update initramfs via
>>
>>    $ sudo update-initramfs -u -v | grep "Adding config"
>>
>> This way you can see all config files and check them if swap
>> partition\hibernation image is still not found.
>> Reboot and try to hibernate.
>>
>  I already did all that stuff, and increased my swap partition to
> twice the
>  ram size...
>
> best regards,

[toc] | [prev] | [next] | [standalone]

#186676

On Mon, 11 Sep 2017, Alexander V. Makartsev wrote:

> Well, in that case, you should start to provide output from "all that
> stuff" I mentioned.

   Hi Alexander,
   the output was the same as yours, with just my UUID instead of yours.
   Anyway, I found a simple way to avoid wasting time with hibernate:

   - for short term, only use suspend at lid close (I have to check now
     what is the battery life)
   - for long term, shutdown/reboot !! It's just a few seconds more
     than the not working hibernate.

     thank you for your help

best regards,
-- 
Pierre Frenkiel

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web