I'm logging at 10 min intervals and the dec value is more or less changing every time th elog is updated, so it is definently working now
I'm using driver 10.8.0.1003 on SATA III btw.
Printable View
I'm logging at 10 min intervals and the dec value is more or less changing every time th elog is updated, so it is definently working now
I'm using driver 10.8.0.1003 on SATA III btw.
Hmm. Well my drive did update 177 in the beginning (though not correctly). I switched back to rst so I could SE the drive, but Ive written 500GB since hitting 14038, and its still there.
I do think that if there is one bit of advice I would give to 830 owners, it would be to over provision the drive. The Magician software will let you do it with data on the drive (I believe). The 830, especially the 64GB, needs a little extra space I would expect. Taking the 64GB from 59 down to 55 would probably work wonders for keeping the drive in shape. We (or me) may wish to try that at some point.
I'm using 10.5.1015 on an h67 SATA III. But I couldn't average 141MBs when the drive was new and with no static data. Despite the fact I was getting 160mbs writes at the loop start, my avg for the first few days was 110mbs. So really, I'm ahead of the game right now.
I do think that Samsung has tweaked some drive behavior with the new FW. I think they may have adjusted some of the GC/TRIM stuff as well. The drive acts a little differently now throughout the loop. Also, it's quite a bit faster after the SE on the new FW.
BUT...
I tested read speeds... and they're even worse now. But the write results speak for themselves.
That's astonishing speed, and the WA is now close to the other models finally!
Phenomenal :cool:
“Normal” ASU WA after 8 hours (and days of 4k random write abuse)
60GiB (LBA) * P/E Cycles (68) = 4080
Actual writes = 3,937
WA = 1.036
I'm now 100% convinced that 177 is the MWI and P/E cycle count.
http://img842.imageshack.us/img842/9783/asu8hours.png
http://img259.imageshack.us/img259/1315/asssd.png
@Ao1, I wish I could press the "Thank You" button but there's no such one for this forum account yet :)
Now it remains to be seen how much host writes it can sustain, with the new firmware. Hopefully it will last longer than the 470, meaning that the WA is really reduced, not that they simply cheated by slowing down the MWI count without actually addressing the bug that caused unnecessary and excessive WA.
New drive starting on Monday, maybe Sunday night. I'm leaving today for a short-notice trip, and won't be back till then.
But, this 'new' drive has similar seq write speeds to the 830... Almost identical. And it's 64GB too...
I've put it in my laptop to shake it down whilst I'm away... I want to be sure that it's five by five before testing begins. But there have been some initial signs that the drive has some... quirks.
In any event, I think I'll test this drive and the Samsung while waiting for the new drives to launch.
Result! I had delivery issues when I ordered my 830. Out of the blue the retailer (Dabs) just emailed to say they would send me another 830 FOC to compensate! I’ve been so impressed with the 830 I’m going to use it for my OS drive when it arrives.
Anyways, a mini update
Enterprise ASU WA after 6 ½ hours
60GiB (LBA) * P/E Cycles (51) = 3,060
Actual writes = 89
WA = 34.38
Current MB/s: 3.98MB/s
MWI: 74
P/E Cycles 925
Looks like I’ve lost 0.5MB/s on the enterprise workload after the f/w update, but again this is phenomenal (and consistent) performance considering this is about the worst workload you could ever throw at a drive. (Also taking into account that the workload prevents TRIM from functioning).
It is interesting that whether you run the standard ASU workload or the enterprise, the 830 goes through erase cycles at nearly the same rate (cycles per hour). So the time to exhaust MWI is nearly the same with either workload.Quote:
Originally Posted by Ao1
^ I hadn’t got round to looking at that in detail, but I had picked up that the wear rate was similar. A rough and ready way to look at it :D
4 MB/s * 34.38 = 137.52 MB/s
141.09 MB/s * 1.036 = 146.17 MB/s
According to that way of looking at it 4K is slower. I will work it out properly at some stage.
EDIT: I'll post the log file when I get to 3K
Kingston SSDNow 40GB (X25-V)
624.44TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5640
MD5 OK
33.28MiB/s on avg (~49 hours)
--
Corsair Force 3 120GB
01 95/50 (Raw read error rate)
05 2 (Retired Block count)
B1 66 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 685054 (Raw writes) ->669TiB
F1 911725 (Host writes) ->890TiB
MD5 OK
106.92MiB/s on avg (~49 hours)
power on hours : 2613
Todays update.
Kingston V+100
And again it dropped out.....:down:
Intel X25-M G1 80GB
232,3221 TiB
20205 hours
Reallocated sectors : 00
MWI=139 to 137
MD5 =OK
48.59 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=475460http://www.diskusjon.no/index.php?ap...tach_id=475459
m4
225.8037 TiB
826 hours
Avg speed 80.70 MiB/s.
AD gone from 232 to 224.
P/E 3969.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=475461http://www.diskusjon.no/index.php?ap...tach_id=475458
Samsung 830 64GB Update, Day 37
FW:CXM02B1Q
GiB written:
234126.89
Avg MB/s
118.88, up from 69.34
PE Cycles
14109 Can't power cycle the drive until I return home on Sunday night.
Reallocated Sectors
40960
20 Blocks, holding steady
899 Hours
https://www.box.com/shared/static/hi...k6ub84n5e2.png
https://www.box.com/shared/static/tt...6ptgibdyrr.png
https://www.box.com/shared/static/vs...xfakog2ygc.png
Notice the write count from yesterday is quite a bit higher after the SE erase. Today's write count still has 3 hours left in the day. It was averaging around 5000GB per day recently.
So I had to leave town unexpectedly to attend a funeral, and I'll be back on Sunday night. Until then, I won't be able to power cycle the drive to get PE cycles. Unlike some people I could name (...cough... Ao1), my drive doesn't update PE cycles while powered.
But a new drive gets thrown in the torture chamber this Sunday! A joyous occasion.
The increase in speed after the FW upgrade + SE is remarkable. Not only that, but it seems that the drive isn't degrading in speed as it did before.
@B.A.T
The MWI of the M4 is really funny - It's a linear rotation between 0 and 255 and the next exhaustion of MWI would be at 7680 P/E :D I wonder if Crucial would honor the RMA when then engineers see a positive value (between 0 and 100) ^^ Do you think the 0009 firmware has improved the wear leveling algorithm for real, compared against the previous one tested with 0002?
When would you do a data retention test?
I lost around 4 hours due to Window’s auto rebooting after an update :mad:
Host writes: 9,205 GiB
MWI: 72
P/E Cycles: 1,011
POH: 137
Edit, looks like the rest helped the M/Bs
http://img194.imageshack.us/img194/7205/updatend.png
I don't know. It might have. Fw 0009 writes slower than 0002 but the WA on the 0002 was 1.09 and for 0009 it is so far 1.02.Quote:
Originally Posted by minpayne
I had an involuntary retention test during christmas. All ssd were without power for 12 and 24 hours due to a storm and powerloss.
I don't think WA was ever really a problem with the M4, even with the earliest FW (0001). In fact, even on a sector-aligned XP setup, the M4 seemed to have really good WA. Obviously, I don't recommend running a drive like that, but I did, and it was pretty amazing.
The increase in read speeds with 0009 is certainly worth it, even it WA actually increased over earlier FWs. My M4 was running 0001FW and the upgrade to 0009 was incredible. The drop in write speed is certainly a good trade-off for the increase in read speeds.
The 830 on with it's new FW seems to be unassailable now. It's been two days, and there has been no slowdown like there was on 01B1Q. If anything it's even faster over time, not slower. I expect it should hit 10000GB today, and possibly more tomorrow. While it's not as fast as it should (and could be), I can't complain. I can't believe that there have been no more reallocations. It should have popped a couple more blocks by now, but it's been holding steady for quite a while at 40960.
Samsung 830 64GB Update, Day 38
FW:CXM02B1Q
GiB written:
241217.21
Avg MB/s
120.54, up from 118.88
PE Cycles
14109 Can't power cycle the drive until I return home on Monday night.
Reallocated Sectors
40960
20 Blocks, holding steady
915 Hours
https://www.box.com/shared/static/g3...i9bdllnrkv.png
https://www.box.com/shared/static/0e...5rhhufa70g.png
I can't be picky about when I get in updates way up here in the middle of nowhere. Just getting my remote desktop app working consistently is hit or miss.
Everything seems good with the 830 today, but I really wish I could get those extra 20MB/s I'm missing on the average. Every once in a while, for a few seconds every three loops, instantaneous speed jumps up to 160MBs for a short time.
Kingston SSDNow 40GB (X25-V)
627.04TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5663
MD5 OK
33.09MiB/s on avg (~72 hours)
--
Corsair Force 3 120GB
01 92/50 (Raw read error rate)
05 2 (Retired Block count)
B1 64 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 691605 (Raw writes) ->675TiB
F1 920442 (Host writes) ->899TiB
MD5 OK
106.91MiB/s on avg (~72 hours)
power on hours : 2636
Getting close to 900TiB :)
I'll let it run until WRD stops decreasing before doing the data retention test.
--
http://www.ssdaddict.com/ss/Endurance_cr_20120112.png
I am using my 830 for normal work for more than a week now, Total LBA'a written is ~255 GiB, 177 raw value is 7. What is kinda strange for me the 235 value, which is "POR Recovery Count" according to the Samsung SSD Magician. Strange that Christopher has only 31 for the same SMART record. Anyone knows what "POR Recovery" means?
Thanks! :)
Forgot to write that my 235 value is 16.
Gsmartcontrol reports that attribute as super capacitor health, though everything else refers to it as POR recovery. I dd some research and could not determine what is was.Quote:
Originally Posted by adrianu
POR looks to be related to caching (DRAM) and so the capacitor is part of that subsystem.
I would't worry at all, if it reaches some threshold it would be something to look out for though.
I think the 830 is pretty good drive. Assuming the drive does well in the endurance test, the combination of features, speed and the super capacitor make for one hell of a drive. It's could end up like the Intel 320 series, except fast.
I wonder if 235 attribute is actually the 830's "unsafe shutdown" equivalent. I won't be able to test that until I get back, but perhaps Ao1 or Anvil could try unsafely shutting an 830 down and see if 235 increments.
I do not think the 830 has a supercapacitor. The way gsmartcontrol works is if it does not have a specific model in its database, it uses entries from a similar model. In this case, another SSD that did have a supercapacitor used that same attribute number for its supercapacitor health.
I cannot find any documentation on the SMART attributes for the consumer 830, but I did find a datasheet on the PM830
http://www.samsung.com/us/business/o...30-mobile.html
http://www.samsung.com/us/business/o...I_Spec_0.2.pdf
Code:ID Attribute Name
5 Reallocated Sector Count
9 Power-on Hours
12 Power-on Count
177 Wear Leveling Count
179 Used Reserved Block Count(total)
181 Program Fail Count(total)
182 Erase Fail Count(total)
183 Runtime Bad Count (total)
187 Uncorrectable Error Count
190 Airflow Temperature
195 ECC Error Rate
199 CRC Error Count
235 POR Recovery Count
241 Total LBA Written
I was pretty sure that it did have a supercapcitor -- or perhaps several smaller capacitors. But I could be wrong -- I usually am.
I seem to recall seeing the capcitor on a PCB shot of the 830 -- I wasn't just going by what GSmartControl said. The Magician software refers to the attribute in question as POR recovery count as well. As I said before, I'm away for a couple days, so I can't test this, but I believe that POR count might actually increment with unsafe shutdowns. I believe that attribute has increased on my drive a few days ago when I was SEing the drive and updating the FW, at which point I had to remove and reconnect the drive to SE it. I can check the SmartLog when I get back to see when it increased.
EDIT
No supercap/cache protection system on the 830 - consumer or OEM. Their 825 eMLC drive does have some kind of system on it. I had seen a picture of the PCB and saw what I thought was some kind of capacitor system, but it isn't. I bought a 120GB 320 because I didn't have a G3 Intel aside from the 311, and I know it has a couple caps on it instead of one "supercap". But that got me thinking, if the 830 ended up being that robust and that fast with cache protection, that there wouldn't really be a reason to get a 320 anymore. I'm still impressed by the 830, even with the initial problems I had, and the drive has operated flawlessly if not always as fast.
I've been looking back at the smart data every day, and I think that 235 is basically unsafe shutdown count. I went and back and looked at the SMART screen pictures, and for the two weeks I was gone at the end of December it was at 18. Then the day I did the FW update it increased to 31 from 21 -- I roughly had to cycle the drive by unplugging it about 10 times that day.
Host writes: 9,730 GiB
MWI: 66
P/E Cycles: 1,206
POH: 162
MB/s: 6.09