My UEFI system has GRUB on Tumbleweed set up as the primary bootloader. For some reason for my Tumbleweed bootloader entry (i.e. the one, that if selected in GRUB, will boot Tumbleweed) on the right-hand side of the resume= equation there’s the UUID of a file system that doesn’t exist. As a result of this a device service (wherein it attempts to mount the file system mentioned in the resume equation) is started by systemd that times out after 1 & 1/2 minutes (or 90 seconds). If you’re wondering if I’ve re-formatted a file system since the entry was made and that’s the reason, well I just re-ran
I don’t use UUIDs in it any more as I do distro hop a fair bit on other partitions so before long some of the UUIDs become incorrect. I have commented many out because with all of them included I find I’m sent to emergency mode as some fail to mount, although I don’t know why /data partitions exist on each distro and each partition exists.
Yes, that happened to me and to several other folk. It’s an installer bug (reported as Bug 1071354.
It is also possible that you caused the problem yourself.
It comes from “/etc/default/grub”. You can fix it there. Or you can fix it with Yast Bootloader where it shows up as the kernel command line. The “resume=” parameter should be for your swap partition. You can find the correct UUID of the swap partition, using the “blkid” command (as root).
My best guess is that this was caused by your installing of another linux system. Some linux installers insist on reformatting the swap partition (or restructuring with “mkswap”), and that changes the UUID. Maybe recheck that after every new linux install. Or define swap with the “/dev/disk/by-id” way of accessing it, since that won’t change when the UUID changes.
Your swap seems to be “/dev/sda2”. So use
ls -l /dev/disk/by-id/* | grep sda2
and the output should give you the “by-id” device to use in “resume=”. If it gives more than one choice, just pick one (probably the first if you don’t have a reason for a different choice).
Rofl, I feel so silly. Yes I apparently did add that to GRUB_CMDLINE_LINUX_DEFAULT. Can’t even remember why I did that, but I think it was part of what I found on the net to quiet the boot process (as I also have “splash=silent quiet” in it).