Alex_UK Posted October 12, 2013 Share Posted October 12, 2013 Hi, First a quick overview I have a GT 240GB drive (which is configured as my main system drive). Last year I used the Firmware Update tool to successful update the firmware to version 5.03 with no problems. This time around, I decided to use the Corsair SSD toolbox to update the firmware to 5.05. The firmware downloaded correctly, but at the end of the firmware update process the Toolbox stated that an error had occurred and that it could not update the firmware. No error code was produced – so I am none the wiser about what happened! As a precaution, I had backed everything up beforehand, and expecting the worst I rebooted the system. You can imagine my surprise when the system booted up correctly (with no warnings) and the toolbox reported that the SSD was now at 5.05. To test, I ran the Trim command via toolbox – no problem reported and I checked the version of the SDD firmware via Intel’s RST + other disk info programs => all reported back 5.05. Corsair’s Toolbox reports that the firmware is up-to-date and no further action is required. Although I can access the drive via the Corsair's SSD toolbox, however, when I tried to access the SSD via the Corsair’s Firmware update tool (v1.1), the drive is no longer visible! I haven’t experienced any instability (yet), it’s only been a couple of hours, but I would like to know (if possible) what has happened and if trouble is ahead. My Questions at this stage Has anyone experienced this behaviour before? Do I have a problem?Has the SDD been updated successfully? Is there a way I can really confirm what the system reports is correct and that there is no firmware corruption?If I’m unsure, is there a way I can reapply the firmware update again without destroying the SDD’s contents?Also, should Corsair’s firmware update tool report back that the drive is at 5.05 and does anyone know why it does not show the SDD drive anymore? Thanks in advance, Alex Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.