OCZ Vertex 2 SSD recognized only every other boot, and UEFI clock resets | GA-Z87X-D3H i7-4770 |

[arunasd]

Builded new system and everything seems to be working except my OCZ Vertex 2 SSD is recognized only every other boot. When it is recognized, first boot screen (with Gigabyte logo) disappears fast and it starts booting. When it is not recognized the screen stays on first boot screen for quite some time and then boots.
Also, if the drive is not recognized and I go back to UEFI, clock is reseted 3 hours ahead then my current time, so I change it back to Pacific Time and it stays that way until the next time the drive is not recognized.
I set 2 booting drives and disable all the rest of the options, but after the OCZ drive was not recognized all that resets too.

Here is my build:
GA-Z87X-D3H
i7-4770
Corsair Vengeance 16GB (2x8GB) DDR3 1600 MHz (PC3 12800) Desktop Memory (CML16GX3M2A1600C10)
Corsair A70 CPU Cooler
Corsair CMPSU-650TX 650-Watt TX Series 80 Plus Certified Power Supply
ASUS GeForce GTX 650 Ti Boost 2GB Video Card
Seagate SpinPoint 1TB HDD (for data)
WD Green 1TB HDD (Windows)
OCZ Vertex 2 64GB SSD (OS X)

I am able to boot into Windows as well as OS X Mavericks when the drive is recognized.


Vt-d in UEFI has to be disabled, other way system is not working.

What I have tried:
Load optimized settings in UEFI
Switch SATA ports on motherboard for the drive
Switch SATA cables
Switch Power cable ports for the drive
Updated to the latest firmware

I don't know what else I could do.

Please, any help will be much appreciated

 

[2x4b]

I had (past tense) an OCZ (32Gb) that behaved like that. Eventually it could never be recognized. It was still under warrantee so I was able to get it replaced.

 

[arunasd]

I had (past tense) an OCZ (32Gb) that behaved like that. Eventually it could never be recognized. It was still under warrantee so I was able to get it replaced.

I kept this drive from my old build and it was working just fine, so it's kinda hard to believe that there could be something wrong with the drive.

Also, what is strange for me is that whenever the drive is not recognized UEFI resets some settings, how is that connected with the hard drive itself...?

 

[arunasd]

Apparently there is a known compatibility issues with Z87 SATA controllers and SSDs with the Sandforce 1200 controller where SSD drives could be slow or not recognized, or cause boot issues, or simply not be seen by BIOS or OS.

Source link: http://www.hardocp.com/article/2013/06/03/asus_z87a_lga_1150_motherboard_review/7#.UngHdpETtUM

Guess it's time to upgrade to a newer SSD.

Hope this helps to someone else with the same problem.

 

[Y0GI]

Apparently there is a known compatibility issues with Z87 SATA controllers and SSDs with the Sandforce 1200 controller where SSD drives could be slow or not recognized, or cause boot issues, or simply not be seen by BIOS or OS.

Source link: http://www.hardocp.com/article/2013/06/03/asus_z87a_lga_1150_motherboard_review/7#.UngHdpETtUM

Guess it's time to upgrade to a newer SSD.

Hope this helps to someone else with the same problem.

Yep! I found this out the hard way when I built the system in my sig. I attempted to use 2 OCZ Vertex 2 SSDs. After many failed attempts, a firmware upgrade and a lot of research, I gave up and resigned myself to the fact that the Vertex 2 and the Haswell (Z87) chipset just don't get along. I ended up buying a 128 GB Samsung 840 Pro which has worked flawlessly.

Yogi

 

[xtrazyx]

There is no solution except having a non Z87 sata controller. This is not acceptable but apparently it is not bothering anyone. You want to upgrade to haswell, oh then put your sandforce SSD (not an old technology by the way) to the trash because it will never be compatible. It is insane, having to throw a machine that works perfectly is a very bad testimony of our time.

 

[mitchd123]

Builded new system and everything seems to be working except my OCZ Vertex 2 SSD is recognized only every other boot. When it is recognized, first boot screen (with Gigabyte logo) disappears fast and it starts booting. When it is not recognized the screen stays on first boot screen for quite some time and then boots.
Also, if the drive is not recognized and I go back to UEFI, clock is reseted 3 hours ahead then my current time, so I change it back to Pacific Time and it stays that way until the next time the drive is not recognized.
I set 2 booting drives and disable all the rest of the options, but after the OCZ drive was not recognized all that resets too.

Here is my build:
GA-Z87X-D3H
i7-4770
Corsair Vengeance 16GB (2x8GB) DDR3 1600 MHz (PC3 12800) Desktop Memory (CML16GX3M2A1600C10)
Corsair A70 CPU Cooler
Corsair CMPSU-650TX 650-Watt TX Series 80 Plus Certified Power Supply
ASUS GeForce GTX 650 Ti Boost 2GB Video Card
Seagate SpinPoint 1TB HDD (for data)
WD Green 1TB HDD (Windows)
OCZ Vertex 2 64GB SSD (OS X)

I am able to boot into Windows as well as OS X Mavericks when the drive is recognized.


Vt-d in UEFI has to be disabled, other way system is not working.

What I have tried:
Load optimized settings in UEFI
Switch SATA ports on motherboard for the drive
Switch SATA cables
Switch Power cable ports for the drive
Updated to the latest firmware

I don't know what else I could do.

Please, any help will be much appreciated

I realize this is an old post, but many others are still running into this problem.

Rather than dumping the SSD, or the motherboard, another option is to purchase an add on SATA card. I contacted OCZ support for my 60Gb Vertex 2 SSD and they suggested the following solution:

The series 2 model drive is not compatible with Haswell based chipsets. It will not function correctly or even at all if attached to the Haswell Intel SATA ports on the motherboard.

If your motherboard has an onboard integrated raid controller, such as one made by Marvell, ASMedia, or JMicron the drive will work fine in one of these SATA ports. But it will not function correctly when attached to an Intel SATA port on a Haswell motherboard.

I added in a $15 ebay SATA card, and now the SSD is rock solid. I used Passmark Rebooter and cycled the box through 120 reboots without a single failure.

 

[photonboy]

Ah.. thanks.

Intermittent boot failure (CSM compatibility) with Asus Z87 Gryphon and OCZ Vertex 2.

 

[ImpliedConsent]

I know this is old - but I'm still gonna use my Vertex2 as my boot drive on Haswell. It doesn't bother me too much as long as UEFI can see it (about 75% of the time), it'll boot. I found that if I activated 'display S.M.A.R.T. info' within BIOS/UEFI, it increases the chances of a recognition and eventual boot. OCZ is refusing to do anything about it and hope they die an ugly death.

Any SSD is better as a boot than any HDD.

-- oh, about clock -- I use Kubuntu 14.04 and by default it will reset hardware clock to UTC (Zulu), but the OS will continue at your local time (and you can disable the fuction) ... not sure what OS you are using, so not sure if this applies.

 

[Praz-1]

OCZ is refusing to do anything about it and hope they die an ugly death.

Hello

There is nothing OCZ can do regarding this incompatibility. This issue exists for SSDs from all manufacturers that use the 12xx/15xx controllers. A fix would need to come from SandForce and as SSDs based on these controllers have been EOL for a long while now they have chosen not to address this issue.

 

[ImpliedConsent]

Hello
There is nothing OCZ can do regarding this incompatibility. This issue exists for SSDs from all manufacturers that use the 12xx/15xx controllers. A fix would need to come from SandForce and as SSDs based on these controllers have been EOL for a long while now they have chosen not to address this issue.

Praz, I know that you and the OCZ team's hands are tied, but the Haswell SKU specifications went out to manufacturers (RTM) at least a year (or more) prior to the release in May 2013. My guess is that Sandforce did some regression testing on the controllers, found a problem, either kept it quiet...or DID publish to their results to the manufacturers. That's where OCZ comes into play. When was your first indication there was a problem prior to your post? Y'all just happen to wait until most ran out of their warranty?

On the bright side - Vertex 2 DOES work with Haswell, but just have to deal with reboots at P.O.S.T. (Get rid of splashscreen so you can see what's going on). If POST doesn't see it, it'll fail. If POST does see it, you're gonna get a boot. My disappointment is with OCZs handling - no warnings - no offers - just a big forum release said: Yep, it's broke and it's not our fault...sorry, get another SSD.

 

[Praz-1]

Hello
There is nothing OCZ can do regarding this incompatibility. This issue exists for SSDs from all manufacturers that use the 12xx/15xx controllers. A fix would need to come from SandForce and as SSDs based on these controllers have been EOL for a long while now they have chosen not to address this issue.

Praz, I know that you and the OCZ team's hands are tied, but the Haswell SKU specifications went out to manufacturers (RTM) at least a year (or more) prior to the release in May 2013. My guess is that Sandforce did some regression testing on the controllers, found a problem, either kept it quiet...or DID publish to their results to the manufacturers. That's where OCZ comes into play. When was your first indication there was a problem prior to your post? Y'all just happen to wait until most ran out of their warranty?

On the bright side - Vertex 2 DOES work with Haswell, but just have to deal with reboots at P.O.S.T. (Get rid of splashscreen so you can see what's going on). If POST doesn't see it, it'll fail. If POST does see it, you're gonna get a boot. My disappointment is with OCZs handling - no warnings - no offers - just a big forum release said: Yep, it's broke and it's not our fault...sorry, get another SSD.

Hello

First, I guess you and I have different definitions of "DOES work". I can't bring myself to consider a drive as working when it can and will disappear at will.

Personally, I was aware of this incompatibility shortly before the Haswell platform launched. I found it during testing. At that time neither OCZ nor any other SSD manufacturer were aware of any issue as far as I know. I received the reason for this incompatibility directly from Intel. Intel published this incompatibility when the Haswell platform was launched. Because this incompatibility was made public by Intel at launch and this launch closely coincided with SandForce making the 12xx/15xx controllers EOL I believe that all the SSD manufacturers felt no other announcement was needed. Any fix for this issue would had to have come from SandForce not the SSD manufacturers.

 

[ImpliedConsent]

[qu

Hello

First, I guess you and I have different definitions of "DOES work". I can't bring myself to consider a drive as working when it can and will disappear at will.

Personally, I was aware of this incompatibility shortly before the Haswell platform launched. I found it during testing. At that time neither OCZ nor any other SSD manufacturer were aware of any issue as far as I know. I received the reason for this incompatibility directly from Intel. Intel published this incompatibility when the Haswell platform was launched. Because this incompatibility was made public by Intel at launch and this launch closely coincided with SandForce making the 12xx/15xx controllers EOL I believe that all the SSD manufacturers felt no other announcement was needed. Any fix for this issue would had to have come from SandForce not the SSD manufacturers.

Yep, I guess our definitions do differ ('cuz any semi-working/working SSD is better than platter); however, for the remainder of your answer, it appears that SandForce washed their hands of it and no pressure from the manufacturers would help. I get it, but for the remainder of your original post on ocz (from what I remember pre-Toshiba), it was more of an 'oh-well' response. That's what stuck in my head, which, unfortunately, brings me to 'slow-death' comment.

Praz, I know y'all work your butts off with support, RMAs, etc ... but for me personally, that's what put me and ocz at odds at 'never-again' (just like that Hyundai car my ex-wife insisted on), even though it was SandForce issue, it had the ocz name on it.

 

[nudog2]

If you really want to fubar your OS try installing Intels Rapid Storage Driver on that Sandforce 1xxx SSD......BOOM!!.... no boot to windows just a BSOD saying your MBR is corrupt or missing..

I dont know why people are failing to see that Intel was (kinda still is) SandForces direct competitor in the SSD controller market.

If you have to buy a new SSD theres a good/better chance it will have a Intel controller on it.

 

[photonboy]

If you really want to fubar your OS try installing Intels Rapid Storage Driver on that Sandforce 1xxx SSD......BOOM!!.... no boot to windows just a BSOD saying your MBR is corrupt or missing..

I dont know why people are failing to see that Intel was (kinda still is) SandForces direct competitor in the SSD controller market.

If you have to buy a new SSD theres a good/better chance it will have a Intel controller on it.

Where did you come to the conclusion that most SSD's use Intel controllers?

I could NOT find any SSD's that used an Intel controller other than Intel SSD's and some of those weren't Intel. You can see what controller is used here for any SSD: http://pcpartpicker.com/parts/internal-hard-drive/#t=0

There were also plenty of other controllers from Samsung, Indilinx, JMicron, Marvell for the other SSD's. So again, I'm not sure where you got this information that most SSD's use an Intel controller.

 

[illepic]

I just wanted to post here and say that I went through this exact same thing on an Asrock z97 Extreme6 motherboard, using my previous build's OCZ Vertex 2 as a fast secondary drive. Absolutely could not boot to Windows, hard drive lights would stay on for 5+ minutes before Windows boot, etc. Like others have pointed out, I had the OCZ Vertex 2 drive plugged into the Intel SATA ports. I moved it over to the Asrock "Asmedia SATA3" ports and I boot flawlessly.

Now the only thing I have to deal with is the drive not showing up after sleep, but that's probably yet another issue. Just wanted to thank everyone for solving this issue for me.

 

[ImpliedConsent]

Praz (and all). OK, I moved on to another SSD for my PC (850 Pro); however, the good news is that the Vertex 2 works very well as a PS3 drive replacement. BTW, Clonezilla was flawless to move over my ext4 Kubuntu from the OCZ 120GB to the 850 Pro 256GB drive ... and extended the partition as one.

 

[Redheadsrule13]

Bumping this as I am having the same problem. I have a Kingston SSDNow v300 240GB with an Asus Maximus VI Gene, and I've discovered that I can't get a proper boot when I have it plugged into the Intel Z87 ports. However, when I plug it into the extra two SATA ports which are ASMedia SATA ports it works just fine. My SSDNow V300 uses the SandForce SF-2281 controller as well, so this doesn't seem to be just an issue with the older Sandforce controllers.

For anyone else out there who might be having the same issue; when booting to Win 8.1, I'll normally get to the login screen after the ring of dots has gone around once or twice, but when I have it plugged into the Z87 ports, it goes around about 10 or so times before blue-screening and restarting immediately, not even giving my a chance to see the bluescreen information.

 

[Aeolian]

Hello all,
A lot of users seem to have this problem, me no exception!
I have similar system like OP, exception a newer SSD: OCZ Vertex 3 (120GB) on SandForce SF-2281 controller.

I have loaded UEFI W8.1 on USB drive, followed installation instruction here. However after the first boot as part of the W8.1 installation process, the PC would reboot/shutdown with no avail.
On my BIOS/UEFI end I have made everything UEFI only and disabled any Legacy mode support.

Any clue what is cooking here? Should I blame SF controller and get a new SSD or there is something more sinister.
Cheers