December 27, 20241 yr I built my machine in november, and I am now in a state where everything almost works. Unfortunately I have a bog problem, sometimes something happens that makes my docker containers crash. I try to reboot remotely, but the webUI just goes down, the machine doesn't reboot. I can see the array gets stopped but the reboot won't go through. I have to power cycle the machine when in happens. Last time it happened, I pulled the syslog, and thought it was something with my SSD, i red some won't play well with ASPM, so I deactivated l1_aspm for my NMVe, but it happened again today, unfortunately, the syslog previous is not populated this time. I added my diagnostics from last time, maybe someone can help me, this is really frustrating. nos-diagnostics-20241221-2207 2.zip
December 27, 20241 yr Community Expert There appears to be an issue with the pool NVMe device, previous sylsog is filled with these: Dec 21 11:24:28 NOS kernel: critical target error, dev nvme0n1, sector 1498613520 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:29 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 705245792, 131072 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:29 NOS kernel: critical target error, dev nvme0n1, sector 705245792 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:29 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 752697448, 131072 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:29 NOS kernel: critical target error, dev nvme0n1, sector 752697448 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 612204768, 152 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:49 NOS kernel: critical target error, dev nvme0n1, sector 612204768 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 394372432, 128 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:49 NOS kernel: critical target error, dev nvme0n1, sector 394372432 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 4152
December 27, 20241 yr Author 1 minute ago, JorgeB said: There appears to be an issue with the pool NVMe device, previous sylsog is filled with these: Dec 21 11:24:28 NOS kernel: critical target error, dev nvme0n1, sector 1498613520 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:29 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 705245792, 131072 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:29 NOS kernel: critical target error, dev nvme0n1, sector 705245792 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:29 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 752697448, 131072 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:29 NOS kernel: critical target error, dev nvme0n1, sector 752697448 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 612204768, 152 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:49 NOS kernel: critical target error, dev nvme0n1, sector 612204768 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 394372432, 128 blocks, I/O Error (sct 0x0 / sc 0x80) MORE Dec 21 11:24:49 NOS kernel: critical target error, dev nvme0n1, sector 394372432 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 21 11:24:49 NOS kernel: nvme0n1: I/O Cmd(0x9) @ LBA 4152 Anything you can recommend? Should I replace the drive? I have a cheap PCIe x1 to M.2 adapter to connect the drive, but figured it can't really be a problem, as there's no logic in the board, it's just a connector.
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.