Kernel update 3.13.0-105 causes SATA errors that end up remounting partitions as read-only
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
I started to notice SATA errors on my secondary hard disk (a Toshiba DT01ACA100 1TB, on an Intel DG45ID motherboard) after updating to 3.13.0-105. A simple file copy operation fails after a few megabytes and the drive stops responding. Sometimes it remounts itself as read-only, and sometimes it disappears from the drive list. On next reboot the drive is sort-of OK, but without the new files.
I thought it was a hard disk failure, but reverting to 3.13.0-100 seems to fix the problem completely. SMART is OK and fsck checks passed.
I'll try to post more details about my system later when I'm back to my home computer.
---
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2012-05-12 (1676 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
NonfreeKernelMo
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.22
RfKill:
Tags: trusty
Uname: Linux 3.13.0-105-generic x86_64
UpgradeStatus: Upgraded to trusty on 2016-11-03 (40 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/25/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: IDG4510H.
dmi.board.
dmi.board.name: DG45ID
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27729-310
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
affects: | ubuntu → linux-lts-trusty (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Triaged → Incomplete |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1649584/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]