the target drive is not found when connected via USB 3 while installing Lubuntu alternate

Bug #1596281 reported by sudodus on 2016-06-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

While trying to install from the Lubuntu 16.04 LTS alternate amd64 daily iso file, the target drive is not found when connected via USB 3.

This happens with an SSD connected via USB 3. The corresponding desktop iso file works, and the released Lubuntu 16.04 LTS alternate amd64 worked.

This problematic iso file can install into the same SSD, when connected internally (connected via SATA).

I am writing this bug report booted from Lubuntu 16.04 desktop i364 daily, and I will attach the output of some command lines to illustrate how the SSD is recognized (and should be recognized also but the alternate installer).

I think the the bug is located in partman, or some related tool, that should identify connected drives.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-27-generic 4.4.0-27.46
ProcVersionSignature: Ubuntu 4.4.0-27.46-generic 4.4.13
Uname: Linux 4.4.0-27-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lubuntu 1700 F.... lxpanel
CasperVersion: 1.376
CurrentDesktop: LXDE
Date: Sun Jun 26 09:38:09 2016
LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160624)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=sv keyboard-configuration/layoutcode?=se
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-27-generic N/A
 linux-backports-modules-4.4.0-27-generic N/A
 linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.version: PSCBXE-00C00VN5
dmi.sys.vendor: TOSHIBA

sudodus (nio-wiklund) wrote :
sudodus (nio-wiklund) wrote :

Commands illustrating how the target drive is recognized by the desktop system.

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
sudodus (nio-wiklund) on 2016-06-26
summary: - the target drive is not found when connected via USB 3
+ the target drive is not found when connected via USB 3 while installing
+ Lubuntu alternate
sudodus (nio-wiklund) wrote :

I continued testing the problem with

- the released version lubuntu-16.04-alternate-amd64.iso

- another adapter/box to connect the SSD via USB 3.

And this is the result:

This (new) adapter, Deltaco USB 3.0 to SATA II cable fails also with the released version, so it is an old bug.

An (older) AKASA box for 2.5" drives to USB3 and eSATA works via USB 3 (with the released version as well as with the current daily iso file).

-o-

Both the new adapter and the old box are recognized during boot, Lubuntu boots from them, and are recognized by the desktop live system and its installer. So this bug seems specific for the debian installer and the particular hardware in the Deltaco adapter (shown as Asmedia by lsusb)

'Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge'

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc5-yakkety/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
sudodus (nio-wiklund) wrote :

I'll try, but I am a total newbie concerning new or non-standard kernels, so I'm not sure it will work for me :-P

sudodus (nio-wiklund) wrote :

@ Joseph Salisbury (jsalisbury),

I have been trying to think.

- I don't think it helps with a new kernel, because Lubuntu desktop of the corresponding daily-live iso file works (can identify the drive via that USB 3 adapter). See post #4.

- It would be very hard for me to create an alternate iso file with the ultimate upstream kernel.

I still think that the bug is located in partman, or some related tool, that should identify connected drives. Of course I may be wrong, and I will continue testing the current daily alternate iso files. I can also try Ubuntu Server. This way I will be getting new kernel versions ...

The bug is still there with the current Yakkety Alpha 1 iso file dated June 27

yakkety-alternate-i386.iso

-o-

Anyway, I will write a new comment, when I have new information about this bug.

Simon Quigley (tsimonq2) wrote :

@sudodus Is this the Xenial daily image or the Yakkety daily image that is affected?

sudodus (nio-wiklund) wrote :

Both.

I discovered it testing Xenial, but it appears also today, when I'm testing Yakkety.

You may edit the tags accordingly. (I usually avoid editing tags and leave it to people more involved in the administration.)

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1596281

tags: added: iso-testing
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  Edit
Everyone can see this information.

Other bug subscribers