2 identical systems - one has duplicate id's found, other not
- Thread starter geronimobb
- Start date
Hi,
You can still report it to Linux upstream if you want to, so they can add a quirk for the device.
the fix should be part of kernels >=
6.2.16-6 and is independent of the model: https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=069e83e4621ed08c2bdb61e9b0c57958cf55491bYou can still report it to Linux upstream if you want to, so they can add a quirk for the device.
Hi,
I have 2 x Lexar NM790 4TB and I'm running proxmox with kernel 6.2.16-12-pve. Unfortunately have the same issue.
Sometimes after reboot proxmox don't see any disk (lspci does), sometimes one and sometimes 2 are visible.
I had this Lexar nvmes before fix was integrated into the kernel. I've upgraded kernel but issue still exists.
Should I reset disk settings in proxmox or reinstall proxmox in order to have the issue fix?
thanks
I have 2 x Lexar NM790 4TB and I'm running proxmox with kernel 6.2.16-12-pve. Unfortunately have the same issue.
Sometimes after reboot proxmox don't see any disk (lspci does), sometimes one and sometimes 2 are visible.
I had this Lexar nvmes before fix was integrated into the kernel. I've upgraded kernel but issue still exists.
Should I reset disk settings in proxmox or reinstall proxmox in order to have the issue fix?
thanks
Hi,
that does sound a bit different than the other issues reported here. Please check the system logs/journal. What are the exact error messages you get?
hi @fiona , i've checked logs and see
I see that there is a bug ticket for this issue https://bugzilla.kernel.org/show_bug.cgi?id=217863
does that mean that as soon as the working patch will be merged to the new kernel version it will also be available soon in proxmox?
Bash:
nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
nvme nvme1: Device not ready; aborting initialisation, CSTS=0x0I see that there is a bug ticket for this issue https://bugzilla.kernel.org/show_bug.cgi?id=217863
does that mean that as soon as the working patch will be merged to the new kernel version it will also be available soon in proxmox?
The patch submitted for stable seems to be here: https://lore.kernel.org/stable/20230920112839.812803999@linuxfoundation.org/
It's unfortunately not trivial, so it might be better to wait until it comes in via the Ubuntu kernel tree (might take a few weeks).
The issue with Lexar NM790 (2TB) could be also intermittent, it would work for few hours and than fail.
Could be linked to https://forum.proxmox.com/threads/lexar-nm790-2tb.134293/
Could be linked to https://forum.proxmox.com/threads/lexar-nm790-2tb.134293/
Last edited:
A build of kernel 6.5, which will include the fix, is planned be released for testing soon-ish (likely in the next few weeks): https://forum.proxmox.com/threads/proxmox-ve-8-0-released.129320/post-573961
EDIT: Unfortunately, as pointed out by @Instantus in the other thread, the mentioned fix is not included in the current build of 6.5 yet. The fix is in mainline 6.5.5, but the current build is based on 6.5.3. It seems that there were multiple issues and some are already addressed, but not yet that one.
Last edited:
FYI, the build is now available for testing: https://forum.proxmox.com/threads/o...-2-for-proxmox-ve-8-available-on-test.135635/
FYI, the current build of the 6.5 kernel, i.e.
proxmox-kernel-6.5.11-1-pve, finally includes a backport to fix that bug.