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
#AskFedi #TechSupport #Windows #Windows10 #SSD #NVMe #Linux #Hardware
@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.
@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.
@fell @techsupport @aliceif Fun. I'd assume that crcs are now cheap enough that bad connection should not corrupt data, but clearly not so.
@techsupport Turns out Lemmy doesn't support images in comments. If you're on Lemmy, click the Fediverse icon for screenshots.
@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@aliceif @techsupport It's just always the same entry saying something like "command completed successfully"