10-20-2012 06:07 AM
That's actually not the way it was found.
If you want to see an increase right away then back your data up, SE the drive and put the data back on. I personally like Acronis for the task.
10-20-2012 08:42 PM
That is true of course, you are correct, I am wrong (I'm telling you??)
I was confusing the TweakTown and RWLabs method of fill testing SSDs and the affects of TRIM, with the method that Anandtech tested TRIM in RAID 0. Unrelated, but both on my mind.
BTW, nice work finding and documenting the SF 5.0 firmware bug, still astounding to me it could slip past LSI/SF. You found it initially I imagine, as part of your usual SSD testing, which is described in the link in your post above.
It's also curious IMO that TweakTown and RWLabs were the first and apparently only PC review web sites that published articles about this topic (I chatted about that a bit with Jon C.) That provides some insight into the true intended "customers" of those two web sites, in contrast to the others, IMO.
10-21-2012 04:59 AM
Parsec, you sir, are a good man.
I really just wanted to say it once but I've read several reviews on Anandtech and their fill test is different. they tends to seperate reads and write or percentage of read and writes, but the amount of files written to it, only around 10-20 gb? this may have larger effects on smaller drives ie 64/128 gb SSD but not so much on the 256 version.
imo what Chris and Jon are doing they literally have the drive filled up 25 50 and to 75% and then run vantage on all situaion, as explained in the article. compressed or incompressed, this is probably by far the most accurate way of doing it.
11-01-2012 12:45 PM - edited 11-01-2012 12:46 PM
Thanks unityole, I did not see your response until now.
I agree with your comments about the SSD fill tesing with Vantage done by Chris and Jon, which while seemingly simple compared to Anandtech's tesing, is really a more real world test for most SSD users. It is also a basic lesson in SSD performance that many SSD users need. As you fill up and use a consumer/client SSD, its performance goes down. A simple reality that escapes many SSD owners. SSD performance does not remain the same as day one, empty, Fresh Out of Box performance.
HDDs suffer from a generally similar performance decrease as they are used, but I never see users complaining about that.
11-17-2012 10:34 AM
I can't update my Macbook Pro (MacBookPro6,1), I don't have the optical drive installed as I have two disks.
I tried using reFit to boot from a CD and a USB drive with the image written to it, but I always get the same error coming back.
Error: Not found while loading legacy loader
Has anyone managed to update a MacBook with an external USB optical drive or Pen Drive?
11-19-2012 10:58 AM
external USB CDROM do not work. you will need to put the internal CDROM back in it or move the SSD to a different computer and do the update from there.
11-22-2012 11:25 PM
Maybe one day we'll have the SanDisk tools for the Mac, life will be so much easier... Just the through of having to rip macbook apart for each new firmware version is super dull.
11-29-2012 08:07 AM
And super super super dull when you have to take a Mac Mini apart.
There is no way to boot linux on a 2011 Mac Mini without major hacking (and even then I haven't managed to get it to work), so you have to dismantle the machine to get the SSD out, just to do a firmware update.
PLEASE Sandisk, update your tool to run on OSX. Would that be so freaking hard? It would save 1000's of your customers a whole load of pain.
12-17-2012 03:36 PM
My firmware update fails. I put the 240 Extreme in a lenovo with the disk temporarily replaced by the SSD. The update menu comes up and finds the SSD but fails immediately. The error I see on the following screen is
Operation not permitted - 23 Inappropriate ioctl
a little lower says:
Download Microcode (MS 0) ATA result (129,0)
Anyone see something like this ? I'm booting from the CD I burned. I tried it on two different Lenovo's (all the windows boxes I have available to me).
12-18-2012 11:01 AM
In case it helps anyone, I was able to update after retrying with the USB stick. Possible my CD image was corrupted but odd that it worked otherwise.