kernel-packages team mailing list archive

[Gunter Ohrner <1449005@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1338706 ***
    https://bugs.launchpad.net/bugs/1338706

This question / problem does not really fit here, as it's, as you write
yourself, totally unrelated to the TRIM issues mentioned above and this
is bug report is a dublicate in any case.

That being said your logs don't look too promising and I'd assume an SSD
failure. One of the first things I'd try in this case is having a closer
look at the S.M.A.R.T. stats (smartctl --xall /dev/sdX | less) and
running the different S.M.A.R.T. self tests (man smartctl). This should
give you more information about how your SSD feels and might help to
rule out any software issues immediately.

In any case, you should not discuss the results here but on an
appropriate mailing list or help forum, which bugs.launchpad.net isn't.
(You can also contact me directly via mail, however while I've some
experience using Linux systems, also with SSDs, I'm no ATA / libata
expert.)

Good luck!

-- 
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:
  Fix Released
Status in fstrim source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in fstrim source package in Utopic:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in fstrim source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Released

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