SPBonzo

The SSD Toolbox now informs me that there's no update. Is this correct?

I download the 15.1 firmware which is 'installed and' then get asked to shut the system down. On power up the old 13.0 firmware is still in place so something's not working.

Is it 4250MB/s: https://www.corsair.com/ww/en/Categories/Products/Storage/M-2-SSDs/Force-Series%E2%84%A2-Gen-4-PCIe-NVMe-M-2-SSD/p/CSSD-F500GBMP600 Or is it 500MB/s: https://www.amazon.co.uk/dp/B07WS1BRX4?ref_=pe_3187911_248764861_302_E_DDE_dt_1&th=1 Or is it 2500MB/s: https://www.scan.co.uk/products/500gb-corsair-force-mp600-m2-2280-pcie-40-x4-nvme-ssd-phison-tlc-3d-nand4950mb-s-read2500mb-s-write4

I finally managed to perform a secure erase on my MP600 500GB today after some posters saying that it fixed their v13 upgrade write speed issue. The secure erase was a pain because the MP600 500GB is my OS drive. Result - it made no difference! Back to the drawing board.

I raised a support call for the exact same issue and had my MP600 500GB replaced by a unit with the same BIOS version and the same reduced write speed. It's simple - for many people the upgrade to BIOS v13 has affected write performance. You can RMA as many units as you want but this isn't the solution.

The colour scheme is dreadful. Black on blue is hard to read for many and the app comes over as rather amateurish. The main improvement outside of the appearance would be to allow firmware upgrades to drives used in storage spaces.

So are you saying that after updating the firmware to v13 on OS and data drives you're only seeing a performance drop on the system\OS partition? I have three MP600s in my system - a single drive used for the OS and two drives configured as a Storage Space (no resilience). As the SSD Toolbox is unable to update the firmware on the drives used for the Storage Space I've only being able to upgrade to v13 on my system drive and that's when the performance drop was noted. I've received a replacement drive through the RMA process but this too suffered from poor write performance despite being delivered with v11.3 on it. I'm baffled.

No - I've yet to return the original drive so this was a completely new replacement. They could have flashed 11.3 onto a drive that had been upgraded to 13 but I guess I'll never know.

Replacement RMA drive was received today and fitted. The new drive came with the 11.3 firmware but benchmarks showed that the performance was similar to the original drive which had been upgraded from 11.3 to 13 (it was this upgrade that introduced the write speed drop). I upgraded the new drive to 13 - no difference. So, in conclusion: Original drive (firmware 11.3) - Read ~ 4.5GBs\Write ~ 4GBs Original drive (firmware 13) - Read ~ 4.5GBs\Write ~ 2GBs New drive (firmware 11.3) - Read ~ 4.5GBs\Write ~ 2GBs New drive (firmware 13) - Read ~ 4.5GBs\Write ~ 2GBs I've no idea what's going on.

I'm having a drive RMA'd because of this but I'm still baffled as to why this is seen as a solution as opposed to waiting for new firmware that fixes the issue introduced in v13.

I've agreed to a RMA with Corsair so will receive the replacement drive any day now. It'll be interesting to see what firmware it comes with and what its performance figures are. Ideally, as a test it'd be good to have the previous firmware loaded and the previous high performance recorded. I will then update to the latest firmware and retest. If the same drop in performance is noted it'll be interesting to see what Corsair's response is as I've noticed that the same firmware is being used by NVMe products provided by other companies.

My write speeds were nearly double yours before that last firmware update so not sure what your point is.

Corsair have asked me to RMA the drive. Their approach is for me to send me drive to them whilst I wait 2 weeks for a replacement - no chance. That would leave me without a PC. Quite why they can't fix the issue with new firmware is beyond me. After all, it was a firmware update that affected the drive's performance.

I use ATTO for my benchmarking and write speeds have definitely halved since updating to 13. Case open with Corsair so let's see what comes of it.

The Get-PhysicalDisk Powershell command correctly identifies and lists all three NVMe drives even though two of them are configure as a Storage Space. Device Manager does the same. Why can't the SSD Toolbox identify the drives at the same physical level and allow firmware updates?