Lexar NM790 2TB
- Thread starter senkis
- Start date
FYI, the current build of the 6.5 kernel, i.e.
proxmox-kernel-6.5.11-1-pve, finally includes a backport of https://git.kernel.org/pub/scm/linu.../?id=6cc834ba62998c65c42d0c63499bdd35067151ecFixed daily crashes on Proxmox host with MSI PRO Z790-P WIFI and Lexar NM790 4TB SSD by updating BIOS. Original BIOS version was early 2023. Now running Linux 6.5.3-1-pve, host stable for 7 days without further modifications. Previous setup with old BIOS and kernels 6.2.16-19 or 6.5.3 experienced daily crashes.
Always good to update BIOS for stability with latest hardware.
So the good news is that with proxmox Version 8.1-1, i can confirm that the drives are now accressible without problems. Also in the intaller, which is great.
The bad news is that i see periodically this error on all systems with Lexar NM790 .. no crashed or other problems.. but quite concerning, isn't it?
The bad news is that i see periodically this error on all systems with Lexar NM790 .. no crashed or other problems.. but quite concerning, isn't it?
I don´t get this error with proxmox 8.1.3.
But in the last days I got two system freezes without any logging showing the following error on the display. I don´t know if this is a specific NM790 problem because I found similar reports for other nvme drives.
Code:
[...] device-mapper: thin: process_cell: dm_thin_find_block() failed: error = -5Updated kernel to Linux pve 6.5.11-7-pve
Removed the kernel cmd line workaround (nvme_core.default_ps_max_latency_us=0) which worked for me with an older kernel and a similar issue is back.
It takes less than a day for the issue to appear, similar to the way it was before I used the workaround with older kernel.
Removed the kernel cmd line workaround (nvme_core.default_ps_max_latency_us=0) which worked for me with an older kernel and a similar issue is back.
It takes less than a day for the issue to appear, similar to the way it was before I used the workaround with older kernel.
Last edited:
I have the same issues with 6.5.11-7-pve.
Which kernel version an workaround do you use to have a stable system?
Last edited:
I would like to try this too. I will report the result here after a few days.@fiona the workaround (nvme_core.default_ps_max_latency_us=0) seems to work for the new kernel (Linux pve 6.5.11-7-pve) too. Uptime 2.5 days
To understand it clearly, would this the correct entry in my /etc/default/grub file?
Code:
GRUB_CMDLINE_LINUX="nvme_core.default_ps_max_latency_us=0"
Same place as all other kernel parameters (on a single line in /etc/kernel/cmdline): https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_edit_kernel_cmdline