Overclock.net banner
1 - 20 of 62 Posts

Lutsk92

· Registered
Joined
·
270 Posts
Discussion starter · #1 ·
So I downloaded latest OCZ Vertex 3 firmware at:
http://www.ocztechnology.com/ssd_tools/OCZ_Vertex_3,_Vertex_3_Max_IOPS,_Agility_3,_and_Solid_3_series/

but cannot update it when getting error:
Firmware update is not supported on primary drive.

Again, there's a notice at the main page before downloading the firmware saying: Updating the firmware from the toolbox is not supported when Windows is running off the drive you are trying to update.

So what do I do now? I want to update my OCZ Vertex 240GB 2.02 to 2.36
Do I need to switch from SSD to HDD? How do I do that?
 
You need some imaging software to image the SSd then load the image to your hdd. Acronis is a good one that properly aligns ssds when imaging to them. You could also just load Windows on the spare hdd temporarily or use a different pc. Either way, back up your data before the firmware update because you could lose your data.
 
If I may ask, why do you want to upgrade the firmware from 2.02 to 2.06?
For loads of us, this irreversible update led to ridiculous BSODs or unresponsiveness issues. Once you get this, you reset the computer only to find the SSD is no longer detected. The only way to fix this is to turn off the computer and turn it back on. However, this seems to happen at least once a day for most...
I've literally tried everything under the Sun to get this sorted but cannot. I'm now RMA'ing my SSD in the hopes they send me a 2.02 drive so I can never touch 2.06 again!
 
Discussion starter · #4 ·
Quote:
Originally Posted by Gib007;13753050
If I may ask, why do you want to upgrade the firmware from 2.02 to 2.06?
For loads of us, this irreversible update led to ridiculous BSODs or unresponsiveness issues. Once you get this, you reset the computer only to find the SSD is no longer detected. The only way to fix this is to turn off the computer and turn it back on. However, this seems to happen at least once a day for most...
I've literally tried everything under the Sun to get this sorted but cannot. I'm now RMA'ing my SSD in the hopes they send me a 2.02 drive so I can never touch 2.06 again!
Mine is 2.06 right now and want to update it to 2.36 for the main reason that i'm getting random freeze-ups every day though detection isn't an issue for me.
 
Discussion starter · #6 ·
Quote:
Originally Posted by Lutsk92;13753767
Oh lol, I think u're right.
So no updating for me then?
You're in the same boat as me mate, so sadly no!
frown.gif

I wish there was a new update. The main issue at the moment is that OCZ and SandForce have been working hard to crack down on all the reports (Corsair are getting the same problem reports on their forums for their Force 3 SSDs) but they have announced that so far, they cannot reproduce our problems. Some OCZ staff are even convinced we're somehow causing the problem with an unstable system or lack of Windows installation technique...
kookoo.gif


I've jumped through so many hoops but am still unsatisfied. I'm RMA'ing my SSD and hoping I receive a 2.02 firmware SSD in return.
 
By the way, take a look at this:
Quote:
Optimum SSD Installation
==================

1. Reset BIOS and set "AHCI" mode for all SATA ports with "SATA-6.0Gb/s" for "OnChip SATA Speed". Disable "Onboard ATA Controller" and make sure "Suspend Mode" is set to "Auto". No system overclocking must be present ("Auto" on all "Extreme Tweaker" options).

2. Turn off computer, disconnect SSD and leave only HDD and optical drive connected.

3. Install Windows on a HDD partition.

4. Once installed, turn off computer, connect SSD and boot into HDD.

5. If applicable, delete all SSD partitions within Windows on the HDD. Secure Erase the SSD, reboot, Secure Erase again and reboot again. This ensures SSD is completely clean.

6. Turn off computer and disconnect SSD.

7. Boot into the Windows installation disc and format the HDD partition and remove it (leaving unallocated space in its place).

8. Exit Windows installation and turn off computer. Disconnect HDD and connect SSD, along with the optical drive.

9. Reset BIOS and set "AHCI" mode for all SATA ports with "SATA-6.0Gb/s" for "OnChip SATA Speed". Disable "Onboard ATA Controller", "iROG Timer Keeper" and "ROG Connect", also making sure "Suspend Mode" is set to "Auto". Again, no system overclocking must be present ("Auto" on all "Extreme Tweaker" options).

10. Install Windows on the SSD. Once done, turn off computer and connect HDD.

11. Once on the desktop, partition any unallocated HDD space and start installing all the drivers, rebooting between each core driver. Start with graphics card, then South Bridge, then AHCI.

12. Once all drivers are installed, reboot. Run "Windows Experience Index" assessment. Once done, reboot and do it again. Reboot once more.

13. Activate Windows and update it fully including Service Packs and any and all updates.

14. Once Windows is up to date, reboot once or twice to make sure they are all installed completely. Set the computer to sleep and resume two or three times (completely - S3 Sleep Mode).

15. Adjust Windows power settings to any desired custom profile. Reboot to apply the settings.

16. Re-run the "Windows Experience Index" assessment and reboot after.

17. Since system has more than enough RAM, reduce and fix page file size to 512MB.

18. Disable Windows Hibernation. In "Command Prompt", enter:

powercfg -h off

19. Turn off System Restore on the SSD.

20. Set any desired system overclock settings in the BIOS and continue all software installation.

21. Re-run the "Windows Experience Index" assessment and reboot after.

NOTE: If any core driver is updated in the future, make sure to re-run "Windows Experience Index" assessment and reboot after running it.
After some recommendations by OCZ staff on their forums, this is the guide I follow to get Windows on my Vertex 3 SSD. It was written by me, based on these staff recommendations. Ridiculous, I know, especially because "any old way" worked with my previous Vertex 2E SSD and any HDD I've ever had. What makes the Vertex 3 such a cranky *****!?

Please note that the above "guide" includes some tweaks (reducing page file size and disabling hibernation and system restore) that are purely to get extra SSD free space back. Also, the BIOS options are specific to my Asus Crosshair IV Formula motherboard. The "Onboard ATA Controller" is a JMicron Controller for RAID that I don't use and we're recommended to disable in that case.
 
The first image looked as expected but the second seems to be a little on the slow side (for writes) for a Vertex 3 240GB SSD. Remember that over-benchmarking will impact performance overall. You also seem to be benchmarking your SSD whilst running Windows on it, which will impact performance even more. The best idea to benchmark an SSD is to connect it as a secondary drive (running Windows on a HDD, or another SSD entirely) and benchmark it then. After you're satisfied with benchmarks, Secure Erase to clean it up and then use it. I suspect a Secure Erase will clean up your SSD and make it as fast as it should be.
 
Discussion starter · #12 ·
Quote:
Originally Posted by Gib007;13754191
The first image looked as expected but the second seems to be a little on the slow side (for writes) for a Vertex 3 240GB SSD. Remember that over-benchmarking will impact performance overall. You also seem to be benchmarking your SSD whilst running Windows on it, which will impact performance even more. The best idea to benchmark an SSD is to connect it as a secondary drive (running Windows on a HDD, or another SSD entirely) and benchmark it then. After you're satisfied with benchmarks, Secure Erase to clean it up and then use it. I suspect a Secure Erase will clean up your SSD and make it as fast as it should be.
How do I connect it as secondary, I meant to do that before but never figured out how. And does Secure Erase cleans everything on SSD including all applications and even OS itself? Where do I find that?
 
Quote:
Originally Posted by Lutsk92;13754254
How do I connect it as secondary, I meant to do that before but never figured out how. And does Secure Erase cleans everything on SSD including all applications and even OS itself? Where do I find that?
When I say connect it as a secondary drive, in essence you'd be using your HDD as the boot drive. You could either leave the HDD and SSD connected to the same ports as they are now but install Windows on your HDD and boot into your HDD, or, make sure the HDD in SATA port 0 and SSD in SATA port 1 and then install Windows on your HDD and boot into the HDD. Either way once you have Windows on your HDD and boot into your HDD, the SSD is a secondary drive.

Secure Erase does indeed clean everything. I think what it does is basically send a pulse to the SSD's NAND memory modules to erase them all completely. Secure Erase is a great way to make sure your SSD is back to factory default in terms of performance and cleanliness. The easiest way to Secure Erase your SSD is to get OCZ Toolbox. When your SSD is connected as a secondary drive, run OCZ Toolbox and it will detect your SSD. Select it and go to Security and there you will find Secure Erase. It only takes two seconds to perform.

Before you try to Secure Erase, though, make sure that whilst your SSD is connected as a secondary drive, that you go into Windows Disk Management and delete all the partitions made on your SSD. Then go ahead and run OCZ Toolbox to Secure Erase. If for some reason you get an error when you try to Secure Erase, close the OCZ Toolbox and run it again. It will work from that point on. I believe running OCZ Toolbox a second time makes sure the SSD is unlocked and ready to be Secure Erased.

If you're going to run some benchmarks, after the Secure Erase, create one single partition for your entire SSD (again as a secondary drive) and then run your benchmark. Remember, to get 100% reliable numbers you might need to Secure Erase between one or a few benchmarks (I say might because I'm not perfectly sure on this). Once you're happy your benchmark itch is scratched, delete the partition again and Secure Erase. At that point you're back clean and can install Windows on the SSD. And remember, it's not a good idea to run benchmarks on your SSD when it's your primary drive, nor if you're not intending on Secure Erasing it after the benchmarks. The benchmarks write tremendous amounts of data in a very short time so be sure to not benchmark it if you're using the SSD for its intended purposes (boot drive, for programs, games, etc).
 
I just noticed the FW update and found this thread via Google after making little sense out of the OCZ guide.

So let me get this straight, I have to install windows onto another drive to update the firmware?

If that's the case I won't bother.
 
Quote:
Originally Posted by elbeasto;13767860
I just noticed the FW update and found this thread via Google after making little sense out of the OCZ guide.

So let me get this straight, I have to install windows onto another drive to update the firmware?

If that's the case I won't bother.
Indeed, if you use the OCZ Toolbox, you have to basically boot into another drive (another SSD or a HDD) so for this you'd have to install Windows on to the other drive. Once you're on the desktop there, your SSD will be seen as a secondary drive naturally rather than a primary drive. That's when you can open up OCZ Toolbox, select your SSD and get its firmware updated.

Having said that, OCZ have one or two other methods and if you check their SandForce official forum, there are stickies on the top with download links and instructions. I think one of them involves installing some Linux files on to a USB drive and booting from the USB drive, which updates the firmware there and then. I don't know the specifics - I've never tried it, sorry. Someone else here might have, though.

As for the actual updating for the firmware, I'm assuming you have a Vertex 3 SSD and have version 2.02. Is there any particular reason you want/need to update to 2.06?
Apparently the risk of getting BSOD/unresponsiveness problems after updating to 2.06 is very significant (I myself have problems now with 2.06). Because of this, unless you NEED it because you have other problems (I did), then do yourself a favour and skip this firmware release. Perhaps later firmware will be much more stable. Who knows!?
 
Quote:
Originally Posted by Gib007;13768079
Apparently the risk of getting BSOD/unresponsiveness problems after updating to 2.06 is very significant (I myself have problems now with 2.06). Because of this, unless you NEED it because you have other problems (I did), then do yourself a favour and skip this firmware release. Perhaps later firmware will be much more stable. Who knows!?
I'm getting BSOD with v2.02, computer will hang for approx. 30sec then either get responsive again or BSOD. Same problem as with 2.06? I waited a long time for this drive, but with the stability issues it's "#¤%"#¤ going back. I'm using the PC at work, I can't deal with the computer crashing at random intervals.
 
Quote:
Originally Posted by soulvoid;13826730
I'm getting BSOD with v2.02, computer will hang for approx. 30sec then either get responsive again or BSOD. Same problem as with 2.06? I waited a long time for this drive, but with the stability issues it's "#¤%"#¤ going back. I'm using the PC at work, I can't deal with the computer crashing at random intervals.
Argh, that's not good. Indeed this is the problem 2.06 firmware seems to have, at least for a lot of us. OCZ and SandForce are still working on the problems. An apparent "fix" is to Secure Erase the SSD in IDE mode in Linux (yes, you read that right). Once that is done, you can go back to AHCI mode and install Windows. Check out this:

OCZ SandForce Forum - Intel-based Systems
OCZ SandForce Forum - AMD-based System

The Linux Secure Erase method is described in detail here:

OCZ SandForce Forum - Linux Secure Erase

If you're willing, give that a go. From the reports, it fixes the hanging/BSOD problems in 2.06 firmware so I assume it will fix them on your 2.02 drive. Of course, this is by no means a permanent solution and you don't really need to follow the strict guidelines of the guides I linked above - just the IDE mode Secure Erase in Linux should do the trick. Kind of points to problems with the OCZ Toolbox...
 
Quote:
Originally Posted by Gib007;13828375
Argh, that's not good. Indeed this is the problem 2.06 firmware seems to have, at least for a lot of us. OCZ and SandForce are still working on the problems. An apparent "fix" is to Secure Erase the SSD in IDE mode in Linux (yes, you read that right). Once that is done, you can go back to AHCI mode and install Windows. Check out this:

OCZ SandForce Forum - Intel-based Systems
OCZ SandForce Forum - AMD-based System

The Linux Secure Erase method is described in detail here:

OCZ SandForce Forum - Linux Secure Erase

If you're willing, give that a go. From the reports, it fixes the hanging/BSOD problems in 2.06 firmware so I assume it will fix them on your 2.02 drive. Of course, this is by no means a permanent solution and you don't really need to follow the strict guidelines of the guides I linked above - just the IDE mode Secure Erase in Linux should do the trick. Kind of points to problems with the OCZ Toolbox...
wow .. that's a lot of work.
 
Other forums are mocking the ever-increasing voodoo OCZ is making their users go through just for the possibility of getting their drives to work.

I only saw the missing from BIOS situation once in three weeks of owning an Agility 3, but the discussion and reports from elsewhere made me lose all confidence in the drive, in spite of it working reasonably well for me.

When I tweeted about it and asked "What would Patrick Norton do?", he replied with sage wisdom:
Quote:
Originally Posted by Patrick Norton
If you think the brand of hard drive or SSD has reliability issues, @DarkAudit, I'd avoid it, even if it is stupid fast!
'nuff said. I'm rockin' the Intel 510 now.
biggrin.gif
 
Quote:
Originally Posted by faulkton;13828848
wow .. that's a lot of work.
Indeed...
And useless work at that. Now Tony from OCZ is suggesting using the MSAHCI driver and not the Intel RST driver. However, everyone who has tried this is still reporting a problem despite Tony saying OCZ cannot yet reproduce the issue with the MSAHCI driver. Another user just reported that using Intel RST 10.5 (he reports that it is very new and not available on all websites yet) he has spent four days without BSODs and may be a fix. Having said that, it leaves us AMD users a bit in the woods.
Quote:
Originally Posted by DarkAudit;13832183
When I tweeted about it and asked "What would Patrick Norton do?", he replied with sage wisdom:
Quote:
Originally Posted by Patrick Norton
If you think the brand of hard drive or SSD has reliability issues, @DarkAudit, I'd avoid it, even if it is stupid fast!
'nuff said. I'm rockin' the Intel 510 now.
biggrin.gif
Hahahahaha that's pretty good. I'm too late to return the SSD to the online retailer I bought it from but OCZ are offering complete refunds if you send it to them. When I receive my RMA replacement drive, I'll think about what to do.

You know what bothers me the most?
That OCZ insist that less than 1% of their users are suffering any problems. How they came up with that number, I have no idea. When I confronted them on the forums about it, they simply ignored my post. "Less than 1%" my ****, I'm sure there are those without problems but they are trying to save face.
 
1 - 20 of 62 Posts