Dennis HilkLinux Fix LabDE

Boot, GRUB & systemd-boot

Boot waits for an obsolete hibernation resume device

A stale resume UUID can delay an otherwise valid cold boot after swap changes; identify resume configuration separately from root storage.

Editorial source review: Start with the evidenceShare this guide
On this page
  1. Symptoms & scope
  2. Possible causes
  3. Diagnose safely
  4. Evidence-guided next steps
  5. References & review
  6. Related problems

Symptoms & scope

  • Boot pauses while waiting for suspend/resume device, then may continue.
  • The old swap UUID remains in initramfs or kernel arguments after swap was recreated.

Relevant environment

Linux hibernation resume using initramfs-tools, dracut or systemd-hibernate-resume. Cold-boot repairs must not discard an intended suspended session.

Recognizable messages (synthetic examples)
Begin: Running /scripts/local-premount ... Gave up waiting for suspend/resume device

Check obsolete swap UUID or early encrypted mapping separately from root-device discovery.

Possible causes

These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.

  • The configured resume device may have been removed or received a new UUID.
  • An inaccessible encrypted swap mapping or stale swapfile offset can also make resume unavailable; root= and resume= serve different purposes.

Diagnose safely

Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.

Check 1

Read resume=, resume_offset= and noresume in the current boot without changing them.

cat /proc/cmdline

Interpret the result: Compare a resume selector separately from root=. A correct root does not make an obsolete resume target valid.

Check 2

Read currently active swap only; this does not enable, disable or recreate swap.

swapon --show --output=NAME,TYPE,SIZE,USED

Interpret the result: Compare available swap locations with the configured resume target and its verified UUID. An inactive resume device might still exist, so absence here is not sufficient diagnosis.

Evidence-guided next steps

Remove an obsolete resume path for cold boots

If hibernation is deliberately unused and this is a confirmed cold boot, remove the obsolete resume selector through the distribution’s supported configuration and regenerate its initramfs/entries. A one-boot noresume comparison can confirm the delay source.

Precautions: Do not skip resume while intending to recover a hibernated session; its saved work can be lost, and writing to its filesystems before a later resume is unsafe.

Recovery / rollback: Restore the recorded resume configuration before using hibernation again; discard a temporary menu edit by rebooting normally.

Did this solution help you?

Share this solution#

Update the verified hibernation target

If hibernation is needed, configure the actual supported swap target and, for a swapfile, its filesystem-specific supported offset. Ensure encrypted swap is available early and regenerate the selected kernel’s resume integration.

Precautions: Do not guess offsets, recreate swap containing a needed image or resume after mounting its filesystems for modification. Test only after a clean shutdown.

Recovery / rollback: Restore previous verified target/configuration if the new setup fails; return to cold boots until resume is validated.

Did this solution help you?

Share this solution#

References & review

This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.