Getting a 'Unable to resume' message while turning on laptop

I’m getting this message / error while booting up laptop

If I’m not mistaken I kind of get this sort of similar message while resuming laptop from hibernation but I never got this during booting , should I be concerned about it ? cus it’s new


Mod edit:-
@Char – Please avoid posting images of text – recreate the text instead. Image removed and substituted for text by way of example. No charge. Please adopt this habit in future.

inxi -zv8
and
lsblk -f
or
blkid

would help to understand what the message might mean, which partition of your system it refers to

It says it tried to resume from some partition, but it could not
and the boot process continues - continues normally, I guess.

Because it does continue, it could be interesting to find out why this happens,
but it is likely nothing to be concerned about or wanting immediate attention or action.

System:
  Kernel: 6.1.161-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=f2158531-513d-457e-99eb-962cabe45fbd rw quiet apparmor=1
    security=apparmor resume=UUID=d4a2bbfe-f657-4b6d-ad7b-291b32ce3bb1
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.22.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Inspiron 15-3567 v: N/A
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0FGN4M v: A00 serial: <superuser required> part-nu: 078C
    uuid: <superuser required> Firmware: UEFI vendor: Dell v: 2.10.0
    date: 05/10/2019
Battery:
  ID-1: BAT0 charge: 21.4 Wh (64.5%) condition: 33.1/41.4 Wh (80%)
    volts: 14.88 min: 14.8 model: LGC-LGC2.80 DELL 7PY0D37 type: Li-ion
    serial: <filter> charging: status: discharging cycles: N/A
Memory:
  System RAM: total: 8 GiB available: 7.63 GiB used: 2.58 GiB (33.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: DIMM A type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 4 GiB speed: spec: 2400 MT/s actual: 2133 MT/s volts: note: check
    curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: 80AD000080AD part-no: HMA851S6AFR6N-UH serial: <filter>
  Device-2: DIMM B type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 4 GiB speed: spec: 2400 MT/s actual: 2133 MT/s volts: note: check
    curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: 80CE000080CE part-no: M471A5244BB0-CRC serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i3-6006U bits: 64 type: MT MCP arch: Skylake
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x4E (78) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
    smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 500 min/max: 400/2000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 500 2: 500 3: 500 4: 500 bogomips: 16006
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb
    ibpb_exit_to_user ibrs intel_pt invpcid invpcid_single lahf_lm lm mca mce
    md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
    pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts
    rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1
    sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
    tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Skylake-U GT2 [HD Graphics 520] vendor: Dell driver: i915
    v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
  Device-2: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2
    chip-ID: 1bcf:28c0 class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0690 built: 2015 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2 chroma: red:
    x: 0.592 y: 0.349 green: x: 0.329 y: 0.557 blue: x: 0.153 y: 0.118 white:
    x: 0.314 y: 0.329 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1920x1080
  EDID-Warnings: 1: parse_edid: unknown flag 0
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 520 (SKL GT2)
    device-ID: 8086:1916 memory: 7.45 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 6 device: 0 type: integrated-gpu name: Intel
    HD Graphics 520 (SKL GT2) driver: mesa intel v: 25.3.4-arch1.1
    device-ID: 8086:1916 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl, snd_soc_avs, snd_sof_pci_intel_skl
    bus-ID: 00:1f.3 chip-ID: 8086:9d70 class-ID: 0403
  API: ALSA v: k6.1.161-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.10 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0-98-gb096 status: active with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl
Network:
  Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: Dell driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0042 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: deprecated noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Info: services: mld, NetworkManager, smbd, systemd-timesyncd,
    wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:4 chip-ID: 0cf3:e009
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 931.51 GiB used: 844.03 GiB (90.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 1002 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 85.59 GiB (87.4%)
    fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: f2158531-513d-457e-99eb-962cabe45fbd
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: 6699-007E
  ID-3: /mnt/be9fd59c-519e-4b50-a158-0e15e4410673 raw-size: 822.42 GiB
    size: 808.43 GiB (98.30%) used: 758.41 GiB (93.8%) fs: ext4 dev: /dev/sda4
    maj-min: 8:4 label: N/A uuid: be9fd59c-519e-4b50-a158-0e15e4410673
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.59 GiB used: 29.3 MiB (0.3%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: d4a2bbfe-f657-4b6d-ad7b-291b32ce3bb1
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-5:2 info: Sunplus Innovation Integrated_Webcam_HD type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 1bcf:28c0 class-ID: 0e02
  Device-2: 1-6:3 info: Realtek RTS5129 Card Reader Controller
    type: <vendor specific> driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc
    interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 0bda:0129 class-ID: ff00 serial: <filter>
  Device-3: 1-8:4 info: Qualcomm Atheros type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 0cf3:e009 class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 37.0 C pch: 36.0 C mobo: 37.0 C
  Fan Speeds (rpm): cpu: 0
Repos:
  Packages: 1737 pm: pacman pkgs: 1731 libs: 465 tools: pamac pm: snap pkgs: 6
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.meowsmp.net/manjaro/stable/$repo/$arch
    2: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    3: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    4: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    5: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    7: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    8: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 208
  1: cpu: 500% command: ps pid: 15867 mem: 3.71 MiB (0.0%)
  2: cpu: 50.0% command: sh pid: 15866 mem: 3.06 MiB (0.0%)
  3: cpu: 7.5% command: chromium pid: 14173 mem: 325.9 MiB (4.1%)
  4: cpu: 4.8% command: kwin_wayland pid: 1168 mem: 193.1 MiB (2.4%)
  5: cpu: 4.5% command: chromium pid: 13892 mem: 316.0 MiB (4.0%)
  Memory top: 5 of 208
  1: mem: 446.7 MiB (5.7%) command: chromium pid: 13844 cpu: 4.2%
  2: mem: 397.0 MiB (5.0%) command: plasmashell pid: 1351 cpu: 0.7%
  3: mem: 325.9 MiB (4.1%) command: chromium pid: 14173 cpu: 7.5%
  4: mem: 316.0 MiB (4.0%) command: chromium pid: 13892 cpu: 4.5%
  5: mem: 244.6 MiB (3.1%) command: chromium pid: 15138 cpu: 3.6%
Info:
  Processes: 208 Power: uptime: 4h 37m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.04 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 258 default: graphical tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.40

lsblk -f

NAME   FSTYPE   FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core18/2976
loop1  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core18/2979
loop2  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core20/2686
loop3  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core22/2216
loop4  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core22/2292
loop5  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/core20/2717
loop6  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/ngrok/350
loop7  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/ngrok/345
loop8  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/snapd/25577
loop9  squashfs 4.0                                                    0   100% /var/lib/snapd/snap/snapd/25935
sda                                                                             
├─sda1 ext4     1.0         f2158531-513d-457e-99eb-962cabe45fbd    7.3G    87% /
├─sda2 vfat     FAT32       6699-007E                             510.7M     0% /boot/efi
├─sda3 swap     1           d4a2bbfe-f657-4b6d-ad7b-291b32ce3bb1                [SWAP]
└─sda4 ext4     1.0         be9fd59c-519e-4b50-a158-0e15e4410673    8.9G    94% /mnt/be9fd59c-519e-4b50-a158-0e15e4410673

blkid -o list

device                         fs_type      label         mount point                        UUID
----------------------------------------------------------------------------------------------------------------------------------
/dev/loop1                                                /var/lib/snapd/snap/core18/2979    
/dev/loop8                                                /var/lib/snapd/snap/snapd/25577    
/dev/loop6                                                /var/lib/snapd/snap/ngrok/350      
/dev/loop4                                                /var/lib/snapd/snap/core22/2292    
/dev/loop2                                                /var/lib/snapd/snap/core20/2686    
/dev/loop0                                                /var/lib/snapd/snap/core18/2976    
/dev/loop9                                                /var/lib/snapd/snap/snapd/25935    
/dev/loop7                                                /var/lib/snapd/snap/ngrok/345      
/dev/sda4                                                 /mnt/be9fd59c-519e-4b50-a158-0e15e4410673 
/dev/sda2                                                 /boot/efi                          
/dev/sda3                                                 [SWAP]                             
/dev/sda1                                                 /                                  
/dev/loop5                                                /var/lib/snapd/snap/core20/2717    
/dev/loop3                                                /var/lib/snapd/snap/core22/2216   

I get a similar message.

On my system it refers to the Swap Partition, so I would assume it does so on the OPs (or the swap File)

It continues to boot normally, so I don’t worry about it.

1 Like

The message indicates that hibernation data could not be read from disk.

i don’t know the consequences of not being able to resume from hibernation, but I assume that some kind of data loss could occur, e.g. unsaved changes to a large document - or even worse - file system corruption.

1 Like

We don’t know if you have setup hibernation properly, if you want to fix it best study the wiki first:

1 Like

The message does refer to your swap partition.
Nothing wrong there.

Why the system is apparently trying to resume when you didn’t ask it to,
instead of just booting?

I don’t know. Can’t explain.

I still would not worry about it.

Does it resume when you ask it to resume? When you hibernate instead of poweroff?

1 Like

I must clear the confusion , this is the message I get when I resume from hibernation and yes it resume without any trouble , should’ve mention sort of similar message in my original post

but the message I’m getting during booting in my original post

Maybe the 8GB ram need a swap partition bigger than the current 8GB in order to handle hibernation.
Changing that would need a clean-up of the drives, size: 97.87 GiB used: 85.59 GiB (87.4%) is bound to cause issues sooner or later.

For the system to know what kind of startup the current start is, it needs a pointer.

What that pointer is or where it is stored I don’t have any clear picture.

However I do recall reading somewhere that - at least - systemd-boot writes data at a specific location in the UEFI firmware - and the message - my guess - could be that the kernel is informing the user; this is not a cold boot but a resume from hibernation.

Most likely what is described in the following thread is your “little issue”:

So it’s harmless but can be fixed by removing the resume kernel parameter in /etc/default/grub.

3 Likes

My interpretation:
system is checking for the presence of a hibernation image - as it should,
doesn’t find one (because the system wasn’t hibernated),
tells you about it,
and continues booting normally.

All good.
It’s not an error, it’s just information.

1 Like

It’s all described by twig in the link:

The resume kernel parameter in your boot entry forces systemd to try to wake up the system because it has no idea if the system is hibernated or simply shut down. If the system isn’t hibernated, the wake-up call fails. Systemd throws the warning you see and continues with the normal boot.

You can ignore the message or fix it by removing the resume kernel parameter from /etc/default/grub if you don’t want to see this warning.

1 Like

That is my interpretation, when I get the message.

Thank you

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.