OCZ Agility 3 problem

theukmoog · 21 May 2011 at 13:23

Installed my OS onto this new 60gb SSD Thursday morning.

PC was off overnight.

Friday morning, PC wouldn't boot - BIOS couldn't see the SSD.
Had to hard-reset the PC to get it to see the SSD and boot up.

PC was off overnight last night - fired it up this morning at 10am and the BIOS cannot see the drive again. However, 30m of rebooting has failed to get it working!

I've put the old drive back in - the SATA port and cable etc are all OK as the previous SSD is now back in that slot and working fine.

My PC is an i7-920 on a Gigabyte EX58-UD5 motherboard - yes, only Sata2 but the drive is sold as being "SATA-III / 6Gbps (Backwards compatible with SATA-II / 3Gbps)".

Does this sound like a bad drive to RMA or a complete incompatibility with my motherboard?

RJC · 21 May 2011 at 13:36

Can I ask a daft question please, the board is not see another drive and trying to boot from that? As my X58 UD5 does something similar, soon as I do something regards storage devices it throws a wobblier and I need to go into the BIOS and redo the boot sequence.

Nightglow · 21 May 2011 at 13:45

You running latest bios F12 out 2010/03/12

There is a firmware update for the Agility 3 here: http://www.ocztechnology.com/ssd_to...ex_3_Max_IOPS,_Agility_3,_and_Solid_3_series/

Install it earlier today on my Agility 3, have'nt got the rest of the pc rebuilt to see if it's a newer version.

theukmoog · 21 May 2011 at 14:14

It's not a problem with trying to boot from another drive - it says "no drive detected" in the POST screen and then is unable to boot.

I'm currently running Win7 on my old Corsair SSD, which has been working fine in that SATA2 slot since last June.

Once booted into Windows, I can plug the OCZ drive into my eSata dock and Win7 sees it - so I've downloaded the OCZ tool, which says my drive is on firmware 2.06. The release notes on that link are for 2.06, which was released on 13th May, so I've not updated.

Wombatinahat · 21 May 2011 at 18:34

isn't the latest firmware 2.36?

theukmoog · 21 May 2011 at 21:53

The readme on the page linked above has a PDF release notes for 2.06 dated 13th May.

Where did you get 2.36?

Nightglow · 21 May 2011 at 21:58

OCZ Toolbox is version 2.36 I believe.

And the Agility 3 firmware is version 2.06 .

LJ50 · 22 May 2011 at 10:02

theukmoog said:
Installed my OS onto this new 60gb SSD Thursday morning.

PC was off overnight.

Friday morning, PC wouldn't boot - BIOS couldn't see the SSD.
Had to hard-reset the PC to get it to see the SSD and boot up.

PC was off overnight last night - fired it up this morning at 10am and the BIOS cannot see the drive again. However, 30m of rebooting has failed to get it working!

I've put the old drive back in - the SATA port and cable etc are all OK as the previous SSD is now back in that slot and working fine.

My PC is an i7-920 on a Gigabyte EX58-UD5 motherboard - yes, only Sata2 but the drive is sold as being "SATA-III / 6Gbps (Backwards compatible with SATA-II / 3Gbps)".

Does this sound like a bad drive to RMA or a complete incompatibility with my motherboard?

I have woken up this morning to precisely the same issue. Hard to tell if a pattern as I only installed the drive onto a new build yesterday.

Main board is the Asus P8P67 Pro, and it is plugged into the SATA III/6Gbps port.

All I've done is remove the mains power, check the cables are all plugged in and rebooted and everything seems to be working fine again.

When I first loaded the whole thing up yesterday morning I installed the Intel RST software, but suffered a couple of "hangs" so took it off. No hangs for the rest of the day, but did wake up to this which is troubling.

theukmoog · 22 May 2011 at 10:07

And it's doing it again this morning.

Only way I've got it working is to have it in the eSata docking bay and turn it on after Win7 has loaded.

Time to raise a ticket and return it.

Atom · 22 May 2011 at 10:32

Same with mine on P67 chipset. Have to do a power cycle to get it to be detected.

Been told it is a incompatibility problem so it is boxed up to go back. Firmware update will probably fix it but it is no good until then..

LJ50 · 22 May 2011 at 10:34

Atom said:
Same with mine on P67 chipset. Have to do a power cycle to get it to be detected.

Been told it is a incompatibility problem so it is boxed up to go back. Firmware update will probably fix it but it is no good until then..

Do you mind me asking what the incompatibilty problem is? The P67 type motherboard or the motherboard model?

Thanks

Atom · 22 May 2011 at 10:38

I don't know. Just what I was told on OCZ forums..

I'm no expert but I would put it down to the drive itself. The op is on X58..

theukmoog · 22 May 2011 at 13:10

Atom said:
I don't know. Just what I was told on OCZ forums..

I'm no expert but I would put it down to the drive itself. The op is on X58..

Do you have a link to where you saw that?

Atom · 22 May 2011 at 14:19

http://www.ocztechnologyforum.com/forum/showthread.php?88836-Agility-3-disappearing-after-shut-down

Post 5.

theukmoog · 22 May 2011 at 14:43

Thanks for that.

I've posted my issue on their forums to see what OCZ's response is...
http://www.ocztechnologyforum.com/f...-Agility-3-(60GB)-problem&p=636869#post636869

Atom · 31 May 2011 at 02:23

How did you get on with this?

Vega · 31 May 2011 at 06:52

OCZ are having huge issues with the 2.06 firmware that comes with the 2.36 toolbox. My two Vertex 3's are having to be returned because of it. Theres a **** storm a brewin'.

avatar12m · 31 May 2011 at 12:52

i had the same prob so i booted of my old windows drive used the toolbox to install the latest firmware secure erased the drive and it works fine now been using it about 4 days no issues at all except it does not like asrock's instaboot

Ryan-3 · 31 May 2011 at 13:31

Mines running fine through my Asus U3S6, just a faulty temp sensor.

theukmoog · 31 May 2011 at 15:43

The only response from any official OCZ source was...

If the drive is being properly powered and connected with a known good SATA cable, the UEFI set to AHCI and the drive is still not detected in the UEFI or during Post the drive needs to be replaced.

but that came too late for me to care about as I had already DSRd the drive and am hoping the upcoming Corsair Force3 drives don't suffer from the same issues!