Now, the supplier has run some tests on the SSD, claimed it's fine, and won't respect the warranty.
I'm looking for a tool that can deep test the SSD and provide support for my claim that the SSD is faulty. Any ideas
Good thinking.The drives will keep track of things like I/O errors in their SMART data, and Windows keeps track of I/O problems in the Event Viewer logs. That's the data you'd need to establish that the drive was messing up, and should be sufficient to get a warranty claim approved. But I/O timeouts are also very commonly associated with other things too (like bad cables.) So maybe the SSD wasn't the problem.
If you replaced the boot drive in your system, you presumably reimaged or re-setup the OS, reinstalled VMWare, new drivers, etc. There are a lot of other potential issues that could have resolved.
If you just unload the parts cannon, you'll often accidentally fix problems without really knowing the root cause; that doesn't obligate vendors to subsidize the parts cannon.
That does make the drive a pretty likely culprit. I'd still be curious what, if anything, Event Viewer showed while VMWare was running w/ the old drive, though.Good thinking.
However, this was not my boot drive. I had upgraded VMware as well as the drivers and Samsung magician PRIOR to replacing the SSD trying to locate the problem. Nothing helped. Replacing the SSD (using, AFAIK, the same cable) solved this problem.
It's a phrase common in auto repair - basically means replacing a bunch of stuff that might be the problem without being sure what actually is the problem, in the hopes that the problem will go away anyway.B.T.W, English is not my first language. What does "unload the parts cannon" mean?
There is no real way he can check health of said drives except possibly crystaldisk, and even then its not 100% accurate.
There are fewer things that can go wrong with NVMe drives than with SATA drives, and fewer layers of abstraction involved. You post is impressively wrong. As long as you aren't trying to debug issues with a NVMe drive using software that's 5+ years old and hasn't been updated to support anything other than SATA, it's not going to be any harder to figure out what's wrong with a NVMe drive than to do the same with a SATA drive.The only way your going to prove something is wrong with the SSD is by trying to find something reproducable, and basically recording via video and submitting it to RMA.
This is so false..There are fewer things that can go wrong with NVMe drives than with SATA drives, and fewer layers of abstraction involved. You post is impressively wrong. As long as you aren't trying to debug issues with a NVMe drive using software that's 5+ years old and hasn't been updated to support anything other than SATA, it's not going to be any harder to figure out what's wrong with a NVMe drive than to do the same with a SATA drive.
SATA drives use a SATA link to an HBA (usually in the chipset) which then uses PCIe to communicate up to the CPU.Again, on a NVMe drive since it uses the PCI-E you have a more things that can go wrong, then a SATA which uses just the sata bus.
Any issue with PCIe is just as likely to affect the lanes going to your NVMe SSD as the lanes going to your SATA controller.A CPU will not corrupt a SATA drive, while it can corrupt a NVMe, by corrupting the PCI-E lane.
I'm not sure what you mean here. If a motherboard's firmware doesn't include NVMe support, it will simply not boot off a NVMe drive, but it won't damage the drive or any data stored on it.Motherboard BIOS's can also fubar a NVMe, which has been common in some cases, as the board needs to support m.2
This bit's rather incoherent, but I think the only real issue you're referring to can be solved by reading the motherboard manual to see which PCIe lanes are routed to which slots.There is no dubugging the board PCI-E, resitting the CPU, or FLASHING a new bios which a NVMe can be.
There is also no making sure you use the proper M.2, as if your cpu can not handle the lanes so your PCI-E slots are deactivated or run at which slots are deactivated when you run a PCI-E adapter.
I'm not seeing a difference here. If a drive doesn't work with one connector on the motherboard, you try a different one. That's just as true of NVMe as SATA. The only complication is that you might end up buying a cheap passive PCIe to M.2 riser so that you can test a NVMe drive in the slot that you know works because you usually use it for your GPU.The PCI-E lane which you are either limited to begin with, you can only debug it by moving said NVMe onto another M.2 slot or getting a PCI-E adapter for, vs a SATA which u can just move it to another port as all the ports are linked under most cases.
Most NVMe SSDs when thermally throttling are still faster than SATA SSDs, and it takes very contrived circumstances to get a NVMe SSD to overheat enough for it to shut down entirely.NVMe's are also prone to overheating vs again a SATA SSD.
960 PRO's are notorious for overheating and going thermal Throttle.
CrystalDiskMark is a shitty tool for people who want quick and dirty numbers to compare without understanding what they're doing. It's basically at the bottom of the list of software tools I'd recommend for any kind of troubleshooting. And again, it sucks equally as a troubleshooting tool for SATA and NVMe SSDs.And there is no software other then crystalmark which will give you a very big grain of salt on the condition of both SATA SSD and NVMe, because you cant test sectors like you could on a spinner, as you will eat up your writes.
|Thread starter||Similar threads||Forum||Replies||Date|
|Question Need more ways to test for a memory problem seemingly!||Memory and Storage||8|
|M||Question Testing my HGST 4TB refurbs||Memory and Storage||2|
|Question How to test new NAS Drives before using?||Memory and Storage||7|
|C||Question Testing refurb HD's||Memory and Storage||10|
|M||Question Lenovo PX4-400D drive size limit? testing with a fake drive?||Memory and Storage||2|