Last available SMART data from from the 830 was:
https://www.box.com/shared/static/e2...ik610rca6c.jpg
199 never incremented. It was never an issue of anything 199-related.
Printable View
Last available SMART data from from the 830 was:
https://www.box.com/shared/static/e2...ik610rca6c.jpg
199 never incremented. It was never an issue of anything 199-related.
Oh well. Did you ever get to the bottom of it?
Not yet. I'm working on it.Quote:
Originally Posted by Ao1
Anyone here have a Larson Creek Intel 311 drive to test ?
I think it would be interesting due to small NAND size but SLC specification.
Ok, I got sidetracked for a while there when my body decided it was time to sleep rather then post on the internet!
Thoughts on the Intel 520: Somewhat faster then my Patriot Pyro 60gig, though not enough to change my mind that the 120gig sandforce drives with cheaper async NAND offer the best price/performance. And for those looking for just an easy 60gig drive, the intel price is a bit hard to swallow. I am only paying for the intel by giving up my entertainment budget for a couple of weeks. But the proof of the pudding will show in the coming months.
Anyway, here is some benchmarks for the intel 520 (I made sure it was not running fresh by endurance testing it for about 80gig or so)
Attachment 124225
Attachment 124230
Attachment 124227
Crystaldiskinfo also reveals a lot of juicy details for this drive.
Attachment 124349
Does anyone know a program that correctly decode the Power on Hours?
I will try and report daily on progress with this drive. I'll report on the erase fail/program fail count, the host and claimed drive writes, reallocation count, and the wearout indicator.
I got one. I tested it out with some endurance loop and it did fantastic. But at the time (several months ago), it didn't seem like there was any point. Hopefully, the MTRON could have fairly high WA to shorten the process, but that 311 was seriously going to take three or four years. Assuming it would ever die, that is.Quote:
Originally Posted by bulanula
Well, I have started the torture.
Attachment 124229
This drive is cracking along reasonably quickly. I am using the following settings:
Static Data:12 gig static data (copy of windows install + a few gig of incompressable data)
OS/Platform: Core duo 2 - 2160@3.0ghz - Windows 7 x64
Date Started: 25/2/2012
Over-Provisioning: None
Drive details (for the record, though everyone should know it off by heart!)
Controller: SF-2281
NAND: Intel 25nm Synchronous - 5000 cycles.
Given that the MLC NAND can often handle 2-3 times the specified write cycle count before actually dieing, and SLC is 10/20 times more durable and ton more forgiving of wear, it may be that the 311 (or even the MTRON) simply never dies.Quote:
Originally Posted by Christopher
According to the manual:Quote:
Originally Posted by canthearu
The raw value reports two values: the first 4 bytes report the cumulative number of power-on hours over the life of the device,
the remaining bytes report the number of milliseconds since the last hour increment.
That does not seem to mean anything however.
If you run this command with smartctl you will see the true power on hours under the device statistics
smartctl -q noserial -i -l devstat,0 -l devstat /dev/sda
The last letter is a reference to the sata port so you will need to change the value depending on which sata port you are on. The command will only work with the 520& 710. (No other drives support device statistics).
MTRON 7000 PRO 16GB SLC, Day 16
GiB : 70779.94
TiB : 69.1210
MBs : 56.66
187 93/93/114768131
Attachment 124231
MTRON 7000 PRO 16GB SLC, Day 17
GiB : 74906.19
TiB : 73.1519
MBs : 56.77
187 93/92/121666447
Attachment 124234
Torqx day 10
Drive hours: 238
GB written: 12334.66 (12.0457 TB)
Avg MB/s: 17.54
Bad blocks: 83
Wear cycle counter: 0/824/1251
Intel 520 - day 1
Drive hours: ?
ASU Count GB written: 4395.34 (4.2924TB)
Smart GB written: 8287.53 (8.09TB , 265201 raw)
Avg MG/s: 75.89 MB/s
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 100 (0 raw)
NAND writes (F9): 5861GB
Notes
I had some problems with ASU losing count due to power outages.
The 09 value reported in the Intel tool box gives you the power on hours, but the counter starts from 894800 so you have to deduct that amount to get the power on hours. If you want to double check try smartmon tools and the command I gave earlier. You will need to deduct 6 hours from the value reported by device statistics to make allowance for the factory test period.
canthearu ,
Thank you for making this thread even more interesting by adding the Intel 520 :) Fingers crossed it amazes us all!
Maybe something interesting will happen to the 520! All I know is, running an SLC drive is worse than watching paint dry... I mean, it only takes 24 hours for paint to dry. I'm not sure it's possible to kill an SLC drive outside of firmware failures.
Really, when was the last time you heard an antecdote about someone wearing out an SLC drive?
Todays update:
Kingston V+100
And it dropped out again.....And because I'm not home until next friday I can't take a cold reboot.
Intel X25-M G1 80GB
374,4503 TiB
21226 hours
Reallocated sectors : 00
MWI=102 to 98
MD5 =OK
33.55 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=480615http://www.diskusjon.no/index.php?ap...tach_id=480612
m4
477.7978 TiB
1890 hours
Avg speed 70.73 MiB/s.
AD gone from 100 to 85.
P/E 8400.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=480614http://www.diskusjon.no/index.php?ap...tach_id=480613
Cool, that makes it easy ... I'll report power on hours, and reorganise the stats a bit for my next report.Quote:
Originally Posted by Ao1
You could create another fireworks display? :rolleyes:Quote:
Originally Posted by Christopher
That is almost guaranteed to happen. Especially since at some point I'm going to measure drive power consumption un endurance testing.Quote:
Originally Posted by Hopalong X
Dragging out the old Tesla coil this time I hope. :up: :rofl:
An interesting drive to test would be my A-RAM 100gig sandforce drive with 34nm NAND.Quote:
Originally Posted by Christopher
Given the force 3 was able to sniff the 1PB limit with 128gig of 25nm NAND, my desktop drive would probably smash that with it's 34nm NAND.
But alas, I can't part with it right now :)
What? No, I was gonna use a Taser... why? Is that bad?? :rofl:Quote:
Originally Posted by Hopalong X
@canthearu
I've never ever heard of A-Ram (where are you located in the world?) I've heard of another Hong Kong brand, ASA (that uses SF). And the Chronos Deluxe 60 obviously used 32nm Toshiba, but didn't fare all that well either.
Australia. A-RAM isn't a big brand here either, but one of the online stores here had stock of the sandforce 1 drives and was a bit cheaper then the OCZ drive, so I went with it.Quote:
Originally Posted by Christopher
The Chronos Deluxe 60 might not have faired that well at the end, but hell, it was quick getting there ..... much quicker then my Intel 520 is proving to be!
Well that makes sense. The Samsung 830 64GB was ripping off 11,000GB a day for a while. It's on hiatus for a while, but it should have some good times still ahead.Quote:
Originally Posted by canthearu
The Chronos Deluxe 60 is a beast, but suffers from the SF problem -- it's write speeds are nowhere near peak (for a couple reasons, but if you've ever seen a graph of SF writes you'll understand why). My CD60 was putting in 10,000GB a day host writes, but only 7300GB NAND writes. Hopefully I'll have some drives that beat the doors off it shortly. I got a new Vertex Turbo on the way (which won't be that fast), but who knows what surprises tomorrow may hold? I've been sitting on a few candidates for a while, but I can only run so many drives at once, and the Vertex Turbo and the MTRON (and the 64GB Samsung 830 eventually) are already gonna take up some spots in the endurance rig.
To be fair, I think people get a bit too upset about compressible vs incompressible performance. All 60gig drives are designed fairly cheap, to use as few chips as possible without utterly crippling the controller, so you shouldn't be expecting 256gig drive performance out of a 64gig drive. It doesn't help that virtually drive makers post extremely over the top sequential write values in their specs ... For example, my torqx 64gig manual says 230meg per second sequential writes ... fat chance, it does 18meg or so a second sustained and that is it.Quote:
Originally Posted by Christopher
It isn't really fair to criticise a sandforce drive for slow incompressible writes when it is paired with 64gig of Async NAND, As the Chronos Deluxe show, pair it up with some nice Toggle Mode NAND, and the sandforce controller can do incompressible about as well as any other drive.
That isn't to say the sandforce drives can't go faster when doing incompressible data .... would be nice to see a bit of a boost in this area when the sandforce 3 comes out :)