Ubuntu 24.04 won't boot after kernel 6.8.0-86 update: "cryptsetup: waiting for encrypted source device" + "gave up waiting for root file system device"

Support and Help
, , , ,
1

Ubuntu Version:

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.3 LTS
Release:	24.04
Codename:	noble

Problem Description:

After upgrading to kernel 6.8.0-86-generic, my system fails to boot with the message:

cryptsetup: waiting for encrypted source device...

Eventually, in recovery mode, it shows:

Gave up waiting for root file system device.

This issue only affects kernel 6.8.0-86. Previous kernels boot without problems. My system uses full-disk LUKS encryption on a PCIe NVMe SSD (no SATA drives).

This behavior appears similar to a known issue discussed here:
https://discourse.ubuntu.com/t/gave-up-waiting-for-root-file-system-device-no-other-os-installed/54932

Current Workaround:

I can still boot the system by selecting an earlier kernel in GRUB:

  • 6.8.0-85-generic: works (currently in use)
  • 6.8.0-86-generic: fails (with cryptsetup/rootfs error)
  • 6.8.0-84-generic: previously worked but no longer available in GRUB

I am concerned that 6.8.0-85 may also be removed automatically, leaving me unable to access my system.

What I’ve Investigated:

I found a related AskUbuntu thread, where users reported the same cryptsetup error on Dell systems. The accepted solution there was to change the BIOS SATA mode from “RAID On” to “AHCI”.

However, this does not apply to my situation because:

  • I use a PCIe NVMe SSD, not SATA
  • My BIOS has no AHCI or RAID options available

System Information:

  • Laptop: Dell Inspiron 16 (Intel-based)
  • Storage: PCIe NVMe SSD (no SATA devices)
  • Encryption: Full-disk LUKS (default Ubuntu installer)
  • Boot Mode: UEFI
  • Bootloader: GRUB
  • Working Kernel: 6.8.0-85-generic
  • Failing Kernel: 6.8.0-86-generic

What I’ve Tried:

  • Rebooted with older kernel versions (84, 85), 85 still works
  • Verified that only 6.8.0-86 triggers the issue
  • Confirmed there are no SATA or RAID BIOS settings to adjust
  • Cross-checked with related threads and known issues

Questions for the Community:

  1. Is this a known bug? If so, is there a bug report I can follow or contribute to?
  2. Should I report this under the kernel package, cryptsetup, or initramfs?
  3. What is the recommended way to pin or hold a specific kernel in Ubuntu 24.04? And how to know when and how to safely upgrade ?

Any guidance is appreciated. This has been a stressful issue since I rely on this system for daily work and have never had a kernel update break encrypted boot before. Thank you.

Note: this question Help! "Gave up waiting for root file system device." boot error - #3 by tea-for-one was left pretty much unanswered.

PS: I think that I will stop upgrades for Ubuntu for a few months, this has only led to stress in the past weeks.

1 Like
2

As this is your working kernel, it cannot be removed automatically because it is in use.

Now, just to be safe, perform any upgrades via the terminal where you will see which packages are being added or upgraded.

sudo apt update

sudo apt upgrade

Temporarily, avoid sudo apt full-upgrade because it can automatically remove unwanted (obsolete) packages.

By the way, the current kernel for Ubuntu 24.04.3 is 6.14.0-33 supplied if you have HWE (Hardware Enablement). More info here
Worth investigating?

Probably no need to pin 6.8.0-85 if you are constantly using it.
You can edit grub to make it default if you wish

1 Like
3

Looks like a kernel regression. Can you please file a bug on Launchpad? Boot the functional kernel and run:

$ sudo ubuntu-bug linux

Then add details about the problems.

3 Likes