Hello all,

I am brand new to unraid, built a nas just for this purpose.

I got two drives for this nas, one is a 2TB Samsung 970 EVO Plus and one is a 2TB SK Hynix Gold P31.

I have the Samsung in slot M_1 and Hynix in slot M_2. They are both recognized by unraid and successfully added to cache pool in zfs mirror with the array started.

I am doing a preclear of my drives, so I haven't fully spun everything up yet. However, I noticed that after a couple of days, the Samsung drive became unresponsive on the main dashboard. It had no temperature details and upon further investigation was basically unconnectable. I rebooted and nothing was resolved. I saw a post saying they had similar issues and had to full shut down, then start from cold and this resolved it.

I googled around and found these threads:
https://www.reddit.com/r/unRAID/comments/1pfqubu/my_nvme_drives_randomly_get_unrecognized_after_a/

https://forums.unraid.net/topic/187748-4tb-samsung-990-pro-nvme-cache-drive-multiple-drive-failures/
https://forums.unraid.net/topic/132024-guide-how-to-upgrade-samsung-nvmessd-firmware/
Basically saying with these drives there is some firmware update. So I went thru this process detailed above of updating the firmware, but long story short it seems that my drive doesn't have any new firmware per this link: https://arstechnica.com/civis/threads/is-anyone-else-having-issues-when-trying-to-update-their-samsung-970-evo-plus.1481103/

So I'm back to square one. I am trying to understand if anyone else has had this issue with a samsung 970 evo plus drive dropping out of their array randomly and if there is any other fix aside from updating firmware since mine won't let me update.

I saw these threads:
https://forums.unraid.net/bug-reports/stable-releases/nvme-dropping-offline-constantly-r4181/

https://forums.unraid.net/topic/164041-does-your-device-have-a-faulty-power-saving-mode-enabled-nvme-issues/
which recommends "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" to bzroot. I have not tried this yet.

Edited January 22Jan 22 by ratmanjones

Post diagnostics next time it happens

On 1/20/2026 at 2:16 AM, Michael_P said:

Post diagnostics next time it happens

Just occurred again in the last hour or so. Posting diagnostic here. By my count there was roughly a 40 hour interval from fresh boot to drive falling out, which is similar to the interval the first time it happened.

Note that I did not add "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" to boot yet.

geofront-diagnostics-20260121-1745.zip

Not sure if I'm looking in the right place but in syslog I see this:

Jan 21 17:33:57 GeoFront kernel: nvme nvme0: I/O tag 22 (f016) opcode 0xa (Admin Cmd) QID 0 timeout, reset controller
Jan 21 17:35:28 GeoFront kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan 21 17:36:00 GeoFront kernel: nvme 0000:01:00.0: not ready 1023ms after FLR; waiting
Jan 21 17:36:01 GeoFront kernel: nvme 0000:01:00.0: not ready 2047ms after FLR; waiting
Jan 21 17:36:03 GeoFront kernel: nvme 0000:01:00.0: not ready 4095ms after FLR; waiting
Jan 21 17:36:07 GeoFront kernel: nvme 0000:01:00.0: not ready 8191ms after FLR; waiting
Jan 21 17:36:16 GeoFront kernel: nvme 0000:01:00.0: not ready 16383ms after FLR; waiting
Jan 21 17:36:33 GeoFront kernel: nvme 0000:01:00.0: not ready 32767ms after FLR; waiting
Jan 21 17:37:09 GeoFront kernel: nvme 0000:01:00.0: not ready 65535ms after FLR; giving up
Jan 21 17:37:09 GeoFront kernel: nvme nvme0: Disabling device after reset failure: -25
Jan 21 17:45:29 GeoFront kernel: block nvme0n1: the capability attribute has been deprecated.
Jan 21 17:45:29 GeoFront kernel: r8169 0000:81:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM

Edited January 22Jan 22 by ratmanjones

Try this: on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Reboot and see if it makes a difference.

22 hours ago, JorgeB said:

Try this: on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Reboot and see if it makes a difference.

thank you for this.

I ended up moving the drive to slot 3 and updating my bios. if that does not fix, I will then try this next. Appreciate it!