March 29, 20251 yr I had a power outage the other day and when the power came back, the server didn't recognize the USB. So I reinstalled the USB and replaced the default config folder with the folder that was prior on the USB. The issue keeps occurring, this is what I've tried: Deleted docker image and reinstalled the containers Increased the docker image size, deleted the docker image and reinstalled the containers Added "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" in syslinux.cfg after "append initrd=/bzroot" under the Unraid OS label. I did chkdsk on the USB on windows and it reported no errors. Is the usb corrupted? The errors will be in the syslog-previous diagnostics-20250329-1854.zip
March 30, 20251 yr Community Expert According to the diags, the Docker service is running, post a screenshot from the Settings - Docker page.
March 30, 20251 yr Author Yes, I restart the server to get it to work again. Eventually it'll crash. Another thing I just did the "restore config" in Back up and Restore. hoping it meant for the flash Edited March 30, 20251 yr by MrTing
March 31, 20251 yr Community Expert 17 hours ago, MrTing said: Yes, I restart the server to get it to work again. Syslog starts over after every boot, so next time you need to grab the diags before rebooting.
March 31, 20251 yr Author The syslog before rebooting is there. In the logs folder, it's named syslog-previous.txt
March 31, 20251 yr Community Expert On 3/30/2025 at 10:26 AM, MrTing said: Another thing I just did the "restore config" in Back up and Restore Where do you see this "Back up and Restore"?
March 31, 20251 yr Community Expert 23 minutes ago, MrTing said: The syslog before rebooting is there Missed that, since originally, I thought the diags were before rebooting, the problem is the NVMe device, it's dropping offline: Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 669786296, 16 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 669786296 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 776435768, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 776435768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 772237136, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 772237136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 793730632, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 793730632 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 752344568, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 752344568 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002) Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Disabling device after reset failure: -19 Try adding "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" as a kernel boot option, after /bzroot
March 31, 20251 yr Author With the Appdata Backup plugin. There is an option to backup the flash drive, so I thought maybe the option to restore the config was referring to the config folder in the usb
March 31, 20251 yr Author 2 minutes ago, JorgeB said: Missed that, since originally, I thought the diags were before rebooting, the problem is the NVMe device, it's dropping offline: Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 669786296, 16 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 669786296 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 776435768, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 776435768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 772237136, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 772237136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 793730632, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 793730632 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme0n1: I/O Cmd(0x2) @ LBA 752344568, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 29 18:26:57 MANISHCLOUD kernel: I/O error, dev nvme0n1, sector 752344568 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 29 18:26:57 MANISHCLOUD kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002) Mar 29 18:26:57 MANISHCLOUD kernel: nvme nvme0: Disabling device after reset failure: -19 Try adding "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" as a kernel boot option, after /bzroot This is what I've already inputed, is this correct?
March 31, 20251 yr Community Expert 13 minutes ago, MrTing said: This is what I've already inputed, is this correct? Yep, if that doesn't help recommend trying a different brand/model NVMe device, or a different board.
March 31, 20251 yr Author I remember this happened a long time ago, which I changed my NVMe. It usually crashed when the mover moves, so I'll to try again when I download a lot of stuff. After restoring the config from last week's backup, it hasn't happened yet though.
April 6, 20251 yr Author So it crashed for the first time again since my last message. My docker image is set to 30gb, and I added up the total of what I have, and it is now 31gb, which would explain the crash. Here are the sizes of my images. Seems like torrent/usenet clients and the ARRs are taking the most. Is it the logs or something? I think I remember there being something that I can add to reduce the docker image increasing so much. This may not be the issue though as before I had the docker image size to 50gb, so we shall see. Edited April 6, 20251 yr by MrTing
April 7, 20251 yr Community Expert If the docker image keeps growing, there's usually a wrong mapping somewhere, check all container mappings.
April 8, 20251 yr Author Ok turn its out it wasn't growing. BUT, I read this forum, and turns out I also had a Samsung cache drive in the second M.2 slot. Both of the slots are rated at the same speed so I thought it didn't matter, but I didn't even consider the CPU vs Chipset connection being an issue. This HAS to be the issue (I pray).
April 8, 20251 yr Author Turns out it was a Western Digital pcie Gen 4 drive 😅. Couldn't find an obvious firmware page for it, but I'm hoping the switcharoo worked. I'll report back in a month. ty for all yall help!
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.