"Gave up waiting for suspend/resume device" [SOLVED]

dbickin · 2023-01-19 04:26:47

I finally broke down and gave Beryllium a try. An hour or so trying to get it to look like something I could use, I went back to my trusty Helium install. Unfortunately, when I boot Helium, I get a noticeable delay during boot and the message "Gave up waiting for suspend/resume device."

Some Googling and I gather the problem is that the Beryllium install reformatted the swap partition changing its UUID but Helium is still trying to find the old UUID.

How should I fix the problem?

Thanks,
David

Last edited by dbickin (2023-01-26 16:37:05)

hhh · 2023-01-19 05:31:51

In Beryillium /etc/initramfs-tools/conf.d/resume (create the file "resume") add RESUME=none. Run "sudo update-initramfs -u" in a terminal. Reboot.

Post back if it solves this or doesn't, please!

johnraff · 2023-01-19 06:10:00

dbickin wrote:

when I boot Helium, I get a noticeable delay during boot and the message "Gave up waiting for suspend/resume device."
Some Googling and I gather the problem is that the Beryllium install reformatted the swap partition changing its UUID but Helium is still trying to find the old UUID.

Often happens. You need to edit /etc/fstab in Helium with the new UUID. 'lsblk -o +UUID' will give it.

To avoid that in future, in the installer choose not to make a swap partition, and post-install edit /etc/fstab to use the existing swap.

Even better, give the swap partition a lable (eg "swap") and use that in fstab instead of the UUID.

dbickin · 2023-01-19 17:49:12

@hhh: Beryllium doesn't have the problem, it CAUSED the problem. While I have found that Beryllium does two things that Helium can't, that really isn't enough for me to "waste" my time trying to get Beryllium to look and act the way I want.

@johnraff: thanks!

johnraff · 2023-01-19 23:54:26

The swap UUID problem is caused by the Debian installer, it's not BunsenLabs specific.

If you want Beryllium to look like default Helium it's very easy:
Menu > Utilities > BLOB Themes Manager > View Saved > Helium_Beam > Restore

If you choose to stay with Helium itself, which is based on Debian old-old-stable (Stretch) and now under life support, you will eventually run into issues which are likely to waste more of your valuable time.

dbickin · 2023-01-20 02:37:42

FSTAB wasn't the problem. I had already removed that new-fangled UUID garbage from it years ago. (But I'll bet the new install DOES have UUIDs in it. Gotta fix that.)

I am guessing the problem is in /etc/initramfs-tools/conf.d/resume I put the new swap UUID in there, but I guess I need to Run "sudo update-initramfs -u" to copy the UUID into the actual initramfs.

johnraff wrote:

The swap UUID problem is caused by the Debian installer, it's not BunsenLabs specific.

I hope I never said anything to imply that I was somehow blaming you guys. Upgrading Bunsenlabs is a walk in the park compared to the dumpster fire of upgrading ubuntu with gnome. The Gnome devs being jerks is what made me hunt out crunchbang all those years ago.

If you want Beryllium to look like default Helium it's very easy:
Menu > Utilities > BLOB Themes Manager > View Saved > Helium_Beam > Restore

Maybe I'll try that, but I know that won't figure out which programs I installed and which scripts I changed to use my preferred programs.

If you choose to stay with Helium itself, which is based on Debian old-old-stable (Stretch) and now under life support, you will eventually run into issues which are likely to waste more of your valuable time.

My time isn't valuable, I'm just a lazy crotchety old shit.

Lets say I wanted to go the upgrade route. I know from a previous email you said I would need to upgrade from Helium to Lithium then from Lithium to Beryllium. Now I do NOT want the process to in any way affect my HELIUM install on sda5. How would I clone the Helium install onto sda6, so I could do the upgrade there? I'm sure that would just introduce a host of UUID madness to deal with. I think I had tried that when I upgraded to HELIUM, and the errors made me go back to my old procedure of manually installing and spending days trying to figure out what to change by hand.

David

johnraff · 2023-01-20 06:20:42

dbickin wrote:

...figure out which programs I installed and which scripts I changed to use my preferred programs.

For file manager, text editor, media player and image viewer there are BL aliases bl-file-manager etc which are used in our scripts (I can't speak for your own scripts of course). And the Debian x-terminal-emulator etc. To switch eg to spacefm instead of Thunar:
menu > System > Edit Debian Alternatives > find bl-file-manager and edit.
There's no need to edit each script individually.
In fact in the case of spacefm just install it and uninstall Thunar, the switch will go automatically.
(See menu > System > About Bunsen Alternatives.)

But in general, to copy all your installed apps into a new install of Beryllium means pulling a list out of the Helium system ( 'apt-mark showmanual > manual-list.txt' will make a list of all the manually installed packages) and applying it in the new one. Some of the packages will have changed names, or no longer exist...

dbickin · 2023-01-25 21:27:50

Getting back to this.

I tried RESUME=UUID={new UUID of Swap drive}, and ran `sudo update_initramfs -u`.

No Joy.

I tried RESUME=none, then ran `sudo update_initramfs -u` but still no joy.

Every time I reboot, there is a delay. I hear the drive seeking for a while, then the "Gave up waiting..." message is displayed.

Anything else I can try?

Thanks,
David

johnraff · 2023-01-26 00:51:17

Are you sure the swap entry in fstab is correct?

dbickin · 2023-01-26 01:46:57

# swap was on /dev/sda3 during installation
/dev/sda3 none            swap    sw              0       0

Looks correct to me.

johnraff · 2023-01-26 02:34:03

'lsblk' would probably be able to confirm that /dev/sda3 is the swap partition.

Is your swap enabled now? 'swapon --show'

dbickin · 2023-01-26 03:16:07

lsblk

├─sda3   8:3    0   1.9G  0 part [SWAP]

swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/sda3 partition 1.9G   0B   -1

And conky has the correct partition size for the swap.

But if I put RESUME=none, in the resume file as hhh suggested, does the swap partition even matter?

David

sleekmason · 2023-01-26 03:41:12

Just to run through the process again in case something was missed. Also, is update-grub not necessary? Sorry in advance if I have misunderstood the question.

To get correct uuid for the swap partition as seen by the system:
blkid -l -t TYPE=swap | awk '{printf $2}'

Make sure /etc/fstab and /etc/initramfs-tools/conf.d/resume match the above output. then:
sudo update-initramfs -u -k all
sudo update-grub

dbickin · 2023-01-26 16:36:22

sleekmason wrote:

sudo update-initramfs -u -k all
sudo update-grub

Well, I looks like the -k or the all parameter to update-initramfs did the trick.

It now reboots with the "Gave up waiting..." message.

Thanks to all that helped.

#1 2023-01-19 04:26:47

"Gave up waiting for suspend/resume device" [SOLVED]

#2 2023-01-19 05:31:51

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#3 2023-01-19 06:10:00

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#4 2023-01-19 17:49:12

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#5 2023-01-19 23:54:26

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#6 2023-01-20 02:37:42

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#7 2023-01-20 06:20:42

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#8 2023-01-25 21:27:50

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#9 2023-01-26 00:51:17

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#10 2023-01-26 01:46:57

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#11 2023-01-26 02:34:03

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#12 2023-01-26 03:16:07

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#13 2023-01-26 03:41:12

Re: "Gave up waiting for suspend/resume device" [SOLVED]

#14 2023-01-26 16:36:22

Re: "Gave up waiting for suspend/resume device" [SOLVED]

Board footer