2 days ago, I labelled my Corsair F60 to be a decent all around drive.
Now, that status went down to a well below average (to put it to user friendly terms) drive.
After a month of working well with my new laptop and an engaging multiplayer on Crysis II 2 days ago, it magically couldn't be detected by the BIOS. I have another HDD, a 750GB 7200RPM Seagate Momentus that is still detected on port 2 of the SATA. So, to put it this way, I can't start my OS and just sits there at POST. It currently has firmware 2.0 FYI.![]()
I had a quick research, and this is quite a recurring problem on the Force series; one solution was to flush the capacitors out by taking off the power from the system (which I am currently doing as of this moment, but at work and no access to the laptop now). But if there is a chance that flushing caps don't work, I'd like some input from the NBR members on how to proceed on this.
Have already emailed my reseller regarding this matter but has yet to get back to me.![]()
-
-
Another recurring issue of SF(i.e. OCZ models as well).
-
Meaker@Sager Company Representative
Yep had 3 drives die on me (vertex 2E) and I am gunning for a C300 based crucial drive now.
-
Just got word from my reseller:
We have had this problem with the Corsair drives before it seems the SATA connection is too short and will result in issues with the laptop detecting it, the only solution to this problem is to use a different SSD or use the original drive as the primary drive.
So much for wasting money on a Corsair drive that doesn't exactly does it job. I'll just plug this one in my netbook then... -
Does the issue go away if you plug the drive back in?
-
Issue still remains...but I have/tried a number of ideas:
1) Taking away both power plug and battery so volatile charges can be discharged. Doesn't work (well still at work, haven't really tested the outcome).
2) Take the drive out, reseat it. Reboot.
Also doesn't work.
3) Put the drive in, and have something in front to apply pressure so the connecter is pushed inside more. Haven't tried this yet but a viable option.
4) Taking out my secondary HDD, leaving the single SSD alone.
Doesn't work either.
5) Taking out the SSD, leaving the secondary HDD to be read. Switch off. Place SSD then reboot. Doesn't work.
I'm contemplating on option 3, sounds reasonable but I don't have access to my laptop currently. -
Is firmware 2.0 the latest?
-
Yeah it is.
-
Sad to hear your problems! I hope i don't sumble into them too..
Though i got a newer f60 series SSD, with firmware 2.1b, yours is probably a 32nm vs mine that is 25nm, and i can only hope that makes a difference when it comes to those problems not being present!
My drive performs great and it gets better everyday it seems. -
SoundOf1HandClapping Was once a Forge
-
-
Tinderbox (UK) BAKED BEAN KING
No problems with my F60, I have had it for 6months+
-
-
I guess it's only the Clevo laptops that have a problem...sad face
-
you also determined that the drive itself was defective. maybe that has something to do with it. maybe you can test it when you get it's replacement to see if it is indeed because of the SATA connection.
what i dont get is why aren't they all a universal length? lol. i mean whoever came up with it in the first place should've sent out a mass txt or somethin. would make things a lot easier -
What I don't get is that the drive was working very well in the beginning of its life. Mind boggled about the SATA length though.
-
-
Mr_Mysterious Like...duuuuuude
Well why not go for a C300 then? They don't have any problems with any particular brand of laptops...
Mr. Mysterious -
He is getting a c300.. But he's also getting his other drive replaced under warranty.
Hopefully this replaced drive will work well in his netbook and the c300 will work well in the Sager
Spoke too soon: Corsair F60...
Discussion in 'Hardware Components and Aftermarket Upgrades' started by Thisisalamp, Mar 31, 2011.