Kingston SSDNow 40GB (X25-V)
555.03TB Host writes
Reallocated sectors : 05 14
Available Reserved Space : E8 99
POH 5032
MD5 OK
33.54MiB/s on avg (~18 hours)
--
Corsair Force 3 120GB
It has been disconnected for 18 hours.
Printable View
Kingston SSDNow 40GB (X25-V)
555.03TB Host writes
Reallocated sectors : 05 14
Available Reserved Space : E8 99
POH 5032
MD5 OK
33.54MiB/s on avg (~18 hours)
--
Corsair Force 3 120GB
It has been disconnected for 18 hours.
Thanks! ...and same to you since this would not be as possible without ASU. :up:Quote:
Originally Posted by Anvil
Thanks! ...I might mount this one on a plaque and hang it in my office. :)Quote:
Originally Posted by Christopher
Not sure yet on running the other one, if I do it will be with FW 1.7.
Thanks! ...and yeah, I'm a little upset with not reaching 1 PB. :shakes:Quote:
Originally Posted by B.A.T
If I do put the other M225 into the test, it won't be till after the New Year.
So I modified the Min GB Free the other day. It took a while, but the 830 is now unable recover its speed. I ran the Magician Optimization 6 times, but no increase in speed. I'm going to have to SE.
I was using 18.3GB of static data, 16GB min Free, so that leaves 26GB per loop. If I move it down to 12GB Min Free, it can't keep its speed up, and worse, can't be fixed.
https://www.box.com/shared/static/tx...8b69uaqlh6.jpg
Before SEing the drive, I tried a few things. The Samsung Magician's performance optimization is worthless. Those numbers above are abyssmal, and it all started when I lowered the min free space to 12GB. It took about a day, but the controller seems to have backed itself into a corner here. Something is wrong though... it's not fixable with traditional means, so I'm going to be forced to SE it. Just deleting the volume didn't do much. Large sequential writes didn't do much. Samsung's software didn't do anything, even when run 8 times at about 4 minutes each.
EDIT
https://www.box.com/shared/static/xu...2qqrt2qezy.jpg
This is after a SE. It looks pretty sad.
Major update. For real this time. Sort of...
but first, today's update:
Samsung 830 64GB Update, Day 10
FW:CXM01B1Q
GiB written:
87061.03
Actual Writes:
87476.6
Avg MB/s
81.54 down from 105MBs
Per-day average:
8706GB
PE Cycles
138
Reallocated Sector Count
20480 (10 blocks)
8K pages, 1MiB blocks
243 hours
https://www.box.com/shared/static/ub...g1yq1pnntm.png
https://www.box.com/shared/static/ti...j1cu94xdgr.jpg
Okay. Notice the 138 PE cycles?
From the reboot, or the SE, things changed. You can see the before and after SE CDM numbers.
Now look at this:
https://www.box.com/shared/static/ip...p7fzbkt7q1.jpg
The PE cycles are now at 5444. That's 1/1/5444.
So the PE cycle/wear leveling does work properly and can be used as a life indicator.
But I can't get performance back to near-new levels to save my life.
That gives a write amplification of 4.00 : 5444*64*1024^3 / ( 85.0205*1024^4)Quote:
Originally Posted by Christopher
The 470 was about 5.0. It seems Samsung may have tweaked the firmware algorithms slightly.
Truth it, I don't put a lot of faith in either number (100+ PE cycles, then a jump to 5444). Looking at the total writes to the total count of write sectors, you don't see much WA. Around 1.06 when I calcluated yesterday.Quote:
Originally Posted by johnw
I'm more concerned that a SE didn't fix the profound performance drop.
One possible, if not probable, explaination is several of the cells are borderline and the controller is having a hard time dealing. Maybe the Samsung SE isn't real SE. Who knows? I deleted the volume first and that made no performance difference. See the a couple posts up for before and after pics.
No, the WA is definitely not 1.06. The 5444 erase cycles makes sense (and 100 is definitely wrong) since the normalized value has already reached threshold (it must have done at either 3000 or 5000).Quote:
Originally Posted by Christopher
Try to reboot..Quote:
Originally Posted by Christopher
Samsung 470 at for example, this behavior is a known bug, similar to the transition mode of the controller in sata 1.5Gbps
You could be right, but my gut tells me neither wear leveling count could be accurate. And I still can't account for the crazy performance drop. The drive didn't go from ~100 PE cycles to over 5000 overnight, it happened instantly. So you could be right, I just have no way of knowing.Quote:
Originally Posted by johnw
The PE cycles havent increased all day either since hitting 1/1/5444... the threshold is 0, but maybe it's at the end of the line.
Right now it's on track to write 200MB an hour... that's not good.
I meant that the actual value of 5444 erase cycles makes sense. The fact that it stuck around 100, then increased to 5444, and now is not increasing, does NOT make sense. That certainly seems like a firmware bug.Quote:
Originally Posted by Christopher
Combined with your weird write-speed decrease, which could be another firmware bug. I suppose it could also be some sort of throttling that comes in after the SSD depletes MWI, but my first guess is a firmware bug.
I may try re flashing the fw but the Samsung software may not let me. And it was slower yesterday... The SE helped a lot, but its still nowhere close.
UPDATE
I SE'd it again. Put a partition on it, and ran CDM again:
https://www.box.com/shared/static/ec...sevk4l36yb.jpg
The writes are bad but where did the reads go?!
Running a 100MB test would normally be on the small side and as the Samsungs have a cache that is larger you should at least do 500MB.
I'd let it idle for a day or so, it might rely on background GC although a SE should normally take care of all such anomalies.
Could you try running HDTune Read Benchmark using 64KB and 4MB?
The earlier post first documenting this used CDM 1000mbs. I was just in a hurry. With the many subsequent ones.Quote:
Originally Posted by Anvil
I'm film the HDTune.
It really looks to me like the drive throttles down its writes because its past the MWI... Read speed should be unaffected though when testing CDM 1000mb.
I'm very curious though about how much total writes the drive can take.
With respect to the CDM numbers, look at the past couple of posts with CDM shots. The first two were with 1000MB, 5 reps -- and the best numbers are being displayed. One of 5 would be much better, and the other 4 would range from low to super low. As far as the writes go, they look better than the reads, but it's not sustainable. Running the endurance loop, the beginning loop instant speeds start at 100 and drop into the 50MBs range.
Secondly, I SE'd the drive many times, in addition to multiple Magician performance optimization runs. Then, just grasping at straws, I tried one of the secure drive wipes in Acronis Drive Cleanser (the fast one that just writes zeros to every LBA). Sequential writes seemed to help at first, but didn't really do anything.
I tried running the drive with Intel RST and MSAHCI, and on two different systems.
I ran HDTune several different ways, but regardless of which benchmark I run, there is something wrong here.
64KB
https://www.box.com/shared/static/gu...omdof2yuc5.jpg
4MB
https://www.box.com/shared/static/i5...od54n4oqz5.jpg
I will let the drive idle the rest of the day, but I don't see why that would work but secure erasing doesn't.
Then it def looks like something is wrong, read speeds should be unaffected...
if you look at the above 4MB hd tune shot, the depressed reads roughly correspond to the amount of static data on the drive. However, most of the CDM shots are with no data on the drive.
Man, the days just seem so boring for me now for some reason. :shrug: LOL
Would you like to buy a Samsung 830 SSD, gently used?Quote:
Originally Posted by bluestang
Christopher, your results really make me regret buying a Samsung 830 128Gb and not going for the Crucial M4. Can it be that this drive is so bad that after exhausting the MWI it drops to ridiculously slow speed for BOTH write AND read?
What happened I'm not sure. But the drive is awesome.Quote:
Originally Posted by iceblade
Are you planning on writing 128TB a week? If not, you should be fine. Somehow, when I made it so more of the drive was being written to each testing loop the drive got in a bad way. But I also think it has to do with writing so much with out a reboot.
The 64GB 830 has written 90TB so far, so some drives will take it in stride while others won't.
But this drive is hard up at the moment. This is after idling for six hours
https://www.box.com/shared/static/ti...pz1qukvt1q.jpg
No, but I'll trade you for an even more gently used M225! :rofl:Quote:
Originally Posted by Christopher
I actually just got a 60GB Vertex EX SLC in the mail today -- brand new, 1.3FW -- for $66... if I didn't think it would take either excruciatingly long to endurance test it, or die in an embarrassingly short time I'd do it in a heart beat... it gives your M225 Turbo a run for it's performance money.Quote:
Originally Posted by bluestang
I also have a new Imation S-class SLC coming in the mail, but with 120 4K write IOPS, it's probably nothing to get excited about. WA would go through the ceiling with that drive, and I think I could kill it pretty quick.
Either way, I'm looking past the 830 at this stage. Maybe I can get it back to health... maybe not.
EDIT
I SE'd the drive again with HDDERASE, and it made no difference.
An endurance loop with no static data (just after the SE) on the drive is just as slow as before. CDM still shows terrible results.
I have a theory... but it's not a good one yet. I'm going to continue with the testing.
@Christopher
Could you try formatting the drive?
Make sure to deselect the Quick Format option as it will make a huge difference, you can stop at 10-20% and run ATTO to check if it works for you, you need to perform a quick format if you abort the full format in order to run tests of course.
(a quick format just won't do sometimes, even if it should include a TRIM)