Ruenagel Posted November 7, 2010 Share Posted November 7, 2010 Hi, I tried to update the 1.0 firmware of my f120 with the new firmware 2.0. But the drive is not recognized by the update-tool, I have tried multiple Boards and controllers.:[pouts: With Jmicron it fails, with Intel ICH9 it fails with both intel and microsoft drivers, on my i3 notebook it fails, all work with AHCI. Are there any incompatibilities with the update-tool and Win 64 bit? Have I missed something? On all controllers the drive works. But I have the problem that after reboot or hibernate the bios does not recognize the drive, I have to reboot. Thank you. Frank Link to comment Share on other sites More sharing options...
jonreeves Posted November 7, 2010 Share Posted November 7, 2010 Had this problem yesterday, someone pointed me in the direction of the solution. (as odd as it sounds) you need to remove some partitions... My SSD (F120) had 3 partitions on it (a Fat16 Recovery partition, C drive [os], D drive [data(empty)]). I used Hirens Boot CD to delete the Recovery Partition and the D drive and expand C to use the whole disk. (after I made an Acronis Image of the drive). After removing those partitions the drive was found successfully (no joke). Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 9, 2010 Corsair Employees Share Posted November 9, 2010 Or just try Parted Magic and secure erase the drive before you try and run the update that is assuming it is not the Boot drive. Link to comment Share on other sites More sharing options...
Ruenagel Posted November 10, 2010 Author Share Posted November 10, 2010 Thanks. That did it. There had been 3 or 4 Partitions on the drive. But my boot problem persists, although firmware 2.0 is now installed: Often BSOD after awake from energy save. Often disk not found by bios after awake from hibernate. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted November 11, 2010 Corsair Employees Share Posted November 11, 2010 Can you test the drive in another system? There have been several reports of OEM systems displaying that symptom from HP, Sony and a few others but the drive work in another MB or system. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.