*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706
Here's an edited summary of the reply I got from the "please contact our
firmware engineers at xxx@xxx" address; turns out there's no engineers
there either, but at least we finally have a sane non-formletter reply
which *for the first time* states that Samsung is aware of the issue and
is working on a fix at the firmware level. Good news for everyone:
"We are just the SSD tech support. We are not the FW engineers. They are
in Korea and have been aware of the issue since it first started being
reported online.
The latest stable Linux Kernal 4.0.5 successfully blacklists the
affected drive(s) from queued TRIM. Linux can still use Sequential
TRIM, so you’re not losing out on anything.
We see that you are well aware that Marc Carino and Martin K. Petersen
are in contact with Samsung on how to resolve the issue since it
started.
All we can say to users at this moment is that Linux is the only
operating system that has this issue with the Queued TRIM. Linux is open
source and can be modified by anyone, as such we do not support the OS.
We recommend updating to the new kernel, as we have seen that other
users have done so and it alleviated their issue(s)."
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1449005
Title:
trim does not work with Samsung 840 EVO after firmware update
(EXT0DB6Q)
Status in fstrim package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Confirmed
Status in fstrim source package in Trusty:
Invalid
Status in linux source package in Trusty:
Fix Committed
Status in fstrim source package in Utopic:
Invalid
Status in linux source package in Utopic:
Fix Committed
Status in fstrim source package in Vivid:
Invalid
Status in linux source package in Vivid:
Fix Committed
Bug description:
Hi,
after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the
fstream command doesn't work anymore. Besides, there are a lot of file system
errors and "bad sectors" reports. The problem is certainly caused by Samsung's
firmware but I reported it as a bug because in Windows TRIM works normally
after the upgrade. I have attached an image uploaded by a user who is
experiencing the same problem. If you execute the command "sudo fstrim /" the
console gets stuck. If you add that command in rc.local the boot is
compromised. I really hope this problem could be solved.
Thanks
===
break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a
break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
