Kernel update 3.13.0-105 causes SATA errors that end up remounting partitions as read-only

Bug #1649584 reported by Marcus Aurelius
6
This bug affects 1 person
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/controlC1: marcuscf 2558 F.... pulseaudio
 /dev/snd/controlC0: marcuscf 2558 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=6b4b37f4-4276-4541-8e40-36a0b8570265
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.
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=15c44951-2c8d-4c57-b8ff-e46deebb7b4a ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-105-generic N/A
 linux-backports-modules-3.13.0-105-generic N/A
 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.86A.0135.2011.0225.1100
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG45ID
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27729-310
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrIDG4510H.86A.0135.2011.0225.1100:bd02/25/2011:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-310:cvn:ct3:cvr:

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/FindRightPackage. 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.]

tags: added: bot-comment
affects: ubuntu → linux-lts-trusty (Ubuntu)
Revision history for this message
Marcus Aurelius (marcuscf) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Marcus Aurelius (marcuscf) wrote : BootDmesg.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : CRDA.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : Lspci.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : Lsusb.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : ProcEnviron.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : ProcModules.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : PulseList.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : UdevDb.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : UdevLog.txt

apport information

Revision history for this message
Marcus Aurelius (marcuscf) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you see if this issue still happens with the latest Trusty kernel in -proposed?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

affects: linux-lts-trusty (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → High
status: New → Triaged
tags: added: kernel-da-key
Revision history for this message
Marcus Aurelius (marcuscf) wrote :

I will try that and some other configurations later today or in the next few days, after backing up the data on that disk.

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

I haven't been able to reproduce the problem after running fsck on /dev/sda5.

I'm attaching an excerpt from my syslog which includes the errors I was getting (I guess they didn't show up in the logs sent by apport).

I still intend to test newer kernels and run other checks to see if it's a hardware or software problem.

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

I'm confirming that it's reproducible in 3.13.0-106-generic and 3.13.0-107-generic (although it seems to happen much less often).

I will run on 3.13.0-100-generic for a while to be sure it works well and to (try to) rule out the possibility of a hardware fault.

Revision history for this message
Marcus Aurelius (marcuscf) wrote :

Forget it. It's not related to kernel >= 3.13.0-105. I guess I need a better hard drive or a better SATA cable.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.