Samsung 840 Pro 512GB not recognized

Bug #1471119 reported by hyper_ch
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

In order to get newer systemd version I installed 15.10.

However the partition manager (using the server image) did not recognize the Samsung 840 Pro SSD. I was forced to go back and install 15.04, then upgrade to 15.10 and that worked without issues.

Changing to a different tty and doing checking /dev/disk/by-id also shows no sign of the Sasmungs 840 Pro.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jul 3 08:47:27 2015
InstallCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-22-generic root=UUID=78220e78-a48e-4add-8268-b84e73d2b2cb ro rootflags=subvol=@ splash quiet pcie_aspm=force nomdmonddf nomdmonisw vt.handoff=7
ProcEnviron:
 LANGUAGE=en_US:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

The server image does not use ubiquity. Does the drive show up in /dev or cat /proc/partitions?

affects: ubiquity (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

no, it doesn't show up there.

Revision history for this message
Phillip Susi (psusi) wrote :

Can you get a copy of /var/log/kern.log at this point?

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

I'd need to redownload Wily, start installation and test it then. However the main issue would be:

How would I save the kern.log?

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Couldn't find kern.log but tried to find other stuff.

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

These errors seem to indicate that either the drive or sata controller are defective:

[ 13.649232] ata1: link is slow to respond, please be patient (ready=0)
[ 17.790930] ata1: COMRESET failed (errno=-16)
[ 23.651669] ata1: link is slow to respond, please be patient (ready=0)
[ 27.793364] ata1: COMRESET failed (errno=-16)
[ 33.654107] ata1: link is slow to respond, please be patient (ready=0)
[ 62.813890] ata1: COMRESET failed (errno=-16)
[ 62.813914] ata1: limiting SATA link speed to 3.0 Gbps
[ 67.835096] ata1: COMRESET failed (errno=-16)
[ 67.835121] ata1: reset failed, giving up
[ 68.842534] ata1: exception Emask 0x10 SAct 0x0 SErr 0xc00000 action 0x1 t4
[ 68.842561] ata1: irq_stat 0x0c000000, interface fatal error
[ 68.842580] ata1: SError: { Handshk LinkSeq }

Are you sure it works when you upgrade? Are you booting with any special kernel command line arguments? cat /proc/cmdline please.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Well, I did install 15.04 without troubles and upgraded to 15.10 and it works without troubles.

No special kernel command line arguments. Whatever comes as default for the installer and then ubuntu itself.

Revision history for this message
Phillip Susi (psusi) wrote :

Can you attach a syslog from this upgraded and working boot for comparison?

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Here's the syslog

Revision history for this message
Phillip Susi (psusi) wrote :

That is very, very strange. I can't see how any of these could possibly make a difference, but I did notice that your working boot uses these three command line arguments:

pcie_aspm=force nomdmonddf nomdmonisw

You might try pressing F6 when booting the installer and add those arguments to the kernel command line ( before the -- ), and see if it changes things.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1471119

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
Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Brad: what good is that log for? This happens during the installation.

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

I just noticed that yesterday kernel 4.0.0-4 hit the repos

So today I made a new installer stick with current daily image and now it works fine. Both my installer problems are gone:

- ethernet card gets dhcp connection
- ssd is recognized in the partitioner

I tried first with those kernel boot params and then without. Result was the same.

Whatever it was, it didn't like 3.19 kernel for installation somehow.

Revision history for this message
penalvch (penalvch) wrote :

hyper_ch, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471119/comments/15 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.