What's wrong with the Turbo?
Printable View
What's wrong with the Turbo?
Nothing, I hope ;)Quote:
Originally Posted by Anvil
I'll post it later. I was upgrading ASU from Beta 9 to Beta 11, so I just did the Samsung.
OCZ Vertex Turbo 64 Update Day 14
TiB 86.7804
GiB 88863.11
82.87 MBs Avg
Avg Erase Count
1595
MWI 69 down from 71
1 Program Fail
29 Erase Fail (up from 28)
0 Read Fail
316 Hours
https://www.box.com/shared/static/cn...8o6un125hd.png
-----------------------------------------------------------------------
Those erase fails are going quick. You have to pop that Turbo open when it dies.
Yes, yes they are.Quote:
Originally Posted by bluestang
But all of the factory bad blocks were laundered, and thrown back into the good pool, so really I think of it as only 11 erase fails... Based on similar drives, like my Vertex LE 100, 128 Turbo that I've peeped out, it's gonna look just like the original. Which is what I'm pretty sure it is, just tarted up with some new FW and a new plastic dress.
I know there is a way to determine actual WA on a SF drive, but that it's covered under strict NDA (though surely someone has figured it out by now). It's possible that the Chonos D and F3 could have much higher WA than it would appear, and perhaps its hidden away in the Smart data for anyone who knows what they're looking for to see.
Maybe there was a good reason that the original SF drives uses 28 percent OP.
Yes, forgot about the FW and what it did with the initial bad blocks. Hopefully it will go quite a distance.Quote:
Originally Posted by Christopher
I'll have to check my M225 data when I get to work tomorrow to see where I was TB wise with 11 erase fails.
I wonder how it tracks with yours. I think my drive is good bit slower, but yours was run without TRIM for quite some time.Quote:
Originally Posted by bluestang
I did look at your drive's last stats and saw that your 1.6FW drive and my 1.7FW are using the same number of PE cycles vs. GB written, just a bit over 56GB/PE cycle.
The 830 is going down for a retention test as of 10:53PM GMT -6 31 Jan 2012.
I’m inclined to agree. Compression obviously helps but something else appears to be offsetting the benefit. At a guess it is the fact that SF (unlike anyone else) do not use DRAM.Quote:
Originally Posted by Christopher
Nice contrast against Ao1's! I bet yours is going to be dead for sure if powerless for a week or so, while his would survive the 3-month enterprise standard :)Quote:
Originally Posted by Christopher
Any news of that Crucial C300 ? Anyone got another one that we can test ?
Quote:
Originally Posted by Christopher
Ok, for comparison...Quote:
Originally Posted by Christopher
Yes, mine ran on XP for 16 days with 53.38 TB written in that time. MWI was 64 and Avg Erase 1830. Ran on Windows 7 from that point on.
I had 8 Initial/Factory Bad Blocks to start with. I threw my first Erase Failure at 87.51 TiB with MWI 49 and Avg Erase at 2571.
At 11 Erase Fails I was at 701.57 TB and Avg Erase 12727. Also Program Fails was at 2.
.....:shrug:......Quote:
Originally Posted by bluestang
Yeah. It could be a refurb, that much is true. But after the factory burn in, by the time the drive had a partition on it, it already had additional blocks bad at runtime. That's never a good sign. I spent some time asking around the OCZ forums, but I didn't get anywhere. People thought that I was just retarded for wanting to know about this drive's behavior. It was at 97MWI out of the box, but just from the couple of erase fails.
I also bought a Vertex EX SLC 64GB from another place at the same time as the Turbo. It was at 89MWI out of the box, and had 209 Initial bad blocks on it's Samsung SLC. But it was on 1.3FW, had a metal case, and some drives did ship with wrong MWI just because of early FW. I dflashed it to 1.7 and it's quite impressive.
@minipayne,
Seriously, a week? I give it three days at the outside. It's writing about 11600GB a day now. I did some benches, and it's actually hitting 172MBs 4MB writes in ASU. Reads... well, they're getting slower still. I think Samsung accidentally throttled reads instead of writes.
@Ao1,
Given my 120GB Chronos Deluxe's performance profile, it's sustained writes are somewhat ridiculous. I think you could look at it's internal WA, perhaps on a workload basis, or maybe overall, through examination of a variety of attributes (that SF will disclose if you sign their NDA).
The SF processor is doubtlessly doing something fruity internally when bombarded with massive amounts of writes.
Interesting. Can't wait to see how far your VT goes.
Kingston SSDNow 40GB (X25-V)
680.89TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6136
MD5 OK
32.79MiB/s on avg (~148 hours)
--
A bit busy these days, will try to catch up later this week.
Anvil
I love it. The old "turtle" just keeps chugging along.
It may be the only one to surpass 1PB by a large margin. Eventually. :up:
The X25-V has written it's own capacity 17,430.784 times. It's probably over 18,000PE cycles. :clap:
OCZ Vertex Turbo 64 Update Day 15
TiB 94.6472
GiB 96918.77
83.56 MBs Avg
Avg Erase Count
1739
MWI 66 down from 69
1 Program Fail
32 Erase Fail (up from 29)
0 Read Fail
343 Hours
https://www.box.com/shared/static/48...fn684yv0tl.png
-----------------------------------------------------------------------
I'm taking a trip over the weekend, so the 830 resumes when I get back.
It's somewhat close to 18K times it's own capacity :)Quote:
Originally Posted by Christopher
Let's hope it lasts for a year :cool:
Slow is the way to go.
The thing is that it really isn't that slow.
I'm using the X25-V as a boot drive on 3 different setups and 99% of the time there are no signs of the capped write speed, random writes are great (for OS usage) and I rarely install apps so copy speed is not an issue :)
I will however be switching to other drives as they are low on capacity, 64GB or 80GB will do for 2012.
edit:
How are you doing B.A.T, it's been a few days since your last report :)
Anvil,
I still use my Vs, even though I have have many faster, larger drives just laying around. And it's not like I have a lot of systems, either; Just a desktop, laptop, and endurance rig.
I am of the opinion that if you want the most TBW, either get a slow writer or artificially cap the write speed in this test. If I capped the 830 at 5TB a day, I think it could make it well over a PB; It would take longer, but you'd get more TBW. You can write faster, but get less TBW.
The X25-M of BATs could last until the next ice age.
-------------------------------------------------------------------------------------------------------------------------
I also have a new MTRON 16GB in on the way, so I hope to have an SLC drive back in the test late next week.
It's a 7000 PRO 16GB 2.5". I have a 16GB 3.5", but it won't really fit in the testing rig. I have pictures of it's pcb in case anyone is dying to see what it looks like inside.
Try and take out the X25-V and see if it dies just like the others. I have noticed that as soon as you take out these drives and leave them for like a week unpowered the NAND cells loose charge and your SSD becomes a paperweight. So much for the read only after the MWI is over.
I've been on a work trip and I'd planned to update during this but with only edge mobile coverage I couldn't use teameviewer.Quote:
Originally Posted by Anvil
On the otherside work was very nice :cool:
http://www.diskusjon.no/index.php?ap...tach_id=477801
Todays update.
Kingston V+100
http://www.diskusjon.no/index.php?ap...tach_id=477806
It dropped out again. I'll get it up running when I'm home tonight.
Intel X25-M G1 80GB
308,22 TiB
20700 hours
Reallocated sectors : 00
MWI=121 to 116
MD5 =OK
46.67 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=477803
m4
354.6262 TiB
1325 hours
Avg speed 81.41 MiB/s.
AD gone from 167 to 148.
P/E 6247.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=477802
Biggest thing with these drives is that nobody is stopping at MWI=0 where according to ISO standard- they should retain data for a year (or 3 months for enterprise?) they are going WELL beyond MWI=0. and IIRC, the x25-v went through a week data retention test in the last month and came through with flying colours.Quote:
Originally Posted by bulanula
Well I think we ought to test the retention as well not only the write endurance. I bet that the X25-V will be totally dead after one week without any power going to its NAND.Quote:
Originally Posted by DragoonXX
Maybe we should see how much past the MWI you can go while still being able to read your data for 1 year after etc. ?
bulanula
The thread started out as an Endurance test, not a retention test.
If we hadn't started out the way we started the thread wouldn't have evolved the way it has, awareness of retention testing is one if the things that has come out of the testing, so far.
There is some retention testing (have you stopped reading the thread or is it just bits), that's how several of the contestants dropped out of the test.
Ao1 is having a 3 month retention test as well.
As for the 1 year retention test, just bring me a time machine and I'll be happy to do some testing :)
If you'd like to enter the test the price of the SSD is just petty cash, the commitment lies in spending the hours and for some of the contestants using their main rig for testing so please don't use "we" until you actually start testing some drive.
Anvil
Wish I had access to a "Thank You" button. :up:
Never have figured out why I don't have one.:shrug:
Come back on the 26th April and you will see if the 830 has been able to retain data after three months of no power after getting to MWI 1.Quote:
Originally Posted by DragoonXX
Thanks!Quote:
Originally Posted by Hopalong X
As for the "Thank You" button, you need 100 posts IIRC.
B.A.T.,
Nice picture!
Thank you!
Some days winter shows herself from her best side :)
Kingston SSDNow 40GB (X25-V)
686.05TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6182
MD5 OK
32.79MiB/s on avg (~193 hours)
--
http://www.ssdaddict.com/ss/Enduranc...r_20120203.png
OK. Looking forward to 26 April 2012 for the 830 retention results.
Todays update.
Kingston V+100
357.2993 TiB
2169 hours
Avg speed 24.49 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=478087
Intel X25-M G1 80GB
315,59 TiB
20750 hours
Reallocated sectors : 00
MWI=116 to 114
MD5 =OK
40.16 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=478086
m4
368.7760 TiB
1376 hours
Avg speed 80.79 MiB/s.
AD gone from 148 to 140.
P/E 6493.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=478088
I'm not dead -- I'm just on a trip. I'll try to find out what is going on with the Turbo.
UPDATE
The system is on and running, but I haven't been able to remote in for a few days.
I hope you haven't missed the recent launch of the Intel 520 SSD ;)Quote:
Originally Posted by Christopher
I'm already over it. I cancelled my order two weeks ago (they've been shipping here in small quantities for some time now).Quote:
Originally Posted by bulanula
I'll get one, and maybe even soon, but more SF drives are not what I need.
What a waste of a launch anyway! SF controller? for Pete's sakes!Quote:
Originally Posted by bulanula
Intel has probably fixed SandForce, but that doesn't mean I'm drooling all over myself. The X25-V,M, and E are the standard bearers of excellence, and you will have to pry them away from my cold, dead hands.Quote:
Originally Posted by devsk
I'm curious about the RAISE being disabled and it's potential ramifications. Having RAISE on the Force 3 and the Chronos D (64gbit devices didn't get it at 60GB, but the CDX60 did with 32gb devices) didn't seem to help, and Intel has chosen to just OP the drive instead. I believe RAISE was primarily for using lower quality NAND in a drive, but even the 320 uses a redundancy scheme. It's unclear whether SF drive are benefiting in any way from having RAISE.
Obviously Intel thinks the OP and SF compression are enough.
Kingston SSDNow 40GB (X25-V)
695.86TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6268
MD5 OK
32.80MiB/s on avg (~279 hours)
--
Getting closer to that data retention test again :)
Need to decide on what drive to test...
edit:
Regarding the 520, it would be nice to know if it is "Life-Time-Throttled".
Update:
Vertex Turbo DEAD, pending destructive flash
Samsung 830 Still works
The 830 is still working for the time being, but I'm suspending testing of it.
EDIT
I just started looking at the Turbo's SMART data, and it's a sight to behold. I'll post some info graphics or something at a later time.
I'm attempting to destructive flash it now.
Yeah seems like Intel has exited the controller market :(
Any news on a C300 ?
Thanks !
The 520 is just the replacement for the 510 -- which didn't use an Intel controller anyway. And they're still releasing new drives with the Intel controller, such as the upcoming 711 series. I know I want one. Intel has never been in the 6gbps controller business, so it's not like the world is losing anything. The 500 series might just always use a third party controller, then all other lines will use Intel controllers. Who knows?Quote:
Originally Posted by bulanula
With under 100TiB on the chart? That's terrible but good enough for me because I have written about 2TiB in ~1.5 years on my Vertex1 128.Quote:
Originally Posted by Christopher
Read errors went through the roof. I can probably save it with a dflash, the drive is fine otherwise. Indilinx drives just up and die for no good reason sometimes, which is why having the option to dflash is so excellent.Quote:
Originally Posted by devsk
Yes, but it took the M225 to mega :banana: :banana: :banana: :banana: TB to get to that point.Quote:
Originally Posted by Christopher
EviLdently, not all Indilinx are built the same :)
Bluestang,
I questioned the drive's pedigree, but you were right to say that it was bunk.
Well, the good news is I can just dflash it -- I checked -- but I'm holding off. Before the drive died, these were it's stats:
Vertex Turbo 64GB 1.7FW
GiB 119230.48
TiB 116.4360
42 Erase Fail
72 Read Fail <-----Went from 0 to 72 in a couple hours.
1 Program Failure
58 MWI
2127 Avg Erase Count
417 Power on Hours.
12 Raw Read Error Rate
The problem is, when I dflash it I'll lose all the smart data accumulation. I'm deciding what to do -- it could just up and happen again in a few days.
I wonder what runnning the NAND cleaner would do?
Mine didn't like it at all, but I believe mine was already past it's time when I tried.
Can/have you ran the Indilinx SmatViewer on it to see what Bank all the errors are on?
If the smart viewer works in engineering mode, I'll give it a shot.
I ran the NAND cleaner on this drive before the start of testing, trying to isolate the issues with the drive. This drive didn't like getting FW flashed or NAND cleaned -- trying to do either one of those would often result in an error.
I let it sit over night, just in case that good old voodoo magic would help. It did not.
On Feb 4 2012 read failures went from 1 to 72. When the drive died, it locked the system up. It was still on technically, but no system will boot with the Turbo not in engineering mode.
No, don't use it in Eng mode. It will scroll forever when listing info as it's not seen in the normal way.
Have you tried hot plugging it in once booted into Windows. That did the trick with mine once, but it sounds like your to the point of no return if it's keeping system from booting. That is where I was with mine when it finally died.
As long as your keeping proper records of SMART data, then I don't see anyone having an issue with d-flashing it to tried and continue if it's your last resort.
Bluestang, you are a gentleman and a scholar. I'm trying to find the smart viewer again, and I may or may not have it.
----------------------------------------------------------------------------------///
UPDATE:
The Vertex Turbo is unflashable. After 70 mins of laundering and dflashing, nothing will "take". I'll try again, but it's dead...
Official Time of Death: 4 Feb 2012 22:11:45 UTC -5
I have put SmartViewer here for you to DL if you need it again. Need to "run as admin" for it to work right I believe.
One drive dies, another one comes in the mail. It's the circle of life.
16GB MTRON PRO 7000 2.5"
187 Total Erase Count 258954
Since I... ahem... destroyed the last MTRON on accident, I got another 16GB model to replace it with.
As you can see, it's not really any faster than the others:
https://www.box.com/shared/static/0q...vg08l2r1mk.png
Now that the testing rig is empty I'm doing some maintenance on it, but I'll start the MTRON later today.
Good work Cristopher !
Really eager to see the small Mtron perform. Thanks !
The MTRON 2.5" 7000 PRO (7025) 16GB SLC is up and running.
I cloned the endurance rig's system drive to the 32GB MOBI, then put the 7000 PRO to work on 8 FEB 2012 21:00 UTC -5
The PRO 7000 uses 16GB of Micron SLC, @50nm and each device is 1GB.
I soon hope to have some new drives in the rig to keep the MTRONs company. I've been considering some newer drives, and I'm still also considering the 120GB Mushkin Chronos Deluxe I already have -- but it's too damn slow for my tastes (in E-testing).
Wow, a lot of things going on for you Christopher :)
Will be updating the charts etc tonight.
--
Kingston SSDNow 40GB (X25-V)
701.99TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6323
MD5 OK
32.80MiB/s on avg (~334 hours)
Looks like I need to decide on that second SSD real soon, the X-25 will be disconnected tomorrow and will stay disconnected for the weekend for a short data retention test.
I'm particularly disappointed by the Turbo. I had such... high hopes for it. 116TB is nothing.
I'm thinking that maybe the Turbo isn't refurbished. Perhaps it just used lower binned 51nm Samsung because all the good stuff was gone. Another possibility is the new features of the 1.7FW. Supposedly, it uses different wear leveling, and maybe it's just not as good as 1.6FW.
Here is a quick and dirty chart from the last 23 hours of the Turbo's short, miserable life.
https://www.box.com/shared/static/nm...n2gemqykxn.jpg
Read failures go from 1 to 72 in ~22 hours. I would just have to assume that it's relevant. I tried flashing it again a while back... but it's still dead.
MTRON 7000 PRO 2.5" 16GB SLC, Day 1
100/100/7640236
GiB: 4,534.91
TiB: 4.4286
Avg MB/s 53.29
https://www.box.com/shared/static/x3...8rughu1hgo.png
I'm not even sure what the differences are between the MOBI and PRO are.. To my knowledge, they perform identically.
UPDATE
I believe that the MOBI drives use Samsung SLC, while the PRO series utilizes Micron SLC. Now that I don't have to worry about breaking it, I can take the dead MOBI apart.
WAIT.....................................
The MOBI uses Hynix SLC.
[Hynix Korea HY27UG088G5B x 16] Data sheet is here
Let me also say that the quality of the PCB seems to be a good deal higher than modern drives, though the MTRONs were not cheap 4 years ago. It's actually quite wonderful.
https://www.box.com/shared/static/zy...5s5m02jxtz.jpg
Kingston SSDNow 40GB (X25-V)
705.20TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6351
MD5 OK
32.80MiB/s on avg (~362 hours)
It is on a retention test as of tonight and will be reconnected late Sunday. (~50 hours)
--
Christopher,
The dead MOBI had Hynix NAND?
I'll get the new one into the charts but the old one didn't really get started so I wasn't planning on including it.
It looks like attachments are back :up:
I just managed to post a few just moments ago, lets hope they are back for good!
Yes, the dead one had Hynix. I had the 3.5" 7025 PRO taken apart, but I couldn't really get it into the test rig, so I had to get another one (the one currently running). The 3.5" used Micron SLC, so I assume the 2.5" 7025 PRO does too.
I was just curious, that's all. I'm not familiar with all that many drives utilizing Hynix SLC...
Anvil, don't bother putting the old MTRON in the charts or anything.
-------------------------------------------------------------------------
MTRON 7000 PRO 2.5" 16GB SLC, Day 2
100/100/14101603
GiB: 8667.90
TiB: 8.6448
Avg MB/s 53.54
The SF12xx drive that Vapor used had Hynix and I'm guessing that one of my 60GB Vertex 2's are Hynix as well, it's noticeably slower (in benchmarks) than the others I've got.
Hynix MLC is terrible, as far as I know. The older SLC might be great for all anyone knows, but I'm sure not very many drives ever used those chips. I'm sure there were some faster CF/SD cards that used the Hynix SLC for higher class ratings. Given the price difference between the MOBI and PRO MTRON's, I would guess that the Hynix was much less expensive than the Micron in 2008.Quote:
Originally Posted by Anvil
Is it using 3GB static data? (like the previous one)
The MTRON's were really great and known as quality devices, it's been quiet lately though...
edit:
Could you check whether the MTRON is a 1.5Gb/s device?
Anvil,
The MTRON is 1.5gbps. It's using 3GB of static data.
It's not native SATA, but is an ultra DMA IDE with a SiliconImage SATA bridge.
OK, could you also check if it is 14.9GiB?
(it should be)
14.90GB, Static data is actually 3.12GB.
I promise not to kill this MTRON on accident.
Attachment 124064
I'll update as soon as B.A.T shows his face :)
--
Christopher,
You better leave that drive alone :)
(it could last for years though...)
Christopher, hope you’re up for a long run. :) That Hynix NAND spec sheet has it down for 100,000 Program/Erase cycles. 2K page/ 128K Block.
HY27UG088G5B
PAGE READ / PROGRAM
Random access : 25us (max.)
Sequential access : 25ns (min.)
Page program time : 200us (typ.)
Block erase time: 1.5ms (Typ)
I don’t have much info for Hynix NAND but as a comparison to lower density NAND from Hynix:
H27UAG8T2B
3,000 Program/Erase cycles 8K page/2MiB Block
Page Read / PROGRAM
Random Access: 200 ㎲ (Max.)
Sequential Access : 25 ㎱ (Min.)
Page program time : 1600us (typ.)
Block erase time: 2.5ms (Typ)
As a comparison to Intel NAND
Intel JS29F64G08AAME1/ JS29F16B08CAME1/ JS29F32B08JAME1
5,000 Program/Erase cycles 8K page/2MiB Block
Page Read / PROGRAM
Random Access: 50 ㎲ (Max.)
Sequential Access : 20 ㎱ (Min.)
Page program time : 1200us (typ.)
Block erase time: 3.0ms (Typ)
Ao1,
You're right, but it's actually worse that it would appear. The Hynix SLC was in the MOBI 3025 that I shorted out (and took apart today). The PRO 7025 currently running uses Micron SLC...
I would guess that they're pretty similar, but if I had to guess which was better, I'd say it's the Micron stuff.
I'm pretty deranged to even attempt such a thing.
A couple of weeks ago I took apart the 3.5" 7025 PRO, and I posted which Micron SLC it had (I was sure it was Samsung).
Just to be clear:
2.5" MTRON MOBI 3025 16GB <------I killed this one, took apart today
2.5" MTRON MOBI 3025 32GB <------System drive for the endurance rig
2.5" MTRON PRO 7025 16GB <------Currently testing
3.5" MTRON PRO 7025 16GB <------Took this apart, wouldn't fit in the testing rig
I wonder if Hynix and Samsung had some joint fabs in Korea (in the past)?
Maybe Hynix:Samsung::Micron:Intel
Fortunately, after 50 or so hours, MWI on the MTRON is now down to 99.
So let's see... 50 hours *100 = 5000 hours, or 208 days. If it died at MWI 0, that would be impressive, but since no drive dies at MWI 0, I'd say I'm in for a couple of years.
MTRON PRO 7025 16GB SLC, Day 3
Attachment 124073
Yesterday, the MTRON seemed to jump back from 99/99/ to 100/99
I don't know why.
I've just reconnected the Kingston (X25-V) and all is OK :)
Anvil,
It was off for ~72 hours? That's pretty amazing, all things considered.
Now that I think about it, I wonder if Vapor's C300 is still alive (if it's just been sitting in a box since last fall, it would be very instructive if it was still working).
Christopher,
It was ~50 hours, Friday night - late Sunday night.
It would be interesting to know what happened to the C300, if he doesn't show up within reasonable time I'll consider using one of my C300 64GB, I've got a few and they have been used for benching only, a couple of them should be as good as new. (I'll check)
The MTRON PRO seems to be using Micron 29F8G08DAA SLC. I couldn't really find much on it, but I'm guessing it's 50nm, 100K PE rated.
Attachment 124092
------------------------------------------------------------------------------------------------------------
I would guess that Vapor's drive would/could have lasted 5 months unpowerered.
And I'm back. I've been busy with some family arrangement the last week.Quote:
Originally Posted by Anvil
Todays update.
Kingston V+100
359.7678 TiB
2228 hours
Avg speed 22.23 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=479058
Intel X25-M G1 80GB
336,04 TiB
20928 hours
Reallocated sectors : 00
MWI=114 to 108
MD5 =OK
45.66 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=479057
m4
410.9854 TiB
1590 hours
Avg speed 64.66 MiB/s.
AD gone from 140 to 115.
P/E 7248.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=479059
The Kingston dropped out again and it looks like it happens after 24h during a random write. It has done that at least the last 3-4 times.
Also the m4 has dropped in write speed by quite a lot of MiB/s. I don't know why but I'll watch it closely and see if it stabilize or drop further.
Welcome back, B.A.T. Do you think the M4's speed decrease is related to the M4 shuffling around the static data? I don't remember the first M4 dropping like that, though.
Kingston SSDNow 40GB (X25-V)
708.08TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6376
MD5 OK
34.36MiB/s on avg (~24 hours)
--
Looks like the m4 is about to overtake the Samsung :)
Attachment 124096
Yeah, and it only took the Samsung being on hiatus for two weeks, 5 weeks of writing at half speed, and probably some unholy goat sacrifices for the M4 to achieve that victory.Quote:
Originally Posted by Anvil
:yepp:
Luckily, I have some sacrificial goats and chickens left over from dark days of SandForce 2281 BSoD "remedies".
----------------------------------------------------------------------
MTRON 7000 PRO 16GB SLC, Day 5
187 98/98/36187185
TiB
21.7186
GiB:
22240.51 GiB
Avg MB/s:
53.67
The drop in speed on B.A.T's m4 was unexpected.
Attachment 124103
The Average MB/s on the MTRON is over 600MB/s.....
I don't think that's right.....
600MB/s :) ?
600.68Quote:
Originally Posted by Anvil
Don't forget the .68
Thank you :)Quote:
Originally Posted by Christopher
The first m4 just increased its speed during the whole test . Why I don't know but I'm wondering if I should take an SE to see if that makes a difference.
It looked difficult in the beginning but maybe it got a chance to win :)Quote:
Originally Posted by Anvil
Maybe I should get out some old Viking rituals to stay ahead :DQuote:
Originally Posted by Christopher
Todays update.
Kingston V+100
361.6627 TiB
2252 hours
Avg speed 22.89 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=479282
Intel X25-M G1 80GB
339,75 TiB
20952 hours
Reallocated sectors : 00
MWI=108 to 107
MD5 =OK
44.87 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=479281
m4
416.3031 TiB
1614 hours
Avg speed 64.48 MiB/s.
AD gone from 115 to 112.
P/E 7339.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=479283
Sadly, the MTRON is down to 441.68MBs Avg -- can't forget the .68 now, can I?
Not sure why it's doing what it's doing, but think it should be fine in a few more days. It has something to do with me stopping ASU for a few moments yesterday.
B.A.T.,
I'm not familiar with the Viking rituals of which you speak. You should probably take some pictures of said rituals for my personal edification and amusement.
I have heard it involves a virgin Vertex.Quote:
Originally Posted by Christopher
First an exorcist removes LTT. :up:
Then the Vertex is sacrificed upon the Anvil of Endurance. :clap:
:ROTF:
It doesn't have to be a Vertex though ;)
:rofl:
I just threaten the m4 with a swing of the axe if don't behave :up:Quote:
Originally Posted by Christopher
http://www.hdforums.com/forum/attach...oo-viking4.jpg
A virgin Vertex just seemed more poetic than a virgin SF. :rolleyes: :up:Quote:
Originally Posted by Anvil
Todays update.
Kingston V+100
363.4381 TiB
2275 hours
Avg speed 22.95 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=479447
Intel X25-M G1 80GB
342,92 TiB
20975 hours
Reallocated sectors : 00
MWI=107 to 106
MD5 =OK
40.12 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=479446
m4
421.4597 TiB
1637 hours
Avg speed 66.76 MiB/s.
AD gone from 112 to 109.
P/E 7429.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=479448
Kingston SSDNow 40GB (X25-V)
713.43TB Host writes
Reallocated sectors : 05 22
Available Reserved Space : E8 99
POH 6422
MD5 OK
33.50MiB/s on avg (~71 hours)
MTRON PRO 7025 PRO 16GB SLC, Day 7
GiB
31433.73
TiB
30.6970
187 97/97/50948619
https://www.box.com/shared/static/2s...c8iydi9j8d.png
MWI is finally down to 97! Yay me!
Looks like we lost a couple o' days in the transition.
Anvil, is it possible to recover running totals through the endurance browser?
MTRON 7025 PRO 16GB SLC day.... I forget
Possibly 46689GiB
Possibly writing 55.06MBs
187 96/95/75672728
I just realized what the xx25 and the xx35 represents in the MTRON model name, and now I feel mildly stupid.
Here are my last 2 updates:
16 Feb:
Kingston V+100
363.4381 TiB
2299 hours
Avg speed 22.81 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=479564
Intel X25-M G1 80GB
346,77 TiB
21000 hours
Reallocated sectors : 00
MWI=106 to 105
MD5 =OK
45.57 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=479563
m4
426.7750 TiB
1637 hours
Avg speed 63.70 MiB/s.
AD gone from 109 to 106.
P/E 7528.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=479565
Yesterdays update:
Kingston V+100
368.6335 TiB
2343 hours
Avg speed 79.58 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=479875http://www.diskusjon.no/index.php?ap...tach_id=479872
Intel X25-M G1 80GB
353,1974 TiB
21055 hours
Reallocated sectors : 00
MWI=105 to 103
MD5 =OK
46.66 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=479878http://www.diskusjon.no/index.php?ap...tach_id=479873
m4
435.8607 TiB
1718 hours
Avg speed 71.86 MiB/s.
AD gone from 106 to 100.
P/E 7699.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=479879http://www.diskusjon.no/index.php?ap...tach_id=479874
Betwhen these updates I've reinstalled the OS because it started to lock up and I did an SE on all the ssd.
Because of this the Kingston V+100 has increaced its speed by a huge amount, but the m4 just did a little jump. The Intel slows down as usual due to the lack of trim.
Another bonus is that SSDLife Pro works again :)
XS is still broken. Mostly.
Plextor M3 64GB or 128GB?. The 64GB is rougly as fast as the 830 64, while the 128GB is not much faster (for testing purposes)