I am attempting to fix an error I woke to this morning. My server will not launch docker or any vms but the array is still on and accessible. I ran fix common problems and got the following errors -

Unable to write to cache

Unable to write to Docker Image

The drive mentioned in the error is not full 316 used, 682 free. This leads me to believe it could have more to do with the docker image being full or corrupted.

I will attach logs ( I think I did that right) and any guidance would be greatly appreciated.

skynetserver-syslog-20260625-1740.zip

Attach Diagnostics ZIP to your NEXT post in this thread.

Here is the correct attachment. Apologies.skynetserver-diagnostics-20260625-1401.zip

Not getting a SMART report for cache (nvme0). Try reseating it.

NVMe dropped offline:

Jun 25 08:53:46 SkynetServer kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Jun 25 08:53:46 SkynetServer kernel: nvme0n1: I/O Cmd(0x2) @ LBA 281250976, 120 blocks, I/O Error (sct 0x3 / sc 0x71)

Jun 25 08:53:46 SkynetServer kernel: I/O error, dev nvme0n1, sector 281250976 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 2

Jun 25 08:53:46 SkynetServer kernel: nvme0n1: I/O Cmd(0x2) @ LBA 18589536, 128 blocks, I/O Error (sct 0x3 / sc 0x71)

Jun 25 08:53:46 SkynetServer kernel: I/O error, dev nvme0n1, sector 18589536 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2

Jun 25 08:53:46 SkynetServer kernel: nvme nvme0: Abort status: 0x371

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

Jun 25 08:54:06 SkynetServer kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Jun 25 08:54:06 SkynetServer kernel: nvme nvme0: Disabling device after reset failure: -19

Try this: 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.

7 hours ago, JorgeB said:

NVMe dropped offline:

Jun 25 08:53:46 SkynetServer kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Jun 25 08:53:46 SkynetServer kernel: nvme0n1: I/O Cmd(0x2) @ LBA 281250976, 120 blocks, I/O Error (sct 0x3 / sc 0x71)

Jun 25 08:53:46 SkynetServer kernel: I/O error, dev nvme0n1, sector 281250976 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 2

Jun 25 08:53:46 SkynetServer kernel: nvme0n1: I/O Cmd(0x2) @ LBA 18589536, 128 blocks, I/O Error (sct 0x3 / sc 0x71)

Jun 25 08:53:46 SkynetServer kernel: I/O error, dev nvme0n1, sector 18589536 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2

Jun 25 08:53:46 SkynetServer kernel: nvme nvme0: Abort status: 0x371

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

Jun 25 08:54:06 SkynetServer kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Jun 25 08:54:06 SkynetServer kernel: nvme nvme0: Disabling device after reset failure: -19

Try this: 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.

Ok, I did this before the unseating suggested in the comment before, and it worked, my docker started and so did my vm. Attaching the log. Thank you!

skynetserver-diagnostics-20260626-0913.zip

Keep monitoring to see if it doesn't drop again in the future.

1 hour ago, JorgeB said:

Keep monitoring to see if it doesn't drop again in the future.

Appreciate the help, you are a lifesaver.