this post was submitted on 07 Oct 2023
7 points (100.0% liked)
Linux Questions
1149 readers
3 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Your nvme drives don't support providing proper device UUIDs instead it results in "0" which of course is the same on both. The actual fix is for your vendor to get their shit together which might mean updating to a new firmware version IF there is a fix. The next best thing would be for the kernel devs to specifically work around your broken model. Such workarounds will appear in new versions of kernels and may not be ported to older versions. See this thread on kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=216049
If you are feeling very adventurous its possible to do this fix yourself in a kernel you build. It mostly entails figuring out how to build and install the kernel and pasting some text not learning c
https://unix.stackexchange.com/questions/711739/globally-duplicate-ids-for-nsid