I watched a lot of Youtube videos about side by side comparison on NVMe M.2 vs SSD vs HDD. But in real-life use, I feel nothing almost. When I use my old Crucial MX100 250GB SSD, I also did the test. The result is a little bit of improvement. I run the AS SSD Benchmark testing again on the new driver. I downloaded it from the Samsung official support site.
I install the Samsung NVMe Controller instead of Microsoft one. Then I run the test on the new AS SSD Benchmark software. Later I found AS SSD Benchmark has a new version. Stornvme driver Score on AS SSD Benchmark 1.8 The test result based on AS SSD Benchmark.
It can be confirmed on the Samsung Magician software. Microsoft Standard NVM Express Controllerĭriver date: Standard NVM Express Controller
The default NVMe driver is Windows 10 builtin driver.
Loop7 7:7 0 3.I did a little bit test on my new Samsung 970 EVO Plus NVMe 250GB SSD.Īfter I installed the new Samsung SSD and migrate the system disk to it. Sector size (logical/physical): 512B/512B Nvme0n1 259:0 0 7T 0 sudo parted /dev/nvme0n1 printĮrror: /dev/nvme0n1: unrecognised disk label Loop7 7:7 0 3.7M 1 loop /snap/gnome-system-monitor/57 Loop5 7:5 0 13M 1 loop /snap/gnome-characters/139 Loop4 7:4 0 2.3M 1 loop /snap/gnome-calculator/260
dev/nvme0n1 xxxxxxxxxxxxxxx HUSMR7676BDP3Y1 1 7.68 TB / 7.68 TB 512 B + 8 B dmesg | grep -i nvme Node SN Model Namespace Usage Format FW Rev Ġ4 00000000000A Available Spare ThresholdĠE 000000000000 Media and Data Integrity ErrorsĠF 00000000003F Number of Error Information Log EntriesDISKPART Windows - Disk 1 is the SAS sudo nvme list Transfer Mode : PCIe 2.0 x4 | PCIe 3.0 x4 Mode sense (10) cdb: 5a 00 01 00 00 00 00 00 fc 00įixed format, current Sense key: Illegal Requestīad field in MODE SENSE (10) ĭ:\sg>sg_format -format -size=512 -six -v PD1īad field in MODE SENSE (6) Crystal Disk Info Windows NVMe HUSMR7676BDP3Y1 Z107 peripheral_type: disk Highest Possible Transfer Rate,PCIe 3.0 x4 Submission Queue Entry Size,"Max: 64, Min: 64"Ĭompletion Queue Entry Size,"Max: 16, Min: 16" I also contacted WD/HGST support and they said they haven't tested these SSDs with those adapters but the SSDs should work fine (they asked for photo of SSDs and S/N)ĭisk Controller,"Standard NVM Express Controller (PCI\CC_010802) Version: 3.168, 6-21-2006"ĭisk Location,"Bus Number 0, Target Id 0, LUN 0" I am accessing the drives with this m.2 nvme adapter + cable or the pcie card (I used this pcie card with many SAS nvme ssds) See below all info from all apps I tried. I thought it must be the 520b block size issue but according to info below it seems to be 512bĪll above apps give one error or another, Windows is blue screening most of the time and when it loads it shows the size of the ssd 512b and won't clean/format it. I tried every suggestion on this forum but nothing worked: sg tools, gparted, fdisk, diskpart The seller said they should work with a PCIe adapter I bought 2 cheap SAS SSDs 7.68TB HGST SN200 HUSMR7676BDP3Y1 from ebay removed from Dell EMC (has EMC P/N on them as well).
HDM didn't find the SSD in Windows (driver issue perhaps, HGST has a specific NVMe driver which I didn't have) but worked fine in linux (ubuntu live) and the command is: "hdm format -sector-size 512 -metadata-size 0 -dif-level 0 /dev/nvme0" - use nvmeo NOT nvmeon1 as it seems you need to format the controller not the namespace, everything I did and posted in this thread was with /dev/nvme0n1 and didn't solve my problems until HDM manual mentioned nvme0 (you can find what nvme0 and nvme0n1 on page 2 after run few commands in HDM) Someone suggested NVME FORMAT command in Linux which seems to have similar syntax with HDM. EDIT 22/4: I solved the problem with HGST Device Manager 3.4 but read the whole thread as you may find other suggestions if my solution doesn't work for you.