How many files are generated during a single loop on each drive? (520 vs V4)
(might make up for the time it takes for deleting/TRIMming the files)
Printable View
How many files are generated during a single loop on each drive? (520 vs V4)
(might make up for the time it takes for deleting/TRIMming the files)
Yeah, the V4 does 18240 files per cycle.
The 520 does 12940 files per cycle.
The V4 (and 520) is quicker deleting when TRIM is disabled though.
--------------------------------
Samsung 830 256 Day 53
1,261,175.94 GiB
1,231.61 TiB
296.40 MB/s Average
1245 Hours
5480 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
--------------------------------
OCZ Vertex Turbo 64 Day 70
495,280.250 GiB
483.67 TiB
85.08 MB/s Avg
1738 hours
8850 Avg PE count
-99 MWI
0/0/1 Read/Program/Erase Fail
--------------------------------
Todays update:
m4
851.2467 TiB
3602 hours
Avg speed 74.49 MiB/s.
AD gone from 127 to 123.
P/E 14673.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490115
Intel X25-M G1 80GB
599.04 TiB
22935 hours
Reallocated sectors : 154
Available Reserved space: 90
MWI=124
MD5 =OK
45.27 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490114
I was too late for the post-office today so you'll have to wait until tomorrow for the fun to begin :(
That's not very becoming for the Bravest Man on the Face of the Earth.Quote:
Originally Posted by B.A.T
I had to work some overtime... But it's going to be a glorious weekend. :D
I posted about this in the Plextor M3P thread, but it's worth pointing out here... because things have changed, and the M3P may now be a testing candidate. I'll have to run some tests, but the M3P 1.03 firmware added a whole mess of new SMART attributes -- MWI, temp, etc (viewable through the new Plextool). I can probably figure out the attributes on my own, but one may be host writes.
UPDATE
Yes, the M3P now has host writes! In 64MB increments! Attribute B1... thanks, Plextor! I don't know why I'm so excited-- it still doesn't have a PE cycle counter.
I got one erase failure more on the VT, and one read failure. I hope it's not about to hit a brick wall and die slow over the next two weeks.
So that's 2 erase and one read fail.
i fear for the M3P now...:bsod:
I got mine today (about 40 minutes ago), not sure what gets connected first, the Vertex 4 or the Kingston or a few M3P's. (will be later tonight anyways)Quote:
Originally Posted by B.A.T
Tthe M3P's have been sitting in their box for almost a week, the 1.03 FW looks to make my day though :)
(registered and got PlexTool last night!)
Well, at first I though the host writes worked in 32MiB increments -- I had no way of knowing how much I had written to the M3P. However, I copied 5.8GB and was able to determine that it was just 64MiB. The Plextool doesn't show hostwrites in any form, which seems like an oversight. After upgrading to 1.03, the host writes were visible -- I'm sure it was there before, since it didn't reset to zero when I flashed.
Further, the Plextool also has a warning about temperature throttling! 1.03 adds temps somewhere, but it's not readily obvious. It's probably just a smart flag that toggles when temp is too high, but I'll investigate further.
There could be loads of attributes that just aren't visible, the host writes attribute should be required on all drives.
(host reads as well)
My Kingston has the 8860 firmware, there is a 8862 but neither is available for download.
Lets hope that B.A.T got the same one.
Strange that Intel never released anything newer than 8850, quite a few (me including) got a mix of firmwares for the X25-E.
Samsung 830 256 Day 54
1,285,269.83 GiB
1,255.14 TiB
296.72 MB/s Average
1272 Hours
5583 Wear Leveling Count
MWI 1
2/0 Erase/Program Fail
Used Reserved Block Count: 4/8192 sectors
OCZ Vertex Turbo 64 Day 71
502,106.22 GiB
490.33 TiB
85.24 MB/s Avg
1761 hours
8972 Avg PE count
-97 MWI
6/0/2 Read/Program/Erase Fail
--------------------------------
The VT keeps getting read failures. This is not good.
The first VT's death was preceeded by a relatively massive number or read failures.
I have a mix too. The toolbox indicates that one of my Es running 8790 can be updated, but I'm not sure to what.Quote:
Originally Posted by Anvil
Was there any point to updating FWs for the Es?
I believe the 88nn series fw fixed the "bug" where the drive could not recover when/if it started to slow down on writes.
Well I upgraded to 8850. Everything was great for about 4 minutes, until the drive failed. It's permanently locked -- detectable, but I can't SE it and can't re-flash.Quote:
Originally Posted by Anvil
:banana::banana::banana::banana:!!!
<100GiB left in the tank on that VT me thinks...hopefully I'm wrong.Quote:
Originally Posted by Christopher
Good to hear from you, Bluestang -- But I can't handle any more bad news today.
Weird, I'd leave it alone (disconnected) till tomorrow and then try a self test using smartmontools.Quote:
Originally Posted by Christopher
Never had issues with intel fw's except for on MBs that typically locks the drive. (Asus used to cause this phenomena)
I always HDDErase / flash old drives on a GB MB, it just works.
The FW update was successful, I then booted from the drive (it had an install on it) and a few minutes in the system locked up, the HDD indicator was solid indefinitely. I tried SEing it in Windows (VHD service and the Intel Toolbox fail to progress through the detection phase). I gave it a shot with PartedMagic, and it showed the partition info, but any attempt to perform any activity on the drive fails.
I'll let the E sit for a day and try again.
And now it's here :)Quote:
Originally Posted by Anvil
Attachment 126657
Attachment 126656
And it got fw 8860, same as you Anvil :up:
Thats's great!
It's got a different feel vs the original X25-E, somehow it feels more expensive/shiny.
That is hard to believe taken into account that this one cost a lot of $ less then the original X25-E.
The sticker and surface is just more shiny.
My drive identifies as an Intel, a bit strange.
It had a power cycle count of 37 (38 now), Power On hours is at 30 and finally 6GB host writes. (probably just testing)
E9 Media Wearout is at 99.