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

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

An answer to "Gave up waiting for suspend/resume device"

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

  An answer to "Gave up waiting for suspend/resume device" Mark Luxton <truthseeker9@yahoo.ca> - 2017-09-23 06:50 +0200
    Re: An answer to "Gave up waiting for suspend/resume device" Jimmy Johnson <field.engineer@gmail.com> - 2017-09-26 04:00 +0200
      Re: An answer to "Gave up waiting for suspend/resume device" Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-26 11:30 +0200
        Re: An answer to "Gave up waiting for suspend/resume device" Jimmy Johnson <field.engineer@gmail.com> - 2017-09-27 10:40 +0200
          Re: An answer to "Gave up waiting for suspend/resume device" Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-27 11:40 +0200
            Re: An answer to "Gave up waiting for suspend/resume device" Jimmy Johnson <field.engineer@gmail.com> - 2017-09-28 09:50 +0200
              Re: An answer to "Gave up waiting for suspend/resume device" Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-28 10:30 +0200
                Re: An answer to "Gave up waiting for suspend/resume device" David Wright <deblis@lionunicorn.co.uk> - 2017-09-28 21:10 +0200
    Re: An answer to "Gave up waiting for suspend/resume device" Larry Dighera <LDighera@att.net> - 2017-09-29 18:40 +0200
      Re: An answer to "Gave up waiting for suspend/resume device" Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-29 19:50 +0200

#187108 — An answer to "Gave up waiting for suspend/resume device"

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

RE:Re: Gave up waiting for suspend/resume device

  
|  
|   |  
Re: Gave up waiting for suspend/resume device
   |  |

  |

 

Try:Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct UUID's in /etc/fstab. Also can use lsblk -f to find the UUID's.

Put the correct UUID's into /etc/fstab, especially swap, for this error.

Put the correct UUID for swap into /etc/initramfs-tools/conf.d/resume.

Run sudo update-initramfs -u

Reboot. Fixed my triple boot of Stretch all with this error, as the swap file had changed.
Truly, Mark Luxton

[toc] | [next] | [standalone]

#187218

On 09/22/2017 09:42 PM, Mark Luxton wrote:
> RE:Re: Gave up waiting for suspend/resume device
> 
>    
> |
> |   |
> Re: Gave up waiting for suspend/resume device
>     |  |
> 
>    |
> 
>   
> 
> Try:Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct UUID's in /etc/fstab. Also can use lsblk -f to find the UUID's.
> 
> Put the correct UUID's into /etc/fstab, especially swap, for this error.
> 
> Put the correct UUID for swap into /etc/initramfs-tools/conf.d/resume.
> 
> Run sudo update-initramfs -u
> 
> Reboot. Fixed my triple boot of Stretch all with this error, as the swap file had changed.
> Truly, Mark Luxton
Hi Mark, while multi-booting I use the device name in fstab,
/dev/sd?? none swap sw 0 0, it works for all my installed systems.
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 - Intel i7-3540M - EXT4 at sda6
Registered Linux User #380263

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

#187228

Le 26/09/2017 à 03:55, Jimmy Johnson a écrit :
> Hi Mark, while multi-booting I use the device name in fstab,
> /dev/sd?? none swap sw 0 0, it works for all my installed systems.

It is not always reliable with multiple drives, because device names are 
not stable across reboots. So it is advised to use persistent 
identifiers such as UUID or LABEL instead.

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

#187296

On 09/26/2017 02:25 AM, Pascal Hambourg wrote:
> Le 26/09/2017 à 03:55, Jimmy Johnson a écrit :
>> Hi Mark, while multi-booting I use the device name in fstab,
>> /dev/sd?? none swap sw 0 0, it works for all my installed systems.
> 
> It is not always reliable with multiple drives, because device names are 
> not stable across reboots. So it is advised to use persistent 
> identifiers such as UUID or LABEL instead.


Yes, what you say is true, but not very often and from what I've seen is 
due to mainboard setup or defects in the mainboard causing the bad setup 
due to mainboard SATA connection being mislabeled.  But if everything is 
correct and you are using lets say sda1 as root in your fstab your 
system will use sda1 as the LABEL, I've seen this over and over.

But all this is advanced setup for people running more than one Linux 
system and having to edit UUID on all systems because you install a new 
system is undesirable.
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

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

#187299

Le 27/09/2017 à 10:37, Jimmy Johnson a écrit :
> On 09/26/2017 02:25 AM, Pascal Hambourg wrote:
>> Le 26/09/2017 à 03:55, Jimmy Johnson a écrit :
>>> Hi Mark, while multi-booting I use the device name in fstab,
>>> /dev/sd?? none swap sw 0 0, it works for all my installed systems.
>>
>> It is not always reliable with multiple drives, because device names 
>> are not stable across reboots. So it is advised to use persistent 
>> identifiers such as UUID or LABEL instead.
> 
> Yes, what you say is true, but not very often and from what I've seen is 
> due to mainboard setup or defects in the mainboard causing the bad setup 
> due to mainboard SATA connection being mislabeled.

No, it is due to the asynchronous nature of device probing and module 
loading by the kernel and udev in modern Linux systems.

>  But if everything is 
> correct and you are using lets say sda1 as root in your fstab your 
> system will use sda1 as the LABEL, I've seen this over and over.

Nonsense. sda1 is the block device name and does not have anything to do 
with the LABEL which is a filesystem metadata field.

> But all this is advanced setup for people running more than one Linux 
> system and having to edit UUID on all systems because you install a new 
> system is undesirable.

No it does not have anything to do with multiple Linux systems.

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

#187345

On 09/27/2017 02:38 AM, Pascal Hambourg wrote:
> Le 27/09/2017 à 10:37, Jimmy Johnson a écrit :
>> On 09/26/2017 02:25 AM, Pascal Hambourg wrote:
>>> Le 26/09/2017 à 03:55, Jimmy Johnson a écrit :
>>>> Hi Mark, while multi-booting I use the device name in fstab,
>>>> /dev/sd?? none swap sw 0 0, it works for all my installed systems.
>>>
>>> It is not always reliable with multiple drives, because device names 
>>> are not stable across reboots. So it is advised to use persistent 
>>> identifiers such as UUID or LABEL instead.
>>
>> Yes, what you say is true, but not very often and from what I've seen 
>> is due to mainboard setup or defects in the mainboard causing the bad 
>> setup due to mainboard SATA connection being mislabeled.
> 
> No, it is due to the asynchronous nature of device probing and module 
> loading by the kernel and udev in modern Linux systems.

Could be but I've only seen that problem on two computers out of easily 
more than 1000 and one of those was a mislabeled main board under 
warranty and the computer was replaced with another model and the other 
computer has taken out of service.

>>   But if everything is correct and you are using lets say sda1 as root 
>> in your fstab your system will use sda1 as the LABEL, I've seen this 
>> over and over.
> 
> Nonsense. sda1 is the block device name and does not have anything to do 
> with the LABEL which is a filesystem metadata field.
> 
>> But all this is advanced setup for people running more than one Linux 
>> system and having to edit UUID on all systems because you install a 
>> new system is undesirable.
> 
> No it does not have anything to do with multiple Linux systems.

In fstab a label is used as a device name, a uuid is used as a device 
name and /dev/sda1 is a device name, you are just trying to make 
nonsense out of nothing.

And editing multiple fstab config files because I've installed a new 
system is, like I said undesirable and why I use device names in both my 
fstab and grub boot menu.  As you know when a new system is installed 
swap is formatted and it's uuid gets changed every time it's formatted.

I do use labels on external plug and play drives though.
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

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

#187347

Le 28/09/2017 à 09:39, Jimmy Johnson a écrit :
> On 09/27/2017 02:38 AM, Pascal Hambourg wrote:
>> Le 27/09/2017 à 10:37, Jimmy Johnson a écrit :
> 
>>>   But if everything is correct and you are using lets say sda1 as 
>>> root in your fstab your system will use sda1 as the LABEL, I've seen 
>>> this over and over.
>>
>> Nonsense. sda1 is the block device name and does not have anything to 
>> do with the LABEL which is a filesystem metadata field.
>>
>>> But all this is advanced setup for people running more than one Linux 
>>> system and having to edit UUID on all systems because you install a 
>>> new system is undesirable.
>>
>> No it does not have anything to do with multiple Linux systems.
> 
> In fstab a label is used as a device name, a uuid is used as a device 
> name and /dev/sda1 is a device name, you are just trying to make 
> nonsense out of nothing.

A label or a UUID are not really used as device names, they are used 
*instead* of a device name.

Anyway, this is not the same as what you wrote earlier and is pure 
nonsense :

"your system will use sda1 as the LABEL"

Unless you meant "define 'sda1' as the filesystem/swap label and use 
LABEL='sda1' in /etc/fstab", which is a really bad use of labels leading 
to confusion between labels and device names. Labels are meant to be 
explicit about the contents, not the container.

> And editing multiple fstab config files because I've installed a new 
> system is, like I said undesirable and why I use device names in both my 
> fstab and grub boot menu.  As you know when a new system is installed 
> swap is formatted and it's uuid gets changed every time it's formatted.

The Debian installer does this, but I am not sure that all other distro 
installers do the same. Moreover, the Debian installer will format an 
existing swap only if that swap is marked for use (the trick is that all 
existing swaps are automatically marked for use by default, so you have 
to pay attention and unmark them if you do not want them to be 
formatted). IMO this is a real bug in the installer.

So my general policy when installing Debian is to mark any existing swap 
as "not used", and if I want to share an existing swap, I add the line 
manually in /etc/fstab in the new system after the installation.

To address this swap sharing issue you may be interested in the GPT 
partition scheme : among other advantages, it supports partition labels 
and UUIDs (PARTLABEL and PARTUUID) which are independent of the contents 
of the partition, so they do not change when the partition is formatted.
Debian supports them in /etc/fstab since Jessie.

Recent kernel emulates partition UUIDs with legacy MBR/DOS partition 
scheme, but they are less reliable because these PARTUUID contain the 
partition number, and logical partitions may be renumbered after 
creating or removing another logical partition. That is another reason 
not to use logical partition device names in /etc/fstab.

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

#187386

On Thu 28 Sep 2017 at 10:29:27 (+0200), Pascal Hambourg wrote:
> Le 28/09/2017 à 09:39, Jimmy Johnson a écrit :
> >On 09/27/2017 02:38 AM, Pascal Hambourg wrote:
> >>Le 27/09/2017 à 10:37, Jimmy Johnson a écrit :
> >
> >>>  But if everything is correct and you are using lets say sda1
> >>>as root in your fstab your system will use sda1 as the LABEL,
> >>>I've seen this over and over.
> >>
> >>Nonsense. sda1 is the block device name and does not have
> >>anything to do with the LABEL which is a filesystem metadata
> >>field.
> >>
> >>>But all this is advanced setup for people running more than
> >>>one Linux system and having to edit UUID on all systems
> >>>because you install a new system is undesirable.
> >>
> >>No it does not have anything to do with multiple Linux systems.
> >
> >In fstab a label is used as a device name, a uuid is used as a
> >device name and /dev/sda1 is a device name, you are just trying to
> >make nonsense out of nothing.
> 
> A label or a UUID are not really used as device names, they are used
> *instead* of a device name.
> 
> Anyway, this is not the same as what you wrote earlier and is pure
> nonsense :
> 
> "your system will use sda1 as the LABEL"
> 
> Unless you meant "define 'sda1' as the filesystem/swap label and use
> LABEL='sda1' in /etc/fstab", which is a really bad use of labels
> leading to confusion between labels and device names. Labels are
> meant to be explicit about the contents, not the container.
> 
> >And editing multiple fstab config files because I've installed a
> >new system is, like I said undesirable and why I use device names
> >in both my fstab and grub boot menu.  As you know when a new
> >system is installed swap is formatted and it's uuid gets changed
> >every time it's formatted.
> 
> The Debian installer does this, but I am not sure that all other
> distro installers do the same. Moreover, the Debian installer will
> format an existing swap only if that swap is marked for use (the
> trick is that all existing swaps are automatically marked for use by
> default, so you have to pay attention and unmark them if you do not
> want them to be formatted). IMO this is a real bug in the installer.
> 
> So my general policy when installing Debian is to mark any existing
> swap as "not used", and if I want to share an existing swap, I add
> the line manually in /etc/fstab in the new system after the
> installation.

In the past I have used the VC2 shell to swapon immediately the
partitioner has formatted the partitions (but not swap), ie just
before "Install the base system". This has never caused a problem
for me, but the Installation Guide says:

"In particular, you should always use [sic] let the installer activate
your swap partition and not do this yourself from a shell." (§6.3.8.2)

Any idea why?

Cheers,
David.

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

#187409

On Sat, 23 Sep 2017 04:42:07 +0000 (UTC), Mark Luxton
<truthseeker9@yahoo.ca> wrote:

>RE:Re: Gave up waiting for suspend/resume device
>
>  
>|  
>|   |  
>Re: Gave up waiting for suspend/resume device
>   |  |
>
>  |
>
> 
>
>Try:Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct UUID's in /etc/fstab. Also can use lsblk -f to find the UUID's.
>
>Put the correct UUID's into /etc/fstab, especially swap, for this error.
>
>Put the correct UUID for swap into /etc/initramfs-tools/conf.d/resume.
>
>Run sudo update-initramfs -u
>
>Reboot. Fixed my triple boot of Stretch all with this error, as the swap file had changed.
>Truly, Mark Luxton

Note what occurs when there is no image in the swap FS and initramfs
is expecting to find one.  

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

#187411

Le 29/09/2017 à 18:31, Larry Dighera a écrit :
> 
> Note what occurs when there is no image in the swap FS and initramfs
> is expecting to find one.

A swap is not a filesystem.
The initramfs does not expect to find a hibernation image. If the swap 
contains a hibernation image then it is used to resume the system. 
Otherwise the normal boot proceeds.

[toc] | [prev] | [standalone]

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

csiph-web