October 20, 2025Oct 20 Hi,I am having some issues with my cache drive, as written above. I have read in some old forum post that it is recommended to disable btrfs for that, and I wanted to know if this is still recommended? I also just now started a scrub, whatever that means, which I read there as well might be helpful.Just curious if someone else has some thoughts. I am using 7.1.4 with OS basictower-diagnostics-20251020-0827.zipEdit: The scrub finished with no errors found... Edited October 20, 2025Oct 20 by poolitzer
October 20, 2025Oct 20 Community Expert Docker service appears to be running; please post a screenshot from the Docker page.
October 29, 2025Oct 29 Author Hey, thanks for the answer. Yes when I restart the server, everything is fine for a while. Which is what I did because the diagnostic just opened a white window before. Edited October 29, 2025Oct 29 by poolitzer
October 29, 2025Oct 29 Community Expert Normal syslog starts over after every boot, enable the syslog server and post that next time it happens.
January 27Jan 27 Author It finally happened again with it enabled, so here is the file syslog-previous
January 27Jan 27 Community Expert Jan 27 18:15:49 Tower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 4848096, 32 blocks, I/O Error (sct 0x3 / sc 0x71)Jan 27 18:15:49 Tower kernel: I/O error, dev nvme0n1, sector 4848096 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2Jan 27 18:15:49 Tower kernel: nvme nvme0: Abort status: 0x371Jan 27 18:15:49 Tower kernel: nvme nvme0: Abort status: 0x371Jan 27 18:15:49 Tower kernel: nvme nvme0: Abort status: 0x371Jan 27 18:15:49 Tower kernel: nvme nvme0: Abort status: 0x371Jan 27 18:15:49 Tower kernel: nvme nvme0: Abort status: 0x371Jan 27 18:19:32 Tower kernel: nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0Jan 27 18:19:32 Tower kernel: nvme nvme0: Disabling device after reset failure: -19NVMe device dropped offline, this can sometimes help with that:On Main 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=offe.g.:append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=offReboot (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.