Search results

Update: The 5.2.9 Linux kernel release has the fix.

Also, if going through all this upsets you (as it should!), you may want to consider complaining to ADATA as well. See the comment @Yury posted above. He mentions a specific case number you'd want to reference with them. This doesn't solve the problem in the short term, but hopefully gets them...

For the nvme command, you need to install the nvme-cli package. In Debian, at least, it's called nvme-cli. Not sure about other distributions. If it's apt-based, try "apt search nvme", if it's yum-based, try "yum search nvme" As far as adding quirks, they're in this file in the Linux kernel...

That's the same as mine, so 5.3-rc2 (and onward) kernel currently has the patch, and maybe a later 5.2 kernel (after 5.2.6) will have it.

I don't know anything about Proxmox, but I do know that the 5.3-rc2 kernel has the patch you are looking for. If you can build the 5.3-rc2 kernel, you'll be all good. Sorry I don't have more info for you. EDIT: Though, if these drives have a different device ID vs the SX6000LNP, this patch...

Looks like there's a resource on this: wiki(DOT)unraid(DOT)net/Building_a_custom_kernel I'll send them (ADATA) an email later, too. I'm not sure if it's on Realtek or ADATA, but crappy firmware from Realtek is no surprise :( And, since I got these SSDs as part of my laptop through Lenovo, I'll...

Ah. Well, fortunately it's easy to patch. If you find others, feel free to adapt my patch. `lspci -nn` will let you see the vendor ID and device ID. Just add another entry to the quirks table if it's the same duplicate subnqn issue. Do you know if anyone's brought up the issue with ADATA? I'd...

I see that you're the one other person on the whole Internet who's run into this problem with this particular SSD. I just ran into it the other day with my new Thinkpad laptop. I've made a patch for this that should be going out in the Linux 5.3 kernel. It's a problem with the firmware, but...