unreliable sata on MSI MS-7346 (sata_nv) + Seagate ST1000DM003-1CH162

Bug #1292046 reported by szu on 2014-03-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned
Saucy
High
Unassigned

Bug Description

what more can i tell? it crashes and does not provide any information, so i can't install ubuntu.
the reporting tool said that some logs will be automatically attached so i'm not sure if i have to add anything here?
ok, let's add syslog and partman according to the guidelines...

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.26
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Thu Mar 13 15:35:41 2014
InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sz 1882 F.... pulseaudio
 /dev/snd/controlC0: sz 1882 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=4084a9ca-831b-44dc-8245-aea2e8b8e4f1
InstallationDate: Installed on 2014-03-14 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7346
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=5d166cf8-1797-4b10-a41f-7d91f98237aa ro libata.force=noncq quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-18-generic N/A
 linux-backports-modules-3.11.0-18-generic N/A
 linux-firmware 1.116.2
RfKill:

Tags: saucy
Uname: Linux 3.11.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/13/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7346
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/13/2007:svnMSI:pnMS-7346:pvr1.0:rvnMSI:rnMS-7346:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7346
dmi.product.version: 1.0
dmi.sys.vendor: MSI

szu (szulat) wrote :
szu (szulat) wrote :

...and partman

Exception during installation:
Mar 13 14:35:31 ubuntu /plugininstall.py: Traceback (most recent call last):
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1780, in <module>
Mar 13 14:35:31 ubuntu /plugininstall.py: install.run()
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper
Mar 13 14:35:31 ubuntu /plugininstall.py: func(self)
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 204, in run
Mar 13 14:35:31 ubuntu /plugininstall.py: self.configure_plugins()
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 580, in configure_plugins
Mar 13 14:35:31 ubuntu /plugininstall.py: self.run_plugin(plugin)
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 554, in run_plugin
Mar 13 14:35:31 ubuntu /plugininstall.py: ret = inst.install(self.target, PluginProgress(self.db))
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/plugins/ubi-ubuntuone.py", line 532, in install
Mar 13 14:35:31 ubuntu /plugininstall.py: self.configure_oauth_token(target)
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/plugins/ubi-ubuntuone.py", line 558, in configure_oauth_token
Mar 13 14:35:31 ubuntu /plugininstall.py: uid = self._get_target_uid(target, target_user)
Mar 13 14:35:31 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/plugins/ubi-ubuntuone.py", line 539, in _get_target_uid
Mar 13 14:35:31 ubuntu /plugininstall.py: uid = int(p.communicate()[0].strip('\n'))
Mar 13 14:35:31 ubuntu /plugininstall.py: ValueError: invalid literal for int() with base 10: ''
Mar 13 14:35:31 ubuntu /plugininstall.py:

tags: added: installer-crash
szu (szulat) on 2014-03-21
summary: - the installer just crashes near the end (regular ubuntu 13.10)
+ unreliable sata on MSI MS-7346 (nForce, sata_nv)
szu (szulat) wrote :

...then i tried another (older) hard drive and it worked correctly.
seems that new kernels do not like some particular drives and/or some sata controllers (but my both drives work well in old ubuntu 10.10)
fortunately, libata.force=noncq helps

summary: - unreliable sata on MSI MS-7346 (nForce, sata_nv)
+ unreliable sata on MSI MS-7346 (sata_nv) + Seagate ST1000DM003-1CH162
affects: ubiquity (Ubuntu) → linux (Ubuntu)

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1292046

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Joseph Salisbury (jsalisbury) wrote :

Does this happen when you are trying to install Ubuntu and/or booting from a LiveCD? If so, can you see if this also happens with the latest Trusty daily build, which can be downloaded from:

http://cdimage.ubuntu.com/daily-live/current/

Changed in linux (Ubuntu):
importance: Undecided → Medium
importance: Medium → High
tags: added: kernel-da-key
szu (szulat) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
szu (szulat) wrote : BootDmesg.txt

apport information

szu (szulat) wrote : CRDA.txt

apport information

apport information

szu (szulat) wrote : Lspci.txt

apport information

szu (szulat) wrote : Lsusb.txt

apport information

szu (szulat) wrote : ProcCpuinfo.txt

apport information

szu (szulat) wrote : ProcEnviron.txt

apport information

apport information

szu (szulat) wrote : ProcModules.txt

apport information

szu (szulat) wrote : PulseList.txt

apport information

szu (szulat) wrote : UdevDb.txt

apport information

szu (szulat) wrote : UdevLog.txt

apport information

szu (szulat) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
szu (szulat) wrote :

re: "Does this happen when you are trying to install Ubuntu and/or booting from a LiveCD? If so, can you see if this also happens with the latest Trusty daily build, which can be downloaded from ..."

LiveCD (or, in my case "live flash drive") worked correctly, but of course it did not use the hard drive, so if sata problem is responsible for this, it would not be apparent. problem only showed up when installing, i tried several times and never succeeded (sometimes it just hanged, sometimes casper displayed a failure message).

then, after trying other releases and my older hard drive i discovered that the old ubuntu (like 10.10) handles both disks without problems, and the old disk can work with any ubuntu, new or old.
only the "new disk" on "new ubuntu" combination is fatal.

this reminded my of "libata.force=noncq" that was needed for correctly handling some SSD drives.
it turned out that it also helped in my case, so now i have working 13.10 (which opens another bunch of problems, but that's another story)

i also filed a bug in the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=72621

ok, i'm going to try Trusty, too, however, theoretically it should not work ;-) (if my theory is correct)

szu (szulat) wrote :

surprise, surprise!
the current 14.04 installs and works correctly without using any special boot options.

Linux ubuntu 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Joseph Salisbury (jsalisbury) wrote :

Can you see if this issue also happens with the latest upstream 3.11 kernel, which can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.6-saucy/

Changed in linux (Ubuntu Saucy):
status: New → Incomplete
importance: Undecided → High
Changed in linux (Ubuntu):
status: Confirmed → Incomplete

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Saucy):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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