Talk:Solid state drive/NVMe

From ArchWiki

Add the reason/link as to why discard is not recommended for NVMe SSDs?

The note merely states it shouldn't be done, but there is no reason or link to the source that supports the statement provided. Soukyuu (talk) 21:54, 12 February 2016 (UTC)

I would like to add that the explanation is unclear for another reason. The statement says,

Warning: Although continuous TRIM is an option (albeit not recommended) for SSDs, NVMe devices should not be issued discards.

This is confusing. Are we talking about continuous TRIM or TRIM tout court? This statement is conflating the two concepts. Moreover, this point isn't at all mentioned on the main Solid state drive wiki page. There, readers are first admonished to check whether their SSD supports TRIM/discard. Readers are then instructed on how to set up periodic TRIM. And finally, they're discouraged from using continuous TRIM.

This presents two problems. First, I feel readers should at least be warned about TRIM on NVMes on the main SSD wiki. Second - and more pertinent to this talking point - it's still unclear to me whether it's safe for NVMes to have periodic TRIM enabled or not.

Pound Hash (talk) 23:40, 22 December 2021 (UTC)

"GRUB does not support booting from /boot partitions that reside on NVMe drives, see FS#47447"

This is not true. I ran into an issue in this regard and fixed it somehow (I'm booting from /boot on NVMe at this moment). Can't remember how I fixed this. Will post back if I figure it out. Greyltc (talk) 16:28, 3 March 2016 (UTC)

Link to Intel-website does not work

The link is dead. There is a page: that is targeted towards developers. But I don't know it it's applicable to this article. The Wiki states that discard is not recommended on Nvme drives, but there is no information why. —This unsigned comment is by Dockland (talk) 11:17, 16 July 2016‎ . Please sign your posts with ~~~~!

NVME power saving patch v.2

The patchset which allows NVME devices to go to lower resting/idle power state has been introduced and on its way into mainline —This unsigned comment is by Frank604 (talk) 19:49, 3 September 2016‎. Please sign your posts with ~~~~!

On 4.13.11-1, I was getting ext4 fs errors that would cause the system to become unusable. I found a similar issue here and was able to successfully sidestep the issue by using the kernel parameter nvme_core.default_ps_max_latency_us=0 to disable power saving on NVMe. Should this become part of the Wiki? Maybelline (talk) 19:42, 7 November 2017 (UTC)

Makes sense - although it would be better to recommend setting nvme_core.default_ps_max_latency_us=5500 as the OP on that stackoverflow thread reported that this was enough to fix the problem. That still allows idle power consumption to be 0.07W instead of 3.10W, so it would be a pity if people unecessarily disabled that state. It looks like its only the deepest state that causes the problem. Perhaps also mention that it might be specific to Dell XPS 9550 (Is that the laptop you're using?) 21:54, 8 November 2017 (UTC)

No, I'm on an Intel NUC (6, I think?) with an Intel 500GB NVMe SSD. I will try changing the parameter to 5500 and see if it is still stable, and then update the Wiki according to my results. Maybelline (talk) 22:15, 8 November 2017 (UTC)