Samsung 960 EVO Internal NVMe Solid State Drive, 250 GB

2017-05-26T20:00:00

I've been using the 840 series for a while and recently upgraded to the 960, the speed is amazing almost incredible.

danielocdh

Originally posted at

2017-04-17T20:00:00

I have this for almost nearly 3 months now. Blazing and unprecedented performance on the previous laptop that I'm using which is Lenovo T460s. Afterwards new laptop come (Lenovo T470p) which is 3 days ago and I decided to use the same NVme (Samsung evo 960 m.2 1tb) after clean installation of OS Windows 10 Pro and downloaded the recent driver from microsoft and lenovo website as well as samsung recent firwmware. After completely switch-off the device then I turn-on again I was surprise the same day that it stuck on Lenovo logo (Please see screenshot attached) and it didn't load the OS at all. When I forcefully rebooted it goes to the normal state then OS loaded properly. Issue is keeps on happening everynow and then, a bit alarming I believe.

BCdP

Originally posted at

2017-03-24T20:00:00

it is an amazing ssd and i recommend it to any one need his pc to speed up :)

samgm

Originally posted at

2017-01-21T19:00:00

First and foremost, this drive is fast with near-advertised speeds (see story below for more details). The response time and consistency has been exceptional, and my cold boot time on Windows 10 after enabling several MSI boot optimizations is now 2 seconds flat. Still amazes me several weeks later. Truthfully, I went through many hoops to get this SSD working with my motherboard (MSI Z97-GD65). However, this was due to my motherboard not having an m.2 port (it has mSata which is significantly different) and was my fault for not verifying this before my purchase. MSI was very gracious however, as about a year or so prior they released an update to their BIOS which added support for m.2 drives - perfect! I ordered an m.2 -> PCI-E x4 adapter, updated the BIOS using a spare USB drive, and installed my new hardware. Initially, the drive was successfully detected by Windows 10 (I had to right-click on the start menu and then initialize the drive via Disk Management). My goal however was to migrate Windows over to this SSD to get off my 1TB HDD RAID setup. I went to a free faithful tool of mine - Clonezilla. After installing the latest stable to a USB stick and booting off the stick, I eventually reached an unrecognized error during the process. Disappointed but not discouraged, I read on a forum post that the dev builds of Clonezilla were on a newer version of Linux with better drive technology support. So I gave it a shot and they were right! Migration took about an hour for 500GBs of written data, and I've been a happy camper since. The m.2 adapter causes a slight loss in performance yielding 85% of advertised read (~2700MB/s), yet still 100% of advertised write (~1800MB/s). I bought this drive for the performance, endurance and future-proofing. I expect this SSD to remain my main drive after building a new desktop a few years down the road. The performance is insane, taking my rapid loads from a dedicated SATA3 SSD for games to an entirely new level. For anyone still reading, my recommendations are to ensure your computer is compatible with m.2 (at PCI-E x4 speeds), that you are okay with your main GPU lane dropping to PCI-E x8 (MAYBE dropped 1-2 fps for me with my GTX 1080 and dual monitors), and that there's plenty of ventilation around the SSD to ensure that top speeds are consistent during huge data transfers.

LarkSS

Originally posted at

2017-01-17T19:00:00

I got a shiny new Supermicro 5018D-FN4T to put this drive into, as a virtualization server. If it worked, it was going to run like a greased pig at the state fair. Unfortunately, the Supermicro BIOS didn't recognize it so I couldn't install onto it. And Centos 7.3 didn't recognize it either, despite being a Linux 3.10.0 kernel (and NVMe drivers being baked into Linux since 3.3). Oddly, when I booted Fedora 25 (Linux 4.8) it saw the drive, which I was able to partition, format, copy files to, etc. So I ended up having to exchange it for a slightly slower, slightly more expensive T*a product instead.

PowerLinuxUser

Originally posted at