Has anyone ever had this issue with NVMe SSDs? (ma.fellr.net)

submitted 3 months ago* (last edited 3 months ago) by fell@ma.fellr.net to c/techsupport@lemmy.world

17 comments fedilink hide all child comments

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.

Update: Solved by re-seating the drive in the slot: https://ma.fellr.net/users/fell/statuses/113883457441026891

@techsupport

#AskFedi #TechSupport #Windows #Windows10 #SSD #NVMe #Linux #Hardware

top 17 comments

sorted by: hot top controversial new old

[-] dhtseany@lemmy.ml 5 points 3 months ago

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.

[-] Vinny_93@lemmy.world 1 points 3 months ago

Could be an issue with the PCIe drivers (i.e. chipset driver). If the drive goes into gone mode, check device management to see if the drive shows up at all. If it does, open disk management to see if the partitions initialise at all.

If your drive is detected, go to device management to see which PCI subsystem it's connected to by selecting it and then go to View - devices by connection.

If it is detected, you can also check its values with something like CrystalDisk to see if something is wrong.

Lastly, if you have another NVMe drive lying about (long shot, I know), chuck it in the same port as the failing one and reboot a couple of times to see if something breaks.

To sum up: it's either the drive or the PCI interpretation layer in Windows. Eliminate to find the cause, then fix that. Since it works fine in Linux I think you can rule out hardware issue.

[-] fell@ma.fellr.net 1 points 3 months ago* (last edited 3 months ago)

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)
@techsupport

[-] altima_neo@lemmy.zip 3 points 3 months ago

The sdd life just checks for worn sectors.

[-] Leah96xxx 1 points 3 months ago

Nope, but I currently have that issues with a SATA SSD

[-] mojofrododojo@lemmy.world 1 points 3 months ago

I always worry about fakes in the supply chain.

[-] fell@ma.fellr.net 2 points 3 months ago* (last edited 3 months ago)

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.

(Lemmy users: Click the Fediverse icon to see a screenshot)

[-] mojofrododojo@lemmy.world 1 points 3 months ago* (last edited 3 months ago)

good luck. sounds like a bad unit. local is great for returns :D

[-] aliceif@mkultra.x27.one 1 points 3 months ago

@fell@ma.fellr.net @techsupport@lemmy.world smart readings? e.g. Crystal Disk Info

[-] fell@ma.fellr.net 1 points 3 months ago

@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.

[-] pavel@social.kernel.org 2 points 3 months ago

@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 1 points 3 months ago

@pavel @techsupport @aliceif It wasn't lying. Turns out the drive was fine, actually! It seems like the problem was caused by a dusty M.2 slot.

[-] pavel@social.kernel.org 1 points 3 months ago

@fell @techsupport @aliceif Fun. I'd assume that crcs are now cheap enough that bad connection should not corrupt data, but clearly not so.

[-] fell@ma.fellr.net 1 points 3 months ago

@techsupport Turns out Lemmy doesn't support images in comments. If you're on Lemmy, click the Fediverse icon for screenshots.

[-] aliceif@mkultra.x27.one 1 points 3 months ago

@fell@ma.fellr.net @techsupport@lemmy.world you can read that error log with some command in the nvme executable on linux, might be a nothingburger though