Hello!

I am experiencing an issue where my cache drive seems to be disconnecting and causing errors and am looking for some help with troubleshooting. About 2 weeks ago I had an issue where Docker would not start and I could not see any containers. in the logs I saw this: BTRFS error (device nvme0n1p1 state EA): bdev /dev/nvme0n1p1 errs: wr 140, rd 2523, flush 0, corrupt 0, gen 0

On restart my cache drive had seemingly disappeared. I opened the computer grabbed the drive and tested it in a separate build and it seemed to be working as it was detected in bios. Ended up reinstalling the same drive and it was detected and I was able to start the array without any data loss. During testing that time I noticed there were issues with some containers not stopping when I was trying to stop the array. After a second restart, I uninstalled the containers causing issue and have not had any errors until today.

Seems that after the AppData Backup plugin went through the containers something happened and the drive was no longer detectable. Screenshot of syslog:

I am trying to narrow down if this is some sort of software related issue or if this is my drive/motherboard showing signs of failure. While I'm not a novice with computers, I still am pretty new at unraid and any help with troubleshooting would be appreciated.

Logs attached are from a few days after the original incident and ones from this morning.

thanks!

astronomican-diagnostics-20260409-0850.zip astronomican-diagnostics-20260420-0920.zip

NVMe device dropped offline:

Apr 20 05:34:34 Astronomican kernel: nvme nvme0: I/O tag 207 (00cf) opcode 0x1 (I/O Cmd) QID 1 timeout, aborting req_op:WRITE(1) size:16384

Apr 20 05:35:04 Astronomican kernel: nvme nvme0: I/O tag 200 (a0c8) opcode 0x1 (I/O Cmd) QID 1 timeout, reset controller

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Disabling device after reset failure: -19

This can sometimes help:

On Main, click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" 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 (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.

3 hours ago, JorgeB said:

NVMe device dropped offline:

Apr 20 05:34:34 Astronomican kernel: nvme nvme0: I/O tag 207 (00cf) opcode 0x1 (I/O Cmd) QID 1 timeout, aborting req_op:WRITE(1) size:16384

Apr 20 05:35:04 Astronomican kernel: nvme nvme0: I/O tag 200 (a0c8) opcode 0x1 (I/O Cmd) QID 1 timeout, reset controller

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Disabling device after reset failure: -19

This can sometimes help:

On Main, click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" 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 (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.

Thanks! Just added it. I'll monitor it for the time being and post if any additional issues arise.

On 4/20/2026 at 11:16 AM, JorgeB said:

NVMe device dropped offline:

Apr 20 05:34:34 Astronomican kernel: nvme nvme0: I/O tag 207 (00cf) opcode 0x1 (I/O Cmd) QID 1 timeout, aborting req_op:WRITE(1) size:16384

Apr 20 05:35:04 Astronomican kernel: nvme nvme0: I/O tag 200 (a0c8) opcode 0x1 (I/O Cmd) QID 1 timeout, reset controller

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:25 Astronomican kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Apr 20 05:36:45 Astronomican kernel: nvme nvme0: Disabling device after reset failure: -19

This can sometimes help:

On Main, click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" 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 (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.

Just as an update, I tracked it for the past two weeks and this seems to have solved the problem. Thank you for the help!

Edited May 9May 9 by Norrik343