Intel NUC 13 Pro (Arena Canyon) review
Endorfy Arx 700 Air chassis review
Beelink SER5 Pro (Ryzen 7 5800H) mini PC review
Crucial T700 PCIe 5.0 NVMe SSD Review - 12GB/s
Sapphire Radeon RX 7600 PULSE review
Gainward GeForce RTX 4060 Ti GHOST review
Radeon RX 7600 review
ASUS GeForce RTX 4060 Ti TUF Gaming review
MSI GeForce RTX 4060 Ti Gaming X TRIO review
GeForce RTX 4060 Ti 8GB (FE) review
OCZ Vertex 460 SSD review
Posted by: on: 01/22/2014 03:55 PM [
3 comment(s) ]
OCZ just released the OCZ Vertex 460 SSD series in 120 GB, 240 GB and 480 GB versions. Based on the Indilinx Barefoot 3 controller we test the 120 GB NAND flash memory based model. The end result is an SSD that is very fast and competitive in terms of pricing, combine that with endurance and you just gotten the golden mix for the OCZ Vertex 460. Head on over into the review.
Read article
Advertisement
SSD_PRO
Senior Member
Posts: 180
Senior Member
Posts: 180
Posted on: 01/23/2014 02:35 AM
What you have described is totally bizarre, ssduser. "A" is something that any consumer-level storage device is susceptible to - yes, they should be more resilient. "B" is just bizarre. If you write over free space only what files are you checking for corruption? And how would this simulate any possible usage scenario? I have written over a Vertex 2 and Vector using AIDA64 and manually with actual files and performed MD5 checksum with no issues on either. Any reviewer would be crazy to implement such a bizarre testing setup.
What you have described is totally bizarre, ssduser. "A" is something that any consumer-level storage device is susceptible to - yes, they should be more resilient. "B" is just bizarre. If you write over free space only what files are you checking for corruption? And how would this simulate any possible usage scenario? I have written over a Vertex 2 and Vector using AIDA64 and manually with actual files and performed MD5 checksum with no issues on either. Any reviewer would be crazy to implement such a bizarre testing setup.
ssduser
Junior Member
Posts: 17
Junior Member
Posts: 17
Posted on: 01/23/2014 04:19 PM
B isn't bizarre at all. B just optimizes the ssd and then wipes the MFT&free space. I've killed two vectors this way, thinking the first was just a bad apple, when the second went, I knew there was a problem with the vector. AIDA64 isn't "(B)" so your AIDA64 thing is irrelevant. No reviewer is crazy if they implement this kind of testing. Mydefrag optimizes the SSD, moving files to best performance the ssd, then what ever files left an empty space, cuz they got moved, gets wipes with ccleaner. I do this with all my HDD's and my vertex2.
"what files are you checking for corruption?"
If you read, "On reboot, with Win7," and read all over, many many stories of, "i just rebooted, got a bunch of corrupt files, vector disappeared." So i don't know where you got "are you checking", the human doesn't check for anything.
IMHO, your entire post is irrelevant and doesn't even provide any benefit.
What you have described is totally bizarre, ssduser. "A" is something that any consumer-level storage device is susceptible to - yes, they should be more resilient. "B" is just bizarre. If you write over free space only what files are you checking for corruption? And how would this simulate any possible usage scenario? I have written over a Vertex 2 and Vector using AIDA64 and manually with actual files and performed MD5 checksum with no issues on either. Any reviewer would be crazy to implement such a bizarre testing setup.
B isn't bizarre at all. B just optimizes the ssd and then wipes the MFT&free space. I've killed two vectors this way, thinking the first was just a bad apple, when the second went, I knew there was a problem with the vector. AIDA64 isn't "(B)" so your AIDA64 thing is irrelevant. No reviewer is crazy if they implement this kind of testing. Mydefrag optimizes the SSD, moving files to best performance the ssd, then what ever files left an empty space, cuz they got moved, gets wipes with ccleaner. I do this with all my HDD's and my vertex2.
"what files are you checking for corruption?"
If you read, "On reboot, with Win7," and read all over, many many stories of, "i just rebooted, got a bunch of corrupt files, vector disappeared." So i don't know where you got "are you checking", the human doesn't check for anything.
IMHO, your entire post is irrelevant and doesn't even provide any benefit.
Click here to post a comment for this article on the message forum.
Junior Member
Posts: 17
Additional testing
This is in regards to ocz_vertex_460.
Let me explain. I and others had owned the vector, which is barefoot3, had power failure "power outage from power company" the vector no longer worked. corrupt files system ect. And the reviews are all over newegg, forums everywhere.
There are two ways to kill a vector to my knowledge.
A)Power failure.
B)Mydefrag program/ flash memory disk option / tick the selected ssd / Run. Let it finish. Ccleaner / Tools / Drive Wiper / Free space only / Simple Overwrite (1 pass) / Tick the selected SSD / Click Wipe. Let it finish. Reboot. On reboot, with Win7, you should see bunch of corrupt files / corrupt filesystem ect. Power off the system. UEFI will no longer detect the vector, vector is dead.
I "ssduser" done both A) & B) atleast 30 times with my vertex 2 and never had a problem.
Search overclock dot net is-my-crucial-64-gb-ssd-failing Post 10 by ACHILEE5
Post 10
ACHILEE5
Yeah wiping the free space won't cause any harm, it's just one write after all!
And I'm doing it right now smile.gif
edit, just finished it!
I would love to see you guys purposely cause power failures over and over with a system that is running this ocz_vertex_460 and follow the exact steps provided in section A) & B).
Not just this ssd, but for all future testing of all your ssd reviews.
This is a great idea and please consider adding this to your testings.
Thank you.