* [REGRESSION] Boot failure on NVMe multipath LVM root since 6.19-rc8 (dracut cannot find root)
@ 2026-02-16 16:50 Kumar, Sumit
2026-02-17 16:59 ` Thorsten Leemhuis
0 siblings, 1 reply; 2+ messages in thread
From: Kumar, Sumit @ 2026-02-16 16:50 UTC (permalink / raw)
To: linux-next; +Cc: Narasimhan.V
Hi,
I am observing a boot regression where the system fails to boot and drops into the dracut emergency shell because the LVM root device is not detected. The issue is reproducible with both linux-next and mainline kernels.
Regression Status (linux-next):
Boot passes: 6.19.0-rc7-next-20260129
Boot fails: 6.19.0-rc8-next-20260203
This indicates a regression introduced between the above kernel versions.
Environment:
Distribution: RHEL-based system
Storage: NVMe disk with multipath
Root filesystem: LVM on NVMe multipath device
Boot method: local disk
System layout:
[root@cinnabar-3f48host ~]# lsblk
nvme1n1
├─nvme1n1p1 /boot/efi
├─nvme1n1p2 /boot
└─nvme1n1p3
├─rhel_cinnabar--3f48host-root /
├─rhel_cinnabar--3f48host-swap [SWAP]
└─rhel_cinnabar--3f48host-home /home
The affected system has the root disk configured on multipath over NVMe.
A system configured with multipath over SCSI disk boots successfully and does not show this issue.
Problem Description:
During boot, initramfs fails to detect the LVM root and swap devices and eventually enters dracut emergency mode.
Actual Behavior:
[ 202.597607] dracut-initqueue[1317]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2frhel_cinnabar-3f48host\x2froot.sh: "[ -e "/dev/rhel_cinnabar-3f48host/root" ]"
[ 202.599178] dracut-initqueue[1317]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2frhel_cinnabar-3f48host\x2fswap.sh: "[ -e "/dev/rhel_cinnabar-3f48host/swap" ]"
[ 202.601189] dracut-initqueue[1317]: Warning: dracut-initqueue: starting timeout scripts
[ 202.601312] dracut-initqueue[1317]: Warning: Could not boot.
Starting Dracut Emergency Shell...
Warning: /dev/mapper/rhel_cinnabar--3f48host-root does not exist
Warning: /dev/rhel_cinnabar-3f48host/root does not exist
Warning: /dev/rhel_cinnabar-3f48host/swap does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode.
The system generates /run/initramfs/rdsosreport.txt and drops to the dracut shell.
Expected Behavior:
The system should detect the LVM volumes and boot normally.
Steps to Reproduce:
1. Checkout linux-next tag `6.19.0-rc7-next-20260129`.
2. Build and install the kernel.
3. Boot the system → boot succeeds.
4. Checkout linux-next tag `6.19.0-rc8-next-20260203`.
5. Build and install the kernel.
6. Boot the system → boot fails and drops to dracut emergency shell.
The issue reproduces consistently on systems with NVMe multipath root.
Mainline Results:
The same issue is also observed with mainline kernels:
Boot passes with 6.19.0-72c395024dac.
Boot failure starts from 6.19.0-192c0159402e, where the system drops to the dracut emergency shell with the same behavior described above.
Please let me know if additional logs, kernel configuration, or further debugging information is required.
Thanks,
Sumit Kumar
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [REGRESSION] Boot failure on NVMe multipath LVM root since 6.19-rc8 (dracut cannot find root)
2026-02-16 16:50 [REGRESSION] Boot failure on NVMe multipath LVM root since 6.19-rc8 (dracut cannot find root) Kumar, Sumit
@ 2026-02-17 16:59 ` Thorsten Leemhuis
0 siblings, 0 replies; 2+ messages in thread
From: Thorsten Leemhuis @ 2026-02-17 16:59 UTC (permalink / raw)
To: Kumar, Sumit; +Cc: Narasimhan.V, linux-next
Lo! Thx for reporting this!
On 2/16/26 17:50, Kumar, Sumit wrote:
>
> I am observing a boot regression where the system fails to boot and
> drops into the dracut emergency shell because the LVM root device is
> not detected. The issue is reproducible with both linux-next and
> mainline kernels.
Then it's best to completely leave -next out of the picture, as it
confused things. The subject line is an example for that, as from the
commits you mentioned below the regression was introduced post 6.19 (and
not before -rc8).
> Mainline Results: The same issue is also observed with mainline
> kernels: Boot passes with 6.19.0-72c395024dac. Boot failure starts
> from 6.19.0-192c0159402e, where the system drops to the dracut
> emergency shell with the same behavior described above.
Maybe someone will be able to find what's wrong using the problem
description you gave. But given that nobody replied yet that seems
unlikely, hence: you you maybe bisect between 72c395024dac and
192c0159402e? Then we know whom to contact.
https://docs.kernel.org/admin-guide/bug-bisect.html
Ciao, Thorsten
#regzbot report: ^
#regzbot introduced: 72c395024dac..192c0159402e
#regzbot title: Boot failure on NVMe multipath LVM
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-02-17 16:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-16 16:50 [REGRESSION] Boot failure on NVMe multipath LVM root since 6.19-rc8 (dracut cannot find root) Kumar, Sumit
2026-02-17 16:59 ` Thorsten Leemhuis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox