Rumboogy Posted July 29, 2013 Share Posted July 29, 2013 I have a Force GT (90GB, FW ver. 5.06B) that is installed in a "early 2011" MacBook Pro 13". It fails to boot about every 7th time. What happens is I get the grey Apple logo and the spinning clock and then the Apple logo changes to a circle with slash (like a do not enter sign). I have tried these combinations: - Force GT all by itself in HDD bay - Force GT in HDD bay and Hitachi OEM drive in optical bay - Force GT in optical bay and Hitachi OEM drive in HDD bay I also tried using cloned versions of OS X and a fresh install. Also did SMC and PRAM resets. Nothing works. This Force GT is just not reliable on boot. But once booted (if it does succeed) then there are no more problems. So this is purely a boot time issue. What do y’all think? Link to comment Share on other sites More sharing options...
Rumboogy Posted July 29, 2013 Author Share Posted July 29, 2013 I also found that as a non-boot drive, sometimes the SSD just does not show up after booting from the HDD. Called up Corsair tech support and they suggested sending me a new drive (RMA) so that is what I will do. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted July 30, 2013 Corsair Employees Share Posted July 30, 2013 If the issue persists I would check with Apple as I remember with the early 2011 Models had a cable issue that was solved by replacing the adapter cable. But not sure if it was this specific Model. Also check the system has the latest Firmware installed. Link to comment Share on other sites More sharing options...
Rumboogy Posted July 31, 2013 Author Share Posted July 31, 2013 It has never failed to boot with the HDD installed but that is SATA II. I guess the SATA cable could have a signal integrity issue but I don't see any issues once it is up and running. Only at boot. Link to comment Share on other sites More sharing options...
Corsair Employees RAM GUY Posted July 31, 2013 Corsair Employees Share Posted July 31, 2013 The issue as I remember it was that it would cause a detection issue at post and the system would not boot to the O.S. and rebooting the system would sometimes allow the system to start properly. But again that is assuming that your system was one that was affected and one thing to check. If it can be solved by changing the cable? Other than the NB Firmware being updated those are the only two issues I am aware of. But if you can test the drive in another system that may help to isolate that it is not the drive. Link to comment Share on other sites More sharing options...
Rumboogy Posted August 1, 2013 Author Share Posted August 1, 2013 Because it is a Mac is has a SATA cable with a special motherboard connector. I can't just go to Fry's and get anything like it. But the disk works fine once it is up and running. The problem is only at boot time (or before) and it can occur if I am booting to the SSD or to the HDD. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.