Samsung Acknowledges and Fixes Bug On 840 EVO SSDs
Lucas123 writes: Samsung has issued a firmware fix for a bug on its popular 840 EVO triple-level cell SSD. The bug apparently slows read performance tremendously for any data more than a month old that has not been moved around on the NAND. Samsung said in a statement that the read problems occurred on its 2.5-in 840 EVO SSDs and 840 EVO mSATA drives because of an error in the flash management software algorithm. Some users on technical blog sites, such as Overclock.net, say the problem extends beyond the EVO line. They also questioned whether the firmware upgrade was a true fix or if it just covers up the bug by moving data around the SSD.
So are they going to fix the Samsung SM841 SSD or are we just screwed because we bought Dell?
It will be better to purchase from an owner who is a good farmer and a good builder.
This gets me wondering what brand of SSDs is best these days. I've read a lot of good about Intel brand drives, but wonder what is decent these days.
This is almost certainly a firmware bug with their read disturb compensation. At least they're owning up to it - but wow.
This what doctor recommends for this bug.
will be moving data around waaaaaay too much to lower the useful life of the flash memory to warranty length + 1 day.
That's awfully disappointing to hear as I was hoping to buy one of these soon. I might have to look elsewhere now, particularly because of that last statement "They also questioned whether the firmware upgrade was a true fix or if it just covers up the bug by moving data around the SSD."
"Dos version for MAC, Linux users ... Will be released on end of Oct."
http://www.samsung.com/global/business/semiconductor/samsungssd/downloads.html?CID=AFL-hq-mul-0813-11000279/
Let me guess - the source for that firmware patch is stored on a Samsung EVO 840 disk?
Ah, crap, I just bought 1 too; which means none of data is more than a month old. At least they're giving away a fix. Gee, more mess to deal with... :(
More technical detail as to what is going on.
http://www.anandtech.com/show/...
Glad I haven't upgraded from my Samsung 830 256GB from 2 years ago this month. Still chugging along like a champ with no degradation.
Couldn't write a proper wear levelling algorithm if their life depended on it.
First the MAG4FA/KYL00M/VYL00M data corruption bug that affected the Galaxy Nexus - https://android.googlesource.c...
Then (actually BEFORE it, Google found it during Galaxy Nexus development but Samsung kept it hush-hush - but it became a public issue much later) - the infamous Samsung Superbrick fiasco (If you fired a secure erase command at the chip, it had a chance of permanently corrupting the wear leveller data to the point where the chip's onboard controller would crash until you power cycled it any time you accessed that region of flash). - https://git.kernel.org/cgit/li...
Then pre-release 840 PRO devices suffer from the SAME DAMN BUG SAMSUNG HAD BEEN AWARE OF FOR OVER A YEAR - http://www.anandtech.com/show/... - While this only affected review devices, the fact that this was a known bug since before the release of the Galaxy Nexus (a year earlier) is inexcusable.
Then there was the Galaxy S3 "Sudden Death Syndrome" issue in late 2013... - https://github.com/omnirom/and...
Then there were a few other issues - http://wiki.cyanogenmod.org/w/...
Now this...
retrorocket.o not found, launch anyway?
https://www.samsung.com/global/business/semiconductor/samsungssd/downloads/Samsung_Performance_Restoration_v10_Installation_guide.pdf
Page 4 says:
System Requirements
Operating System
Windows XP SP2 (32bit)
Windows Vista (32/64bit)
Windows 7 (32/64bit)
Windows 8 & 8.1 (32/64bit)
...
Supported Partition Types
MBR, GPT
Page 5 says: Intel chipset is supported with Microsoft and Intel drivers. AMD chipset is supported with Microsoft, AMD and NVIDIA drivers, but the AMD driver is only supported for the latest driver.
Page 6 says:
7) Performance Restoration supports only the NTFS file system.
Blah. I'm running Linux with ext4 on my Samsung SSD 840 EVO 250GB (EXT0BB6Q).
Am I totally screwed?
I've used or installed a dozen or more 840 SSDs and never had a problem with any of them, including the 470 model I'm using now.
Is what's being fixed a widespread problem or a corner case of specific uses?
Don't have Windows here. Would be nice if they had a firmware patch that could run on Linux.
What implications are there for encrypted LVMs? Is it advisable to run such a setup on an SSD anyway or will it break some internal algorithms?
VNAND run at current 1X node levels should provide 32x the capacity for similar cost. Instead Samsung is using their tech to release 4X node level SSDs with similar capacity but double the cost of 1X node level 2D NAND. When the heck are we going to have some competitors come in with their own VNAND tech and bottom out the SSD market? They should even be able to achieve greater cost per byte effectiveness than HDDs.
In my case, based on hdparm -t on xubuntu and centos, the difference between a properly aligned Samsung EVO and an improperly aligned Samsung EVO is 510 MB/sec and 182 MB/sec respectively
http://cillian.wordpress.com/2... has some good info on setting up Samsung EVO properly on linux
My 512GB 830 series heats up like the CPU does. The 500GB traditional 7200rpm drive next to it stays relatively cool. I thought SSD were the future of the storage, not a flipping burn/fire hazard!
250GB EVO running for a year now, i never noticed slowdows using it as my daily SO drive. I guess its because the frequently accessed files aren't affected by this bug, i would have to run a complete drive read test to find out.
I did a test with a tool in one of the links and got the same results as other people.
http://i.imgur.com/1xomFsK.png
See how the graph goes down as age of files increases.
After running the tool to update the firmware and "optimize" the drive the graph is very different.
http://i.imgur.com/37m1bkn.png
Now i have to check again in a couple of months. I could run a full defrag and get the same result since all files would've been moved.
That I read this article BEFORE I started a time machine recovery of a 1TB drive that's at 85% usage. My Yosemite upgrade lasted 2 days before I decided Mavericks has less issues that I am willing to deal with right now. So here I am looking at my mac with another 4hrs to travel in time wondering if I should just nuke it now and firmware it so I can format it or should I wait another week for a possible performance restoration tool for osx...
I wonder if I can "fix" my RAID 5 system with a one disk at a time approach. Pull a drive. Use Linux to zero the drive. Use Windows to build the requisite NTFS partition to prevent complaints. Run the update. Rezero the partition information. And finally reinstall the drive in the RAID and let the RAID rebuild. Lather, rinse, repeat three more times for the other disks.
Of course, methinks I'll take a complete disk image backup of the RAID just in case.
Any thoughts regarding this approach? Is there anything simpler that can be done?
{^_^}