Hi, I'm having a problem with my server.

When I tried to move data in a pool earlier, Windows suddenly told me that I didn't have the necessary permissions.

I checked Unraid and saw that one of my two 2 TB nVME drives from my RAID1 pool was showing as missing.

I saved the logs, restarted the server, and checked again. It was still missing.

I then removed the nVME from the server and installed it in my PC as a test. It was recognized there and all S.M.A.R.T. values were reported as OK.

I have now installed a new 2 TB nVME in the server and restored the RAID1. There are no errors in the logs, the rebuild of the nearly 800 GB ran without errors, and all Docker etc. are running again.

But now I'm a little worried that maybe it's not the nVME that's defective, but something else?

Unfortunately, I don't know much about this, but here are my logs.

(I also saved them on the nVME so that I still have access to them in case of crashes, which is why there are some errors with “syslog-127.0.0.1.log” at the bottom of the logs.

Can anyone help me and tell me whether it was definitely the nVME or whether something else might be defective?

Many thanks in advance.

unraid-syslog-20251211-1705.zip

Dec 11 12:17:37 Unraid kernel: nvme nvme0: I/O tag 345 (e159) opcode 0x1 (I/O Cmd) QID 9 timeout, aborting req_op:WRITE(1) size:49152

Dec 11 12:17:37 Unraid kernel: nvme nvme0: I/O tag 346 (915a) opcode 0x1 (I/O Cmd) QID 9 timeout, aborting req_op:WRITE(1) size:32768

Dec 11 12:18:07 Unraid kernel: nvme nvme0: I/O tag 10 (000a) opcode 0xa (Admin Cmd) QID 0 timeout, reset controller

Dec 11 12:19:38 Unraid kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

NVMe device dropped offline; this sometimes helps:

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.

Thanks for the quick reply!

So you think the nVME might not be broken after all and that it's something else?

Should I reinstall the old nVME and also add the commands you wrote in this config and test it?

(The server has been running stable with this nVME for 2 ½ years without any errors. Can they just suddenly occur without any changes to the server?)

Thank you!

1 hour ago, extrakaese said:

So you think the nVME might not be broken after all and that it's something else?

Typically it's not.

1 hour ago, extrakaese said:

Should I reinstall the old nVME and also add the commands you wrote in this config and test it?

You can add it as another pool with those kernel options and test for now.

Okay, thanks! I'll test the nVME in my second server tonight, so it won't be such a big deal if there are any problems.

If it's not the nVME, what do you think could be causing the problem yesterday?

Maybe a problem with the motherboard?

38 minutes ago, extrakaese said:

what do you think could be causing the problem yesterday?

If you mean the device dropping, can sometimes happen with some hardware and Linux kernel combos.

2 hours ago, JorgeB said:

If you mean the device dropping, can sometimes happen with some hardware and Linux kernel combos.

I have a question related to this but not dealing with an issue, just trying to learn something.

Is it ever considered "normal" during the unraid boot process to see "Device not ready, resetting" messages? Or does this indicate issues with nvme devices dropping offline?

Edited December 12, 2025Dec 12 by MowMdown

43 minutes ago, MowMdown said:

Is it ever considered "normal" during the unraid boot process to see "Device not ready, resetting"

For ATA devices it's normal, for NVMe, I would not think so.