Why is the M4's wear leveling count at 828 now? The Samsung is only at 101. Perhaps they calculate differently?
Printable View
Why is the M4's wear leveling count at 828 now? The Samsung is only at 101. Perhaps they calculate differently?
I was wondering about the same thing.
In my case it's easy to calculate. 64 020 803 584 byte*828 =48,21 TiB
With an WA of 1.01 it looks correct. Yours on the other side......
Is there no MWI for the Samsung 830? I've also read somewhere that the temperature of that SSD is a bit high, hence not recommended for small laptops where cooling might be a problem.
Yes. Perhaps it's a straight average? Maybe it's pe cycles / 10? Perhaps it's actually in Klingon.Quote:
Originally Posted by B.A.T
I don't see how it's possible to have over 1000 times the drive's capacity with slightly over 100 PE cycles. Maybe it's magic.
For real.Quote:
Originally Posted by minpayne
It gets pretty warm, but so did the Mushkin Chronos Deluxe I was testing before the Samsung. The toggle mode NAND models use a good bit of power, both from the NAND and controllers. The both should have thermal pads to conduct heat into the chassis. My Samsung 830 is actually hanging out of the back of my test system, so it's temp readings are from it's own heat and not the system. I should think it would be fine in a smaller laptop chassis as it only gets hot when you are writing to it as fast as you can for days on end. Laptops tend to get hot anyway, so it's more likely that a laptop heats up the Samsung. Indilinx drives and Intel drive don't get appreciably hot, but then, they use very little power. All of the 6gbps controllers will use more juice anyway, but the toggle mode NAND (Toshiba and Samsung) seem to use the most power on a per-device basis. But boy, are they fast.
Concerning SSD power use, newer drives like the Samsung are using as much power as 2.5" HDDs. But like a SB processor, they don't use much power at idle, then use larger amounts of power while completing work, then return to idle. Because they are so much faster than mechanical drives, they spend one twentieth the time doing the same amount of work at max power which means they can get back to idle as fast as possible. So the drive might heat up for a minute or two at a time, but shouldn't ever get problematically hot unless you're doing what I'm doing.
EDIT
If you look at the whole wear leveling values for the 830 you get 97/97/101. It's 73/73/838 for the M4. Maybe I should add some more static data to see what happens.
Hey guys, just got in back to work today...was out sick yesterday.
I'll try and see if I can get the M225 back today.
EDIT: No go. Can't seem to be able to D-flash FW to any version. Keeps saying "ERROR: Erase Failure\High" then "data corrupt" "see good.bin and bad.bin". Don't think the NAND will let itself get flashed. Or should I say the FW won't let the NAND get flashed with the high erase counts (PE).
I need RyderOCZ to supply me a special FW to overlook the high writes and just flash! LOL :)
It's not impossible, if the drive is packed with NAND it will produce heat (my Intel 600GB can get hot) and the Samsung is on the small side, really small.Quote:
Originally Posted by minpayne
I haven't checked my Samsungs yet but will do.
You should keep some 15-20GB of writes per loop (or thereabouts) on the 64GB.Quote:
Originally Posted by Christopher
I'm using 12GB free space as a minimum on both drives.
The PE counter (177) looks OK, it's just on a different scale, if you get the chance you could try catching/creating a screenshot when the attribute changes and compare to F1.
My Intel 600GB is a lot cooler than my M4 512GB, when both running the Endurance testing in AST at around 80-100MB/s fill. The coolest one is the Intel X25-E 64GB - my hand cannot even sense that it is powered on under stress test.Quote:
Originally Posted by Anvil
I'm now thinking about getting a Samsung 830 for my laptop but I'm concerned with the heat I've read so far.
Anvil,
I was using 12GB min free, but from 16 down to 12 average writes dip into the 77MB/s range after a few loops. That's one of the reasons why I was thinking of adding some more static data.
Samsung 830 64GB Update, Day 8
FW:CXM01B1Q
GiB written:
70706.50
Avg MB/s
107.86
Per-day average:
9088
PE Cycles
116
Reallocated Sector Count
16384 (8 blocks)
194 hours
https://www.box.com/shared/static/dy...br5phz845b.jpg
https://www.box.com/shared/static/hi...q1flr1s6xk.png
I was watching last night when the PE cycles hit 110. The CV/worst value hit 96/96 as well. That would mean it should hit 0 at 2750 Wear Leveling Count.
1 in the raw value roughly equals 609GiB, so 2750 * 609GB would equal 1,676,219.83GB
Yup -- 1.68PB to PEexhaustion? I don't think so. I'll keep trying to figure out what it means.
Todays update.
Kingston V+100
289.7360 TiB
1360 hours
Avg speed 25.40 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=471773http://www.diskusjon.no/index.php?ap...tach_id=471770
Intel X25-M G1 80GB
128,3653 TiB
19579 hours
Reallocated sectors : 00
MWI=26 to 21
MD5 =OK
51.35 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=471772http://www.diskusjon.no/index.php?ap...tach_id=471771
m4
53.5538 TiB
195 hours
Avg speed 81.00 MiB/s.
AD gone from 73 to 69.
P/E 933.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=471774http://www.diskusjon.no/index.php?ap...tach_id=471769
@BAT
So, December the 25th for the Intel X25-M G1 and New Years day for the M4 :)
(according to SSDLife)
I need to install SSDLife onto the current test-rig, it's currently sitting on the AMD rig I used until late this summer.
--
The Intel just got past 550TB :) and the F3 will be past 700TiB by tomorrow morning.
Kingston SSDNow 40GB (X25-V)
550.87TB Host writes
Reallocated sectors : 05 14
Available Reserved Space : E8 99
POH 4996
MD5 OK
32.05MiB/s on avg (~72 hours)
--
Corsair Force 3 120GB
01 89/50 (Raw read error rate)
05 2 (Retired Block count)
B1 50 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 535621 (Raw writes) ->523TiB
F1 712916 (Host writes) ->696TiB
MD5 OK
102.75MiB/s on avg (~72 hours)
power on hours : 2032
(for some reason both drives have had a slowdown but they are steadily increasing on avg throughput)
--
@bluestang
Looks like I'll have to update the summary!
Looks like an exciting holiday this year :)Quote:
Originally Posted by Anvil
I bet that you can disregard those dates :), still it can be exciting, anything can happen of course.
I planned on starting my retention test from mwi=1%. Stop every 100GB and try like you did with the X25-V.
Those Intel's 40GBs are a model of good behavior. Maybe if you're writing slow and steady, you can do so almost indefinitely.
The 40GB Intels are writing as much/fast as they can, they are slow though :)
I have considered making an option for "slowing down"/controlling writes.
There are lot'a of possible options to consider though, like setting a fixed number of MB/s or a fixed number of GiB per hour or TiB per day and so the options will make it possible to have a few pauses.
These could be useful options but you can of course run the test just like before, w/o pauses.
One mystery solved --
The Samsung Toggle NAND uses 8K Pages, 1MiB blocks. the reallocated sector count really are sectors. Right now, the Samsung has 10 replaced blocks and reports 20480 reallocated sectors.
512 bytes * 20480 = 10485760 bytes, or 10MiB. Each block is 1MiB, so 10MiB of blocks have been flagged as bad and replaced.
Kingston SSDNow 40GB (X25-V)
552.24TB Host writes
Reallocated sectors : 05 14
Available Reserved Space : E8 99
POH 5008
MD5 OK
32.16MiB/s on avg (~84 hours)
--
Corsair Force 3 120GB
01 90/50 (Raw read error rate)
05 2 (Retired Block count)
B1 49 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 539011 (Raw writes) ->526TiB
F1 717426 (Host writes) ->701TiB
MD5 OK
103.30MiB/s on avg (~83 hours)
power on hours : 2044
The Force 3 is now idling and will do so for a few more hours in wait for a data retention test.
--
Samsung 830 64GB Update, Day 9
FW:CXM01B1Q
GiB written:
80990.91
Avg MB/s
105.43
Per-day average:
8990GB
PE Cycles
129
Reallocated Sector Count
20480 (10 blocks)
8K pages, 1MiB blocks
219 hours
https://www.box.com/shared/static/ii...yjbm4y5lvd.jpg
https://www.box.com/shared/static/e9...6ahx11t8l9.png
The min free space is set to 12GB. If you look at the ASU shot above you'll see the instant MBs in the 60MBs range, but the average hasn't gone down too much (yet)
Measured WA -- 1.05
Since moving to 12GB min free from 16GB, the drive was only able to write 8284GB, about 700GB less than the previous daily average.
My Last Official M225->Vertex Turbo 64GB Screenshot and Stats:
http://img851.imageshack.us/img851/4...texturbo12.png
879.17 TiB (966.66 TB) total.
~2245 hrs (Torture), 3304 hrs (Power-On).
17092 Avg. Raw Wear.
B8-Initial Bad Block Count at 8
C3-Program Failure Block Count at 2
C4-Erase Failure Block Count (Reallocations) at 25.
C5-Read Failure Block Count (uncorrectable bit errors) at 27.
On 12/08/11 Drive threw 16 more C5 for a total of 43.
So a total (B8+C3+C4+C5) of 78 Bad Blocks.
I was able to write down SSD Life total of 901479.9 GiB (880.35 TiB / 967.96 TB) before it died on 12/08/11.
This drive managed 116.48 MB/s over the entire endurance test. :clap:
*** M225 -- R.I.P. December 8, 2011 at 968 TB of Writes ***
Thanks for all your work on this bluestang!
(first post updated)
--
The Corsair Force 3 has been disconnected for about 6 hours, another 48 hours and it will be back online.
Bluestang,
Are you going to put the other M225 into service? Or put it next to the expired one in the SSD Hall of Fame?
Did you ever see the RAW value increment by less than 4096? In the data you posted, I thought it went by at least 4096 increments.Quote:
Originally Posted by Christopher
4096 * 512 = 2 MiB
Todays update.
Kingston V+100
291.9157 TiB
1385 hours
Avg speed 25.39 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=471914http://www.diskusjon.no/index.php?ap...tach_id=471911
Intel X25-M G1 80GB
132,7932 TiB
19604 hours
Reallocated sectors : 00
MWI=21 to 15
MD5 =OK
51.32 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=471913http://www.diskusjon.no/index.php?ap...tach_id=471912
m4
60.5541 TiB
220 hours
Avg speed 81.11 MiB/s.
AD gone from 69 to 65.
P/E 1055.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=471915http://www.diskusjon.no/index.php?ap...tach_id=471910
@Bluestang
R.I.P M225
You did a good job babysitting it. To bad it didn't last all the way to 1 PiB.
Yes. It increments in 2048. That's what I thought as well initially, but it was just because two blocks went out at once. Samsung's web page lists the 8K pages 1MiB block size. If you look at the smart data from today, the number of replaced blocks is listed as 10. Still, I'm a little confused by the erase fail and total runtime bad block counts. It does seem like one doesn't increment without the other.Quote:
Originally Posted by johnw