@Fernando Tyvm buddy…
i just go to device manager, right click update driver ide/atapi control then browser to local folder.
after that rebooted PC go to device manager - storage controllers - standard nvme then force have disk to mod+signed OFA NVMe.
will try Samsung NVMe driver v3.3.0.1910 later then, thanks again for help…
Correction by Fernando: Meanwhile I have corrected the exact version of the driver within my source post. I meant the recently released Samsung NVMe driver v3.3.0.2003
My M.2 PCie OS drive is showing itself as “Ejectable” under “Safely Remove Hardware.”
I just found your forum. I updated my MS NVMe Storage Controller from the OEM Windows 10 to your OFA. (Win10 64 1909.) Am running a WD Blue M.2 PCie.
The M.2 used to be Drive 0. Then I tried making a mirror of two HD’s. (By accident I ended up making a spanned set instead.) After that, Windows moved the M.2 to Drive 4.
So I disabled all the drives in the BIOS (EUFI) except for the M.2 boot drive. That moved the M.2 back to Drive 0. But now I always have a “Safely Remove” icon in the Notification area of m Taskbar.
I assume this is, in part, why Windows doesn’t like to hibernate with the OFA driver? (Because Windows kind of thinks that the OS drive is not internal?)
@pmikp :
Welcome to the Win-RAID Forum!
The presence of the "Safely Remove" icon for the NVMe SSD seems to be a bug of the OFA driver, but this has never been a problem for me.
If you want to avoid this annoying icon, but get the best possible performance with your NVMe SSD, I recommend to replace the mod+signed OFA NVMe driver by the latest Samsung NVMe driver v3.3.0.2003 WHQL.
According to my experience with different non-Samsung NVMe SSDs the Samsung driver works extremely good with all of them, although the HardwareIDs of the driver do not match the ones of the in-use NVMe Controller.
This is what you should do:
1. Set a restore point.
2. Update the driver of the NVMe Controller. You have to force the installation by using the "Have Disk" option.
3. Disregard the warning, that the driver may not support the target device.
4. Enjoy the performance of your NVMe SSD, which will be much better than by using the generic Win10 in-box MS NVMe driver.
Regards
Dieter (alias Fernando)
Danke sehr for the quick reply.
Sorry to have wasted your time with a known “bug.”
I saw your tests with the Samsung driver, but I wasn’t sure that it would play with a non-Samsung NVMe. (Just now I see that you said it would on your drive page. But I didn’t even bother reading anything about the Samsung driver, because I didn’t think it would play with my WD.)
I will plan to try it… later. (I am currently attempting to recover files from my failed attempt at mirroring drives. And I foolishly deleted my only backup of that drive thinking I could make a new one of the spanned volume.)
Update of the start post
Changelog:
Update of the start post
Changelog:
Here are my results with the MS driver and the 3 Samsung ones: 2.0.8.1611 mod, 3.3.0.2003 mod, 3.3.0.2003 pure:
MS
2.0.8.1611 mod
3.3.0.2003 mod
3.3.0.2003 pure
Basically all the 3 Samsung drivers are the same, and the default MS one is inferior in writes for the 4K parts.
And just ignore the higher 4K QD4 in the 3.3.0.2003 pure read test, it happened only then, a fluke…
sorry how to download nvme drivers please?
@tasosko :
Welcome to the Win-RAID Form!
By doing a double-click onto the related download link. You can find the links within the first 2 posts of >this< thread.
Regards
Dieter (alias Fernando)
Hello, a search has brought me to this great article, may be someone has an idea how I fix my issue. Coincidently after installing a new GraphicCard (I assume has nothing to do with the problem, other than triggering a major driver update) my 2 Sabrent Rocket 4.0 now perform really bad (below 3%tile bad) in small file performance - large sequential files are still fast. My Older Samsung 960Pro still performes blasingly fast. I assume the Sabrent drives somehow switched to a slow driver - but how do I identify what driver they are running on given the Samsung Driver does reside on my system happily to support the 960Pro ? Attached the StorageController section from Device manager on whats shown there. Thanks ahead of time to anyone who can help.
Cheers
@verandy :
Welcome to the Win-RAID Forum!
If you want to know, which NVMe driver the NVMe Controllers of your Samsung SSD and your AMD RAID array are using, you have to do a right click onto the related devices, which are listed within the "Storage Controllers" section of the Device Manager, and choose the options "Properties" > "Driver" (> "Driver Details").
Contrary to you I suspect, that the insertion of the discrete graphics card has something to do with the performance of your NVMe SSDs (not enough bandwidth due to less available PCIe lanes?).
Please give us some additional information about your system (mainboard, chipset, CPU).
Happy Easter!
Dieter (alias Fernando)
Hi,
Thanks for the fast response - some quick info on the system: Ryzen 3900X on Gigabyte Xtreme X570 with 16GB Memory
The lane Bandwith should not be the problem - both Rockets are direct to CPU - one in primary M2 one on extension card in PCIE Slot 2 - the way the bord is documented that should drive the primary slot for the GPU to 8X - the secondary also to 8X with only 4X used by the Rocket and finally the M2A having its own 4x lanes - the now much faster Samsung is in M2B Slot which is supported by the Chipset and hence should be the slow one.
The problem with identifying drivers is that only the Smasung shows as an NVMe storage controller, the others show as AMD-RAID Bottom Device and AMD-RAID Controller (storport) - however RAID has never been enabled in BIOS - not for SATA and not for NVME - another strange thing is that in HWINFO the Samsung shows as NVME with a green Checkmark the rockets show as "ATA AMD-RAID Sabrent Rocket 4 " without checkmark.
Something strange has happened here - I can not specifically pin down when it first appeared like this since it was the new Graphics Card triggering running benchmark - system as such behaved normally under light load use the last 2 weeks. But 3 weeks ago on the same set-up (other than GPU) the Rockets had a Userbenchscore setting a new 100%tile and now they are more or less on SATA level other than sequential write is far beyond max SATA bandwith. Somewhat lost what to try.
Cheers & also Happy Easter & Stay Healthy
EDIT:
PS: another strange symptom is that I can not activate Write Cache for the Rockets, while it works fine for the Samsung
All good now - I just forced the recomended Samsung Driver on the Rockets (and the today newly installed 905P 380 GB - which also configured first as an AMD - RAID even though in BIOS it is not even shown under NVMe Drives burt has its own storage class section) - full performance on all drives now - HWInfo also shows the drives as they should be - still no idea why Windows installed these crippling drivers - if it happens again I know where to look. Thanks a lot for this thread here, spared many frustrating days ! Pictures attached
Cheers
@verandy :
Thanks for your report. It is fine, that you were able to solve the performance problems of your Sabrent Rocket 4.0 SSDs.
Since I doubt, that the Windows Update had replaced by its own the MS in-box NVMe driver by the AMD RAID ones, I suspect, that it was you yourself, who installed the AMD RAID drivers by an oversight.
Additional questions:
1. Which specific Samsung NVMe driver did you install for the NVMe Controllers of the Sabrent SSDs and how did you install it?
2. Do you use the Sabrent Rocket Control Panel? If yes, can you search for an update of the Firmware and the Control Panel software?
Happy Easter as well!
Dieter
Hi,
As two the strange install: even the new Optane 905p autoinstalled in windows with the AMD RAID driver without any contribution from my side. So no idea how, but not an active oversight.
I used the Samsung driver linked to in the thread in the Win 10 64bit version.
I have not installed the Rocket toolbox since I am not sure it is intended for the NVMe drives but rather for some of their other storage solutions. I did not find new firmware on their site - but since the optane drive installed the same funny AMD drivers, I rather assume it is something strange the way Gigabyte shows the drives to windows and not a firmware issue of the drives. The Samsung also did need an active install of the right driver but that was more straight forward since Samsung has an Exe install file for download. BTW the board has the latest BIOS and chipset drivers already before the issue first happened.
@verandy :
Since I have a very similar system with an X570 chipset and a 1 TB Sabrent Rocket 4.0 as system drive, I am wondering how you got the AMD RAID drivers installed.
Which version and as original or mod+signed driver?
The Sabrent Rocket Control Panel (Toolbox) is very useful for me, because it can monitor the health of the SSD (Temperature etc.) and gives to option to search for a Firmware Update.
Here is a picture can be enlarged by clicking onto it):
By the way: Have you already done a look into the start post of this thread? There you can see the benchmark results I got with the 1 TB Sabrent Rocket 4.0.
@Fernando
Thanks for the extra Follow-Up - I used the driver 3.3.0.2003 - I think its the unmodified - at least the linked page I downloaded it from did not say anything about modified (I remember having seen that from a link much further up in the thread, the one I used though is from the link just couple pages prior to this).
I now downloaded the toolbox and could confirm Firmware is current - I think though I would not trust it to upgrade firmware since it identifies my Optane totally wrong with wrong size and wrong drive letters and displays my Storage Space HD 12TB set-up (used as NAS Back-up space) as a Sabrent Rocket 4.0 - who knows what that tool would try to flash. I assume the tool would do just fine in a clean Sabrent Only environment, but mixed hardware does seem to stress it out somewhat.
I did read the post originally from the beginning but not with an eye on the detailed results, more to find hints towards my original issue - I then went for the Samsung drivers based on the conclusions section that it was a driver with amoung the best performance and no hick-ups after installing it - which I can confirm, works like a charm, even on the Optane 905p drive.
Even though I might gain a couple extra percent trying some of the other drivers, I am not trying to test my luck and instead enjoy the stable fast system I now have again.
Cheers, Andreas
@verandy :
Thanks for your answers. What is the purpose of using an Intel Optane SSD with an AMD chipset mainboard?
Please post a screenshot of the Devece Manager, which shows the content of the "Storage Controllers" section.
@fernando
Hi, the Optane 905P is not the hybrid acceleration version for Intel Only - it is an Optane based NVME SSD which is available as 380 (M2 form) 480 (U2 Form) and 960 (PCIE Slot form factor) - I had a great opportunity to get one at a reasonable price from a system pull. The benefit is extremly fast small file random R/W also at low que depth (good but not amazing in sequential large files - here Rocket 4 is clearly better) and the response I am seeing in the 24 hours using it is just great - its like launching every application from a huge Ram disk - is it worth the 3x normal SSD price (or 6X without a good buy opportunity) - likely not, its more the fun of a really responsive system. To my own surprise (and initial shock) the X570 xtreme seems to be optimized to take it on. When I inserted it in the M2A slot the slot came up empty in BIOS (and it still does) - however a complete new section appeared in the BIOS showing all the Optane Drives Characteristics and only with CSM enabled it then also came up as a configurable boot drive. None of that is documented in the Gigabyte manual - hence my initial shock to have M2A showing empty just after physically installing an expensive SSD in it.
Attached the storage controller section - now shows 4 Samsung (2 Rockets, one Samsung, One Optane):
Attached a CrystalDiskMark comparison (Rocket completely empty - just wiped after moving Windows to Optane) - it does not tell the full story since the extremely low latency giving the snappy instant performance is not fully reflected by this.
Use Case ? I intend to use the Optane as System and Program drive where the strength of small file access and low latency fully shines and the Rockets for about anything else with large data files.
