Has anyone ever had this issue with NVMe SSDs?
“A device which does not exist was specified.”
Is this a hardware defect? The drive (PNY CS3140 1TB) is only about 5 weeks old. It seems to fix itself after a couple of reboots, but it’s very annoying. Linux doesn’t seem to have any issues with it yet.
#AskFedi #TechSupport #Windows #Windows10 #SSD #NVMe #Linux #Hardware
@fell@ma.fellr.net @techsupport@lemmy.world smart readings? e.g. Crystal Disk Info
@aliceif @techsupport I have never seen SMART report an actual problem in a useful way, and also not this time. The drive claims it’s fine.
@fell @aliceif @techsupport I find smartctl useful for confirming driver temperatures (it made me realize CPU can survive more than spinning rust). It may be also useful to determine “how worn out correctly working drive is”… but clearly your drive is broken in unexpected way.
@fell@ma.fellr.net @techsupport@lemmy.world you can read that error log with some command in the
nvmeexecutable on linux, might be a nothingburger though
I had a similar problem with an nvme and it turned out it wasn’t seated properly in its slot. It was sitting very slightly at an angle even with the screw in place. I had the same problem with it sometimes being detected at boot and sometimes not.
I’d double check it’s fully and correctly inserted into it’s slot before writing it off as defective.
@BananaTrifleViolin Good idea. The M.2 slot was left unpopulated for years before I added this drive. It’s possible that some dust got in there causing a connection issue.
I re-seated it and wiggled it around a bit to ensure any dust between the contacts got out of the way. It’s being properly recognised now, but we’ll see for how long.
Did you remember the standoff?
@Thorry84 Yes, of course.
Excellent! Just checking.
When I got an extra SSD for my system I spent an hour looking through bags of screws to find the correct standoff.
You can power it off, unplug it, remove the drive, and use a small clean and dry paint brush to ensure there is no dust in there.
Since it is happening with Windows and Linux you may be looking at a bad drive. It would make sense to RMA it.
You can use ipa if you pull the cmos battery (backup your bios settings first)
Has nobody suggested checking disk manager for which drive letter is currently assigned to your nvme along with the DVD drive (if present)? I’m used to that error bring present when Windows tries assigning the same drive letter to the wrong drive, which would also explain the reboots fixing it.
Nevermind, Linux also doesn’t like it now. I guess it’s faulty. *sigh*
I don’t think it’s fake. I got it from a local shop which I usually trust.
PNY’s own “SSD Toolbox” reports 100% SSD Life (whatever that means) and no available firmware updates. I can also “optimizate” my SSD here, which is funny.
(Lemmy users: Click the Fediverse icon to see screenshots)
@techsupportThe sdd life just checks for worn sectors.
