Printable View
I tested the new SF fw on a few of my V3s and boy have things changed.
I need to re-check my benchmarks/tests from last night but it looks like they have made a lot of changes, performance has changed a lot.
If what I see is correct I will be testing something SF based with the new fw for sure.
The new 5.02FW is a whole bag full of interesting! They're doing something different for sure.Quote:
Originally Posted by Anvil
I'm not sure anyone is actually looking for one of these two but great prices U.S.
The full ad.> http://promotions.newegg.com/NEemail...ndex-_-E0-_-IT
Intel 520 120GB Desktop kit $160> http://www.newegg.com/Product/Produc..._-20167093-L0C
Crucial m4 256GB $200> http://www.newegg.com/Product/Produc...-20148443-L07B
No rebates that is the price. FREE shipping.
The price of the M4 is far and away the most aggressively priced drive on the market. Few companies are going to be able to match it. But you have to think the drive's successor will be out soon.
The Mushkin Chronos Deluxe 240GB has been in the $250 range for months, and that's not a bad deal either, especially on 5.xx FW. 32nm Toggle is good stuff.
In the ASU thread I posted some results from my CDx120 on 5.02 and got significantly different results than in the past, and its definitely worth the upgrade.
Yesterdays update:
m4
819.1587 TiB
3477 hours
Avg speed 74.48 MiB/s.
AD gone from 148 to 142.
P/E 14128.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=489359
Intel X25-M G1 80GB
579.43 TiB
22810 hours
Reallocated sectors : 150 to 151
Available Reserved space: 90
MWI=124
MD5 =OK
45.15 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=489360
Todays update:
m4
826.7945 TiB
3507 hours
Avg speed 74.46 MiB/s.
AD gone from 142 to 137.
P/E 14258.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=489595
Intel X25-M G1 80GB
584.09 TiB
22840 hours
Reallocated sectors : 151
Available Reserved space: 90
MWI=124
MD5 =OK
45.18 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=489594
Kingston SSDNow 40GB (X25-V)
931.77TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 8352
MD5 OK
33.85MiB/s on avg (~50 hours)
The chronos deluxe 240GB was at 200$ last week at ncix. But yes it's in Canada.Quote:
Originally Posted by Christopher
Too bad I didn't wait, I took it when it was 260$ 2 months ago!
Prices are going down, OCZ reports it sells SSD at 0.65$/GB.
Patriot Torqx-2 64GB - Day 80
Drive hours: 1,932
ASU GiB written: 137,907.07 GiB (134.68 TiB)
Avg MB/s: 25.16 MB/s
MD5: OK
Bad blocks: 4 grown, 83 factory
Wear cycle counter: 8630 average erase cycles, 13275 maximum erase cycles.
Total ECC Error Count: 1
Intel 520 60GB - Day 72
Drive hours: 1,728
ASU GiB written: 547,629.46 GiB (534.80 TiB)
Avg MB/s: 95.36 MB/s
MD5: OK
Host GB written (F1): 551,243.91 GiB (538.32 TiB, 17639805 raw)
NAND writes (F9): 390,247 GiB (381.10 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 114 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 19
Drive hours: 532
ASU GiB written: 219,673.92 GiB (214.53 TiB)
Avg MB/s: 144.97 MB/s
MD5: OK
Sector GB written (E8): 221,533.39 GiB (216.34 TiB, 464589188133 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 71
The throughput looks very stable on all your drives.
Do they vary much during a loop?
Todays update:
m4
832.7410 TiB
3530 hours
Avg speed 74.48 MiB/s.
AD gone from 137 to 134.
P/E 14359.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=489721
Intel X25-M G1 80GB
587.72 TiB
22863 hours
Reallocated sectors : 151 to 152
Available Reserved space: 90
MWI=124
MD5 =OK
45.20 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=489718
Samsung 830 256 Day 50
1,188,765.36 GiB
1,160.90 TiB
297.09 MB/s Average
1175 Hours
5167 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
Attachment 126467
OCZ Vertex Turbo 64 Day 67
474,463.19 GiB
463.34 TiB
85.24 MB/s Avg
1688 hours
8477 Avg PE count
-100 MWI
0/0/0 Read/Program/Erase Fail
Attachment 126468
--------------------------------
The 830 finally popped some blocks.... I'll dig through the data to see when exactly.
While I was away over the weekend, I had trouble getting in touch with the E-Rig. When I got back and looked, the VT was doing .02MB/s and the average had dropped to 47MB/s. I stopped and restarted it, and it seems to be fine now.
Definitely.Quote:
Originally Posted by Anvil
The Intel 520 is definitely the most stable though, usually always running at about 103meg per sec in the loop.
The Torqx 2 is all over the place. (20meg per sec to 60meg per sec) Ussually faster at the beginning of the loop for a gig or so.
The Vertex 4 is mostly 182meg or so per sec during the loops, but slows significantly once free drive space falls below about 8gig or so. My average is probably so low because of the large amount of static data I am using meaning loops are shorter.
A small teaser of what I'll get in the mail next week :D
http://www.diskusjon.no/index.php?ap...tach_id=489857
By the way, it's a 64GB flavour.
My best guess would be the
Kingston SSDNow E Series SNE125-S2 64GB
Should be very interesting :) if that is the case.
(being an SLC it could literally last forever)
BTW, the price makes me wan't one, I paid close to 2x for the Intel X25-E 32GB. (a few years ago)
Looks like one of the stores are already out of stock :)
Oooohhh! I'm so jealous!Quote:
Originally Posted by B.A.T
I did get a 32GB X25-E for $45 not too long ago, so I can't complain all that much.
My 64 cost me 350$ so you got a good deal.
I see you are a quick draw :DQuote:
Originally Posted by Anvil
Interesting news:
Seems the Patriot Torqx 2 is dead. It crashed when I upgraded the vertex 4 firmware.
Reporting CRC errors and saying drive unformatted. Will try a secure erase before declaring complete death though, but not expecting much.
On that note, I'm playing with the new vertex 4 firmware. In some ways it is impressive, in others, it is a setback. For my 55 gig endurance run, I get about 27gig written at about 375meg per sec, and the other 27gig at about 100 gig per sec.
Hopefully, OCZ can get this firmware working a bit more consistently before releasing 1.4 proper, but it has promise.
Looks like it's joining the heard of dead ssd.
I usually disconnect all other drives when performing fw upgrades, let's just say that I had a few odd experiences that lead to data loss on other drives.Quote:
Originally Posted by canthearu
I ordered a V4 along with the SLC, I need to check out that drive :)
The 830 is a monster. Hopefully I made a good decision to stripe 8 of them (256GB) on this 1880ix-24. :D
B.A.T.
You can't seriously be thinking of throwing an X25-E in your endurance rig... 80GB of 50nm SLC, OP'd to 59GB. If you're lucky, in year 5 your power supply will short it out. If not... I mean, unless you're running full span random 4K's, I don't think you stand a chance :rolleyes:
Samsung 830 256 Day 51
1,214,643.37 GiB
1,186.17 TiB
296.25 MB/s Average
1200 Hours
5279 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Total Used Block Count 4
Reallocated Sectors 8192
OCZ Vertex Turbo 64 Day 68
481,958.16 GiB
477.66 TiB
85.10 MB/s Avg
1693 hours
8611 Avg PE count
-100 MWI
0/0/0 Read/Program/Erase Fail
--------------------------------
If the Vertex Turbo's firmware was still set for 10,000PE based MWI, it would still be at 24MWI.
The 830 just hit 1200 hours of testing, so 1,214,600GiB in 1200 hours is nothing to sneeze at.
Oh yes. :up: Been at it for 10 months now and if it's impossible to breake I'll just put it in my foldingrig :)
Todays update:
m4
839.9220 TiB
3558 hours
Avg speed 74.50 MiB/s.
AD gone from 134 to 130.
P/E 14480.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=489920
Intel X25-M G1 80GB
592.11 TiB
22891 hours
Reallocated sectors : 152 to 153
Available Reserved space: 90
MWI=124
MD5 =OK
45.23 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=489919
The way I figure it, you'd be able to avg around 160MB/s with a 32GB X25-E, or 13.5TB a day. That works out to 337.5x drive capacity (based on the 40GB of SLC onboard) a day. That means it would only take ~296 days to exhaust MWI. If the drive died exactly at MWI 1, then that would be do-able.
But I don't think it would work like that. If the X25-V can make it to 25,000PE cycles, why can't the X25-E make it to 500,000? Or 750,000? I think that 50nm SLC will pretty much last forever unless you're placing it under absurdly high WA full-span conditions.
Now double the amount of flash, but keep the same avg. speed... almost two years to MWI 1.
The man who decides to endurance test an X25-E would officially be known as the bravest man to walk the Earth.
But keep in mind the controller doesn't support trim so the WA will be higher than X25-V/M G2 during normal endurance testing.
True, but the OP really helps. I don't think the E's suffer much from the lack of TRIM. Maybe I should do some testing.Quote:
Originally Posted by B.A.T
I think I'll quote you on that and one, frame it and hang it on my office wall :DQuote:
Originally Posted by Christopher
B.A.T.: The Man. The Myth. The Legend.Quote:
Originally Posted by B.A.T
Lot of fun around here....:D
We gonna need to change the graph beyond 1400 soonish. The Samsung is looking to go where no drive has gone before and will ever go: 2PiB and beyond. I see no indications of any kind of distress.
Sounds like I need some kind of cape :rofl:Quote:
Originally Posted by Christopher
:up: You had something like this in mind? :shrug: :ROTF:Quote:
Originally Posted by B.A.T
Attachment 126548
:rofl:
Maybe we should get some T-Shirts, I'm sure we could find some Funny slogan.
That is probably the smartest thing to wear with this hobby :rofl:Quote:
Originally Posted by Hopalong X
By the way - It's in my mailbox tomorrow :)
The New Adventures of B.A.T.M.A.N.
Bats in his Belfry.
Coming to a theater near you fall of 2012.
:clap:
Sorry B.A.T.
Chris and Anvil made me do it. :rolleyes:
:up:
We should have a t-shirt design contest. The winner gets two broken MTRON 16GBs!
Well I already posted my picture entry
B.A.T.S. in his Belfry is my slogan entry. :ROTF:
We have an erase failure on the Vertex Turbo
MWI is now down to 99, erase fail = 1, and it happened somewhere near 8738 avg PE.
So within a few days, both the 830 and the VT have failed their first blocks.
And I'll throw in a Kingston V+100 - The perfect paperweight :rofl:
Who want to be the judge?
Todays update:
m4
845.7021 TiB
3581 hours
Avg speed 74.49 MiB/s.
AD gone from 130 to 127.
P/E 14578.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490012
Intel X25-M G1 80GB
595.66 TiB
22914 hours
Reallocated sectors : 153 to 154
Available Reserved space: 90
MWI=124
MD5 =OK
45.25 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490011
Kingston SSDNow 40GB (X25-V)
940.08TB Host writes
Reallocated sectors : 05 41
Available Reserved Space : E8 99
POH 8425
MD5 OK
33.46MiB/s on avg (~122 hours)
Samsung 830 256 Day 52
1,240,699.36 GiB
1,211.62 TiB
296.62 MB/s Average
1225 Hours
5391 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
OCZ Vertex Turbo 64 Day 69
489,383.22 GiB
477.91 TiB
85.24 MB/s Avg
1718 hours
8743 Avg PE count
-99 MWI
0/0/1 Read/Program/Erase Fail
--------------------------------
The VT has finally dropped a block. If you had put money on the VT having the first erase fail, you would have lost.
Nevertheless, both drives have really impressed me so far in that respect. The 830 didn't lose a block until after a PiB, and the 64GB 830 made it almost halfway to 1 PiB before popping a block.
Attachment 126563
Christopher,
I find the 830 to be the most impressive, nothing wrong with the VT though, as long as the fw does it's job it'll definitely put up a fight.
I'm not saying that as if the fw is bad, it's just that fw's have come a long way.
The Cognac firmware has come about a thousand miles since 2009, but I think I have to credit the Vt's performance to the flash. The last one was obviously defective -- if it arrives on my door with runtime bad blocks AFTER burn in, something is up.
But yeah, the 830 is so sexy -- it's a shame more drives aren't using Samsung flash like the VT and 830.
The VT made it to almost 8.7K PE cycles before a bad block, and the 830 made it to almost 5.2K PEs. Not bad considering one is using 51nm and the other is using 27nm.
Yes, the NAND should be excellent on the VT.
Hmmmm, in other news ... the torqx 2 may not be quite dead yet.
Just did a secure erase and it seems to be back ... but with a couple more popped blocks and a read error.
And a graph showing transfer rates over time for the intel 520 and vertex 4 with new firmware.
Attachment 126594
Notice how the vertex 4 starts off real quick, but ends up going slower then the intel 520 towards the end of each loop
I figured you'd get some response from the Torqx, is it fit for the test?Quote:
Originally Posted by canthearu
So the V4 starts off at ~400MB/s for a minute or so and then levels at ~100MB/s, what does look a bit odd is the pause at the end of the loop, it looks to be lasting longer than the SF drive?
Yeah, TRIM certainly isn't instant on the vertex 4. A few significant pauses during TRIM occur.
On the 1.3 vertex 4 firmware, performance is a bit more consistent (at around 180meg per sec)... which seems to be better for endurance testing then the current situation.
The Torqx 2 seems fit enough to go back into the endurance test .... I'll put it back in tomorrow. (SMART values are starting to show the scars of old age ... tis an old battle wound :P)
How many files are generated during a single loop on each drive? (520 vs V4)
(might make up for the time it takes for deleting/TRIMming the files)
Yeah, the V4 does 18240 files per cycle.
The 520 does 12940 files per cycle.
The V4 (and 520) is quicker deleting when TRIM is disabled though.
--------------------------------
Samsung 830 256 Day 53
1,261,175.94 GiB
1,231.61 TiB
296.40 MB/s Average
1245 Hours
5480 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
--------------------------------
OCZ Vertex Turbo 64 Day 70
495,280.250 GiB
483.67 TiB
85.08 MB/s Avg
1738 hours
8850 Avg PE count
-99 MWI
0/0/1 Read/Program/Erase Fail
--------------------------------
Todays update:
m4
851.2467 TiB
3602 hours
Avg speed 74.49 MiB/s.
AD gone from 127 to 123.
P/E 14673.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490115
Intel X25-M G1 80GB
599.04 TiB
22935 hours
Reallocated sectors : 154
Available Reserved space: 90
MWI=124
MD5 =OK
45.27 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490114
I was too late for the post-office today so you'll have to wait until tomorrow for the fun to begin :(
That's not very becoming for the Bravest Man on the Face of the Earth.Quote:
Originally Posted by B.A.T
I had to work some overtime... But it's going to be a glorious weekend. :D
I posted about this in the Plextor M3P thread, but it's worth pointing out here... because things have changed, and the M3P may now be a testing candidate. I'll have to run some tests, but the M3P 1.03 firmware added a whole mess of new SMART attributes -- MWI, temp, etc (viewable through the new Plextool). I can probably figure out the attributes on my own, but one may be host writes.
UPDATE
Yes, the M3P now has host writes! In 64MB increments! Attribute B1... thanks, Plextor! I don't know why I'm so excited-- it still doesn't have a PE cycle counter.
I got one erase failure more on the VT, and one read failure. I hope it's not about to hit a brick wall and die slow over the next two weeks.
So that's 2 erase and one read fail.
i fear for the M3P now...:bsod:
I got mine today (about 40 minutes ago), not sure what gets connected first, the Vertex 4 or the Kingston or a few M3P's. (will be later tonight anyways)Quote:
Originally Posted by B.A.T
Tthe M3P's have been sitting in their box for almost a week, the 1.03 FW looks to make my day though :)
(registered and got PlexTool last night!)
Well, at first I though the host writes worked in 32MiB increments -- I had no way of knowing how much I had written to the M3P. However, I copied 5.8GB and was able to determine that it was just 64MiB. The Plextool doesn't show hostwrites in any form, which seems like an oversight. After upgrading to 1.03, the host writes were visible -- I'm sure it was there before, since it didn't reset to zero when I flashed.
Further, the Plextool also has a warning about temperature throttling! 1.03 adds temps somewhere, but it's not readily obvious. It's probably just a smart flag that toggles when temp is too high, but I'll investigate further.
There could be loads of attributes that just aren't visible, the host writes attribute should be required on all drives.
(host reads as well)
My Kingston has the 8860 firmware, there is a 8862 but neither is available for download.
Lets hope that B.A.T got the same one.
Strange that Intel never released anything newer than 8850, quite a few (me including) got a mix of firmwares for the X25-E.
Samsung 830 256 Day 54
1,285,269.83 GiB
1,255.14 TiB
296.72 MB/s Average
1272 Hours
5583 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
OCZ Vertex Turbo 64 Day 71
502,106.22 GiB
490.33 TiB
85.24 MB/s Avg
1761 hours
8972 Avg PE count
-97 MWI
6/0/2 Read/Program/Erase Fail
--------------------------------
The VT keeps getting read failures. This is not good.
The first VT's death was preceeded by a relatively massive number or read failures.
I have a mix too. The toolbox indicates that one of my Es running 8790 can be updated, but I'm not sure to what.Quote:
Originally Posted by Anvil
Was there any point to updating FWs for the Es?
I believe the 88nn series fw fixed the "bug" where the drive could not recover when/if it started to slow down on writes.
Well I upgraded to 8850. Everything was great for about 4 minutes, until the drive failed. It's permanently locked -- detectable, but I can't SE it and can't re-flash.Quote:
Originally Posted by Anvil
:banana::banana::banana::banana:!!!
<100GiB left in the tank on that VT me thinks...hopefully I'm wrong.Quote:
Originally Posted by Christopher
Good to hear from you, Bluestang -- But I can't handle any more bad news today.
Weird, I'd leave it alone (disconnected) till tomorrow and then try a self test using smartmontools.Quote:
Originally Posted by Christopher
Never had issues with intel fw's except for on MBs that typically locks the drive. (Asus used to cause this phenomena)
I always HDDErase / flash old drives on a GB MB, it just works.
The FW update was successful, I then booted from the drive (it had an install on it) and a few minutes in the system locked up, the HDD indicator was solid indefinitely. I tried SEing it in Windows (VHD service and the Intel Toolbox fail to progress through the detection phase). I gave it a shot with PartedMagic, and it showed the partition info, but any attempt to perform any activity on the drive fails.
I'll let the E sit for a day and try again.
And now it's here :)Quote:
Originally Posted by Anvil
Attachment 126657
Attachment 126656
And it got fw 8860, same as you Anvil :up:
Thats's great!
It's got a different feel vs the original X25-E, somehow it feels more expensive/shiny.
That is hard to believe taken into account that this one cost a lot of $ less then the original X25-E.
The sticker and surface is just more shiny.
My drive identifies as an Intel, a bit strange.
It had a power cycle count of 37 (38 now), Power On hours is at 30 and finally 6GB host writes. (probably just testing)
E9 Media Wearout is at 99.
Pretty much the same for mine.
Attachment 126661
Looks pretty much identical to mine!
So, when do you plan on starting :)
edit:
there's no hurry, you've got plenty of time :)
Just did :)
Attachment 126662
You should change to 46% (I just noticed)
I wonder what MB/s it can do, you'll know a bit more tomorrow!
How much static data is there?
I'll change it.
You got mail. I posted a full update for the first post.
Got it, will update asap.
(most likely tomorrow morning)
That is shiny!
I like shiny things.
Todays update:
m4
858.1841 TiB
3629 hours
Avg speed 74.52 MiB/s.
AD gone from 123 to 119.
P/E 14790.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490248
Intel X25-M G1 80GB
603.28 TiB
22962 hours
Reallocated sectors : 154
Available Reserved space: 90
MWI=124
MD5 =OK
45.29 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490247
Since the G1 has passed 600TiB I'll give it a 24h retention test.
Attachment 126666
Not good.
^^ 01, CA and CB are staying pretty steady though. How did the last one look in those areas when C5 started to climb?
@Christopher
NAND hasn't even exceeded the supposed erase cycle specification yet :(
I think it might be time to put the barefoot drives out to pasture. (my intel 520 on the other hand is still ticking away just fine, will have to post an update today ... been busy/lazy)
They looked just fine on the first one. CA and CB have been at the same counts for almost six weeks.Quote:
Originally Posted by bluestang
Maybe... it's not like people are still Barefoot crazy. I still heart them -- the VertexEX is where it's at.Quote:
Originally Posted by canthearu
-----------
It's now at 3 erase/38 read fails 9025 AVG PE count.
The 830 tossed another set of blocks too. Sadness!
It's been almost a week since your last update :)Quote:
Originally Posted by canthearu
The new generation drives are definitely the most interesting ones, a few older ones does not hurt though.
Attachment 126683
Oh dear - it has been a week, I better get back in the swing of things than.
Patriot Torqx-2 was offline for several days, but I have restarted it now. It passed the "too busy to reinstall" 2-3 day retention test. It is also running a bit slower.
Patriot Torqx-2 64GB - Day 87
Drive hours: 1,959
ASU GiB written (first run): 137,907.07 GiB (134.68 TiB)
ASU GiB written (current run): 471.20 GiB (0.46 TiB)
ASU GiB written (Total): 138,378.27 GiB (135.14 TiB)
Avg MB/s: 23.41 MB/s
MD5: OK
Bad blocks: 6 grown, 83 factory
Wear cycle counter: 8768 average erase cycles, 13491 maximum erase cycles.
Total ECC Error Count: 1
SATA PHY error count: 250
Intel 520 60GB - Day 79
Drive hours: 1,843
ASU GiB written: 585,640.55 GiB (571.91 TiB)
Avg MB/s: 95.02 MB/s
MD5: OK
Host GB written (F1): 589,806.25 GiB (575.98 TiB, 18873800 raw)
NAND writes (F9): 417,543 GiB (407.76 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 112 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1
Vertex 4 128GB - Day 26
Drive hours: 648 (556 + 92)
ASU GiB written: 276,622.26 GiB (270.14 TiB)
Avg MB/s: 122.87 MB/s
MD5: OK
Sector GB written (E8): 279,130.15 GiB (272.59 TiB, 486156078177 + 99222277356 raw)
Reallocated sectors (05): 0
Raw Read Error Rate (01): 6
Remaining Life (E9): 60 (90 current - 30)
For the vertex 4, all the smart values were reset after firmware upgrade. Overall speed is a lot slower. Regret doing it.
I had issues with my Vertex 4 on the shipped fw (1.3), the 1.4RC fw looks much better. (maybe not for this test though)
Had to flash off the X79 as it gave all sorts off issues, including being locked.
Flashing on a Z68 worked instantly though, it cleared most if not all attributes.
It sucks when a major f/w update gets released after you have started testing. From an endurance perspective it is hard to know what impact the f/w change might have on the end result. Then again it seems a bit pointless to test on outdated f/w.
I’ve read a few snipets recently about some significant changes to NAND structure that are on the cards to cope with smaller geometries. (3D nand). The tech is continuing to evolve rapidly, so I wouldn’t be surprised if drives continue to be outdated every 12months and remain at high price levels for a long time yet.
The Vertex Turbo is dead! And it took the endurance rig with it when it died.
That's three drive failures in three days for me. What are the chances?
Attachment 126698
511,079.0GiB
Those signs looks to be a sure way of telling that it's about to self destruct.
What happened to the rig?
It just locked it up. It didn't "kill" the rig, I just had to restart.Quote:
Originally Posted by Anvil
I'm going to try d-flashing the VT. That SMART data was just taken from my main rig... It shows up in volume management as uninitialized and I get a "semaphore message timeout" when I try to initialize it. I was able to pull the most current SMART data off of it though. Perhaps a d-flash will get it back in the game.
Well, giving up is not in the spirit of this thread ;)
Some days I feel as though I'm in the Bermuda Triangle of solid state storage.
All the read and erase failures were in Bank 6 (C1). A dflash failed, so I laundered the flash. Subsequent dflashing attempts also failed.
Even if I had been successful, it would be like taking a lame racing horse and shooting it full of steroids and pain-killers and making it race once more; nothing good is going to happen, and I'll just have to shoot it in the head.
But that doesn't mean I'm going to stop trying to dflash it though, but I'll just have to wait a day or so.
Too bad about the VT....:(
What will be your next ssd?
At this rate, I'm just going to have to start testing M4s and X25-Vs!Quote:
Originally Posted by B.A.T
I'm thinking about doing a 128GB M3P or a 120GB Mushkin Chronos Deluxe.
The M3P is a very exciting canditate.
Sorry to hear the bad news.Quote:
Originally Posted by Christopher
Scroll down to the SSD's. Samsung 830 128GB $160. Of course you are already doing the 256GB aren't you? Just a thought.
http://promotions.newegg.com/NEemail...E0-_-PromoWord
There is a HyperX 120GB also.