nvme Unable to chnge power state from D3cold t D0 device inaccessible

phoenix324 · 2026-09-01 05:13:08

troubleshooting my friend laptop, he was using windows 11 and nvme stopped working and at bootup message saying " Boot device not found. Please install an operating system on your hard disk"

I booted into fedora live iso as i am still not know of any way to get output from tty to other system, when using archlinux live iso.

Also the nvme is getting super hot, i confirmed it by opening the laptop back panel and using the system.

liveuser@localhost-live:~$ sudo lspci -nnk | grep -A 5 -B 2 -iE 'nvme|non-volatile|volume management'
0000:00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator module [8086:9a11] (rev 01)
        Subsystem: Hewlett-Packard Company Device [103c:87fd]
0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller [8086:9a0b]
        Subsystem: Intel Corporation Device [8086:0000]
        Kernel driver in use: vmd
        Kernel modules: vmd
0000:00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20)
        Subsystem: Hewlett-Packard Company Device [103c:87fd]
--
        Subsystem: Hewlett-Packard Company Device [103c:87fd]
        Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller 980 (DRAM-less) [144d:a809]
        Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
        Kernel modules: nvme
liveuser@localhost-live:~$ sudo lspci -vv -s e1:00.0
10000:e1:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980 (DRAM-less) (prog-if 02 [NVM Express])
        Subsystem: Samsung Electronics Co Ltd Device a801
        !!! Unknown header type 7f
        Interrupt: pin ? routed to IRQ -2147483648
        Region 0: Memory at 82000000 (64-bit, non-prefetchable) [size=16K]
        Kernel modules: nvme

liveuser@localhost-live:~$ sudo nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev  
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
liveuser@localhost-live:~$ sudo nvme list-subsys
liveuser@localhost-live:~$ ls -l /dev/nvme*
crw-------. 1 root root 10, 260 Aug 31 22:43 /dev/nvme-fabrics
liveuser@localhost-live:~$ ls -l /sys/class/nvme/
total 0
liveuser@localhost-live:~$ lsmod | grep -E 'nvme|vmd'
nvme                   73728  0
vmd                    28672  0
nvme_tcp              102400  0
nvme_fabrics           49152  1 nvme_tcp
nvme_core             274432  3 nvme_tcp,nvme,nvme_fabrics
nvme_keyring           20480  3 nvme_tcp,nvme_core,nvme_fabrics
nvme_auth              32768  1 nvme_core
liveuser@localhost-live:~$ sudo journalctl -k -b --no-pager | grep -iE 'nvme|pcie|aer|vmd|timeout|reset|error|fail'
Aug 31 22:43:41 fedora kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS03._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS05._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20250404/dswload2-326)
Aug 31 22:43:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250404/psobject-220)
Aug 31 22:43:41 fedora kernel: ACPI: \_SB_.PC00.VMD0.VOL0.V0PR: New power resource
Aug 31 22:43:41 fedora kernel: ACPI: \_SB_.PC00.VMD0.VOL1.V1PR: New power resource
Aug 31 22:43:41 fedora kernel: ACPI: \_SB_.PC00.VMD0.VOL2.V2PR: New power resource
Aug 31 22:43:41 fedora kernel: ACPI: \_SB_.PC00.VMD0.VOL3.V3PR: New power resource
Aug 31 22:43:41 fedora kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR DPC]
Aug 31 22:43:41 fedora kernel: pci 0000:00:02.0: [8086:9a78] type 00 class 0x030000 PCIe Root Complex Integrated Endpoint
Aug 31 22:43:41 fedora kernel: pci 0000:00:0e.0: [8086:9a0b] type 00 class 0x010400 PCIe Root Complex Integrated Endpoint
Aug 31 22:43:41 fedora kernel: pci 0000:00:1c.0: [8086:a0bf] type 01 class 0x060400 PCIe Root Port
Aug 31 22:43:41 fedora kernel: pci 0000:01:00.0: [10ec:c821] type 00 class 0x028000 PCIe Endpoint
Aug 31 22:43:41 fedora kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 120
Aug 31 22:43:41 fedora kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 120
Aug 31 22:43:41 fedora kernel: pcieport 0000:00:1c.0: DPC: enabled with IRQ 120
Aug 31 22:43:41 fedora kernel: pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Aug 31 22:43:41 fedora kernel: RAS: Correctable Errors collector initialized.
Aug 31 22:43:42 fedora kernel: vmd 0000:00:0e.0: PCI host bridge to bus 10000:e0
Aug 31 22:43:42 fedora kernel: pci 10000:e0:1d.0: [8086:a0b0] type 01 class 0x060400 PCIe Root Port
Aug 31 22:43:42 fedora kernel: pci 10000:e1:00.0: [144d:a809] type 00 class 0x010802 PCIe Endpoint
Aug 31 22:43:43 fedora kernel: Modules linked in: i915(+) drm_buddy ttm i2c_algo_bit drm_display_helper hid_multitouch uas usb_storage polyval_clmulni vmd(+) cec ghash_clmulni_intel i2c_hid_acpi i2c_hid video intel_oc_wdt wmi nvme_tcp nvme_fabrics pinctrl_tigerlake nvme_core serio_raw nvme_keyring nvme_auth sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi loop fuse i2c_dev nfnetlink
Aug 31 22:43:43 fedora kernel: Modules linked in: i915(+) drm_buddy ttm i2c_algo_bit drm_display_helper hid_multitouch uas usb_storage polyval_clmulni vmd(+) cec ghash_clmulni_intel i2c_hid_acpi i2c_hid video intel_oc_wdt wmi nvme_tcp nvme_fabrics pinctrl_tigerlake nvme_core serio_raw nvme_keyring nvme_auth sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi loop fuse i2c_dev nfnetlink
Aug 31 22:43:43 fedora kernel: Modules linked in: i915(+) drm_buddy ttm i2c_algo_bit drm_display_helper hid_multitouch uas usb_storage polyval_clmulni vmd(+) cec ghash_clmulni_intel i2c_hid_acpi i2c_hid video intel_oc_wdt wmi nvme_tcp nvme_fabrics pinctrl_tigerlake nvme_core serio_raw nvme_keyring nvme_auth sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi loop fuse i2c_dev nfnetlink
Aug 31 22:43:43 fedora kernel: Modules linked in: i915(+) drm_buddy ttm i2c_algo_bit drm_display_helper hid_multitouch uas usb_storage polyval_clmulni vmd(+) cec ghash_clmulni_intel i2c_hid_acpi i2c_hid video intel_oc_wdt wmi nvme_tcp nvme_fabrics pinctrl_tigerlake nvme_core serio_raw nvme_keyring nvme_auth sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi loop fuse i2c_dev nfnetlink
Aug 31 22:43:44 fedora kernel: pci 10000:e0:1d.0: retraining failed
Aug 31 22:43:45 fedora kernel: pci 10000:e1:00.0: can't reset device: -25
Aug 31 22:43:45 fedora kernel: pci 10000:e0:1d.0: bridge window [io  size 0x1000]: failed to assign
Aug 31 22:43:45 fedora kernel: pci 10000:e0:1d.0: bridge window [io  size 0x1000]: failed to assign
Aug 31 22:43:45 fedora kernel: pci 10000:e1:00.0: BAR 0: error updating (0x82000004 != 0xffffffff)
Aug 31 22:43:45 fedora kernel: pci 10000:e1:00.0: BAR 0: error updating (high 0x00000000 != 0xffffffff)
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: can't derive routing for PCI INT A
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: PCI INT A: no GSI
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: PME: Signaling with IRQ 149
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: AER: enabled with IRQ 149
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: DPC: enabled with IRQ 149
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Aug 31 22:43:45 fedora kernel: vmd 0000:00:0e.0: Bound to PCI domain 10000
Aug 31 22:43:45 fedora kernel: nvme nvme0: pci function 10000:e1:00.0
Aug 31 22:43:45 fedora kernel: nvme 10000:e1:00.0: Unable to change power state from D3cold to D0, device inaccessible
Aug 31 22:43:45 fedora kernel: pcieport 10000:e0:1d.0: can't derive routing for PCI INT A
Aug 31 22:43:45 fedora kernel: nvme 10000:e1:00.0: PCI INT A: not connected
Aug 31 22:43:54 fedora systemd[1]: Applying preset policy.
Aug 31 22:43:54 fedora systemd[1]: Populated /etc with preset unit settings.
Aug 31 22:43:54 fedora systemd[1]: Listening on systemd-factory-reset.socket - Factory Reset Management.
Aug 31 22:43:54 fedora systemd[1]: systemd-boot-clear-sysfail.service - Clear SysFail Entry If The Boot Is Successful was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderEntrySysFail-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
liveuser@localhost-live:~$ uname -a
Linux localhost-live 6.17.1-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Oct  6 15:37:21 UTC 2025 x86_64 GNU/Linux
liveuser@localhost-live:~$

Last edited by phoenix324 (2026-09-01 06:20:57)

seth · 2026-09-01 05:56:25

For clarification, you're troubleshooting your friends windows pc using fedora and post a question about something™, I guess, on the archlinux forum?

is getting super hot

Can you read the temperature to quantify "super hot"?
https://wiki.archlinux.org/title/Solid_ … Management

Try the nvme in a different host but your friend hopefully has backups…

still not know of any way to get output from tty to other system

1st link below

phoenix324 · 2026-09-01 06:16:57

For clarification, you're troubleshooting your friends windows pc using fedora and post a question about something™, I guess, on the archlinux forum?

Yes, i know this combination is bad. My main system is arch on my laptop. I only fedora because i wasn't sure how to get the output out from tty but now i know, thanks.

Can you read the temperature to quantify "super hot"?
Try the nvme in a different host

I swapped the nvme between my laptop and my friend laptop, his nvme still not working in mine laptop and mine is working in his, i also tried nvme enclosure but his nvme still won't show.

Also in BIOS and HP BIOS DIAGNOSTIC, at both places the nvme is not showing up.

By super hot, i meant when i swapped mine nvme in his, mine nvme wasn't hot at all and i can keep my finger placed on my nvme easily for longer duration but in case of his nvme, i think i will get first degree burn if i keep my finger on it for more than 5 seconds. And i even fear of even keeping that laptop on as not to make nvme get damaged just from the heat it is producing alone.

I wanted to know is there way to fix the nvme ( data is not important ), in this economy buying new nvme is very costly. Also it's samsung nvme 256gb, and it getting dead just in 3 years from the date of purchase of laptop ( came with laptop ). Just wanted to confirm is buying new the only option.

Also is there way to know what went wrong with nvme, was windows responsible for this?

Edit: fixed the log output posted in post #1

Last edited by phoenix324 (2026-09-01 06:21:39)

seth · 2026-09-01 06:43:02

And i even fear of even keeping that laptop on as not to make nvme get damaged

I'd rather worry about the rest of the system - nvmes can get very hot (70°) under load, but if the controller is fused it could heat up drastically more

I wanted to know is there way to fix the nvme ( data is not important ), in this economy buying new nvme is very costly.

More the clankers and the orange man than "economy"… /grrrr
… but if the controller does no longer respond (and we've ruled out the bus) there's not much you could do (if the data was critical you'd need to employ a rescue center to replace the controller - which is gonna set you back a little more than the new nvme)

Also is there way to know what went wrong with nvme, was windows responsible for this?

You'd have to ask your friend. The system might have generally overheated (running in a backtrack) … it also might have been a bogus firmware update for the nvme - was it symptomatic before?
When you physically inspect the device, does it already look burned? (it's still mostly plastic, there might be some unexpected dark spots)

Arch Linux

#1 2026-09-01 05:13:08

nvme Unable to chnge power state from D3cold t D0 device inaccessible

#2 2026-09-01 05:56:25

Re: nvme Unable to chnge power state from D3cold t D0 device inaccessible

#3 2026-09-01 06:16:57

Re: nvme Unable to chnge power state from D3cold t D0 device inaccessible

#4 2026-09-01 06:43:02

Re: nvme Unable to chnge power state from D3cold t D0 device inaccessible

Board footer