CyberMew Posted February 11, 2022 Share Posted February 11, 2022 I start getting some btrfs error. So I went to stop my docker in settings. Then I ssh in to see cache folder but it is not accessible. I still have plenty of cache space. Now I’m worried. How should I go about fixing this? It was working fine. tower-diagnostics-20220211-1141.zip Quote Link to comment
JorgeB Posted February 11, 2022 Share Posted February 11, 2022 NVMe device dropped offline: Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 493 QID 1 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 494 QID 1 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 495 QID 1 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 496 QID 1 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 497 QID 1 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 964 QID 2 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 965 QID 2 timeout, aborting Feb 10 20:55:57 Tower kernel: nvme nvme0: I/O 966 QID 2 timeout, aborting Feb 10 20:56:27 Tower kernel: nvme nvme0: I/O 493 QID 1 timeout, reset controller Feb 10 20:56:57 Tower kernel: nvme nvme0: I/O 22 QID 0 timeout, reset controller Feb 10 20:57:58 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Feb 10 20:57:58 Tower kernel: nvme nvme0: Abort status: 0x371 ### [PREVIOUS LINE REPEATED 7 TIMES] ### Feb 10 20:58:29 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Feb 10 20:58:29 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Feb 10 20:58:59 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Look for a BIOS update, the below sometimes also helps: Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference. Quote Link to comment
CyberMew Posted February 18, 2022 Author Share Posted February 18, 2022 Thank you! I just had the time to try it out. Any idea how I can start back my docker with my apps? I enabled back to Yes but the Docker vDisk location was in red... Quote Link to comment
CyberMew Posted February 18, 2022 Author Share Posted February 18, 2022 Found out about this, renamed it and it started now! Quote Link to comment
Recommended Posts
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.