Vertex 2e problems

adrichardson81

adrichardson81

adrichardson81

Associate
Joined
6 Dec 2007
Posts
1,713
Location
Cambridge
Hi guys

I'm having big problems with my Vertex 2e.

Ever since I got it, I've had odd occasions when it randomly wasn't detected on cold boot. This has now happened for 3 days in a row, so I'm getting a little panicky...

I've tried the usuals (latest bios, disabled quick boot, increased hdd detect delay, tried regular ahci mode, different sata ports etc). Needless to say, none of them made a scrap of difference even after multiple cold boots.

If I move it to a different sata port, it's detected.

Any ideas?
 
+1
just use another Sata port and enjoy your new SSD.

I got one there used as a system drive for windows 7 and bloody hell...what an upgrade! :)
 
I had this problem when using standby, occasionally would crash and I it was as if the drive was dead. Also had to change ports to get it to be detected again. Didn't matter which port I left it in.
 
Upgrade the Firmware using the OCZ Toolbox

Hey Guy,

I had some odd issues with my Vertex 2E 120GB, including random PC restarts even after a fresh install. I knew it was the drive because I put another drive in and installed Windows on that.

I found that there is a tool called the OCZ Toolbox that I downloaded from the OCZ Forum page which updated my drive to a new version that I could not find on the site. Direct link to the tool here, but I strongly advise reading the page here.

Since then my drive has been EVEN FASTER and no more reboots.
Also no more issues of not being detected, which I was getting after the PC crashed.

Please note, I put my drive into another PC and updated it because I didnt want to risk updating it from the PC that I was experiencing issues.

I hope this is of assistance guy.
 
Thanks guys.

I originally had it on port 2 and moved it to 3 when the problems started. I moved it between 0 and 1 when the problems continued. My F3s are running perfectly happily on ports 2 and 3 (they were originally on 0 and 1), so I can rule out dodgy sata ports.

Now it's a case of day 1: not detected on port 1, connect to port 0 = detected. Day 2: not detected on 0, connect to 1 = detected. Rinse and repeat...

I'm holding off updating the firmware, as the only change between 1.25 and 1.28 is support for 25nm flash. Is it worth trying a secure erase?

Must admit I'm tempted to RMA, ebay the replacement and grab a C300...
 
adrichardson81 said:
Thanks guys.

I originally had it on port 2 and moved it to 3 when the problems started. I moved it between 0 and 1 when the problems continued. My F3s are running perfectly happily on ports 2 and 3 (they were originally on 0 and 1), so I can rule out dodgy sata ports.

Now it's a case of day 1: not detected on port 1, connect to port 0 = detected. Day 2: not detected on 0, connect to 1 = detected. Rinse and repeat...

I'm holding off updating the firmware, as the only change between 1.25 and 1.28 is support for 25nm flash. Is it worth trying a secure erase?

Must admit I'm tempted to RMA, ebay the replacement and grab a C300...
Click to expand...

If you're having issues, I would definitely update the Firmware, as I did every test imaginable and that fixed it for me. I also did a secure erase afterward USING THE OCZ TOOL and that all worked a treat.

All my memory testing and drive replacing all pointed to the drive as the issue.

My advice is plug it into another PC, update firmware and secure erase then put it back and fresh install onto the drive.
Like I said before, the tool updated my firmware to a version I didnt see on the site. Maybe it was 1.30, but I will need to check when I get home (Definitely was not the version on the site though).
 
I put the ssd on its own power cable. You know the SATA power cables usually have two or sometimes three connectors well i used only one out of the two for the ssd. Not sure if that makes any difference but I was getting issues with SATA drive when on same power as SSD.

Also some motherboards come with the option to turn on the SATA hardware rom. So when it boots up you actually see it loading all the drives. Also if you have two sata controllers on your mb, i do. Try moving it to the other one rather than just another sata port.
 
Last edited:
I'll definitely look into the power issue - I've got a feeling it's either sharing with the hdds or on a molex/sata adapter (which would be less than ideal). That might also explain why none of the lights come on when it isn't detected...

I think secure erase is the next logical step, as well as maybe updating the firmware. plonka2000 - I'd be cautious about a firmware update installing something that isn't listed on their site...

I'm going to stick with the Intel controller for now - I'm pretty sure the Marvell controller doesn't support trim :(
 
Bunyan said:
Are you sure it did not update it to 1.28 thats the latest version.
Click to expand...
Yeah I'm pretty sure, because I remember updating the drive to 1.28 using the standard flash tool due to the issues I was having (Was running 1.25). I then remember after updating it using the OCZ toolboox, the version was above 1.28. I checked at the OCZ site and 1.28 was (and still is) the latest. Unfortunately I have the Intel Matrix Storage driver installed on my system which gave me an additional boost in the drives performance but somehow prevents any OCZ software from detecting the drive (Thats both the normal tool and the OCZ Toolbox). I put it into another PC as a secondary disk when updating it now, which works fine for me. Wasnt able to find time to check the exact version last night but will try over the weekend.

adrichardson81 said:
I'll definitely look into the power issue - I've got a feeling it's either sharing with the hdds or on a molex/sata adapter (which would be less than ideal). That might also explain why none of the lights come on when it isn't detected...

I think secure erase is the next logical step, as well as maybe updating the firmware. plonka2000 - I'd be cautious about a firmware update installing something that isn't listed on their site...

I'm going to stick with the Intel controller for now - I'm pretty sure the Marvell controller doesn't support trim :(
Click to expand...
I installed the 'latest' update from the official tool released by OCZ, who manufacture that drive. This is in advisement made by an actual OCZ employee on the official OCZ forum to use an official OCZ Tool. If that was to mess up my drive, I think there is some major comeback on that. ;)

Either way, it fixed my issues and gave me a boost so I'm passing on my experiences so that it may hopefully help others. The OCZ Toolbox I also found to be much easier for the same process (Updating firmware, etc) than using the flash tools on their site. The tool even checks and downloads the latest firmware itself from OCZ which most other firmware update tools do anyway.

Again, this is OFFICIAL OCZ SOFTWARE. I'm not trying to convince anyone because its all there on the forum link I provided earlier. :D
 
Last edited:
adrichardson81 said:
Actually you need driver support as well (hence no TRIM with older RST drivers).

@plonka2000 - really weird, can find 1.30 for the original vertex, but not for the 2e. Maybe it's a beta??
Click to expand...

Driver support is not necessary, TRIM did not work on older RST drivers due to compatability issues.

I'm interested with the possibility of a new firmware. Vertex 1.30 has nothing to do with firmwares for Vertex2 as it's totally different hardware.
 
There's been no proper firmware updates since 1.24 in November or December 2010. A new firmware fixing some issues was due in mid-January but was pushed back to mid-Feburary. All firmwares from 1.24-1.28 are the same except for support for newer hardware revisions.

I would ask on the official OCZ forum, they're usually quite helpful and will be able to speed through an RMA if necessary compared to the usual route.
 
Thanks for the pointer re power groen! Turns out I was running it on a molex/sata adapter, on the same line as all my case fans (I can only imagine I was p*ssed when I installed it). It's now running on an unshared native sata power cable, and I also replaced the sata data cable, just in case. So far, so good.

On the minus side, 1 stick of ram is on the way out :(
 
Having these issues.

Just quite plainly not being picked up from cold boot. The ports are fine as my original HDD is picked up and re-installed raid across the 2 drives absolutely fine.

Will try this this evening, I love how google directed me straight to the OCuK forums :p
 
You must log in or register to reply here.
Back
Top Bottom