This is a firmware issue. The kernel only enumerates the set of devices
exposed to it by the hardware/firmware; it doesn't have any way to know
you don't want them until it's too late. If they can be turned off in
the firmware, that's probably the best solution.
The failure of parted to partition /dev/sdj on the Garrison sounds like
a different issue. We do not have access to Garrison hardware so are
not going to be able to help with debugging that. We have successfully
installed Ubuntu on Firestone as part of our certification process.
** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1561447
Title:
MFG HOT: ubuntu installer device detection issue on Firestone and
Garrison
Status in linux package in Ubuntu:
Invalid
Bug description:
== Comment: #0 - Lucas J. Schroeder <[email protected]> - 2015-07-15
15:59:37 ==
---Problem Description---
The installer for 14.04.02 and 15.04 is detecting hard disk media that does
not exist. In my preseed files for both Firestone and Garrison, the
debconfig-set partman-auto/disk has to followed by /dev/sdj. Trying to use
/dev/sda will result in an installer error
Contact Information = [email protected]
---uname output---
Linux rcx2c360 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:42:36
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Firestone 8335-GTA, Garrison 8335-GTB
---boot type---
Network boot
---bootloader---
opal
---Kernel cmdline used to launch install---
cd /tmp
tftp -g -l ./initrd -r /tftpboot/initrd.Ubuntu14_1502.gz 9.10.192.40
tftp -g -l ./vmlinux -r /tftpboot/vmlinux.Ubuntu14_1502 9.10.192.40
kexec -l ./vmlinux --initrd ./initrd --append
---Bootloader protocol---
unsure
---Install repository type---
Local repository
---Install repository Location---
http://9.10.192.40/install/ppc/Ubuntu14_1502/CD1
---Point of failure---
Other failure during installation (stage 1)
== Comment: #5 - NISHANTH ARAVAMUDAN <[email protected]> - 2015-07-16
11:48:54 ==
Michael,
I think this is the same issue we see on our Garrison as well.
Lucas, Michael will take a look at it.
-Nish
== Comment: #7 - NISHANTH ARAVAMUDAN <[email protected]> - 2015-07-16
12:16:47 ==
HA!
From our Garrison:
Jul 15 19:20:35 kernel: [ 7.544664] scsi 0:0:0:0: CD-ROM AMI
Virtual CDROM0 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.548145] scsi 0:0:0:1: CD-ROM AMI
Virtual CDROM1 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.552144] scsi 0:0:0:2: CD-ROM AMI
Virtual CDROM2 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.554643] scsi 0:0:0:3: CD-ROM AMI
Virtual CDROM3 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.925426] scsi 1:0:0:0: Direct-Access AMI
Virtual Floppy0 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.925672] scsi 2:0:0:0: Direct-Access AMI
Virtual HDisk0 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.927825] scsi 1:0:0:1: Direct-Access AMI
Virtual Floppy1 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.928042] scsi 2:0:0:1: Direct-Access AMI
Virtual HDisk1 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.928547] scsi 1:0:0:2: Direct-Access AMI
Virtual Floppy2 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.928805] scsi 2:0:0:2: Direct-Access AMI
Virtual HDisk2 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.929173] scsi 1:0:0:3: Direct-Access AMI
Virtual Floppy3 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.929669] scsi 2:0:0:3: Direct-Access AMI
Virtual HDisk3 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 7.931045] scsi 2:0:0:4: Direct-Access AMI
Virtual HDisk4 1.00 PQ: 0 ANSI: 0 CCS
Jul 15 19:20:35 kernel: [ 8.031783] sr 0:0:0:0: [sr0] scsi-1 drive
Jul 15 19:20:35 kernel: [ 8.031908] cdrom: Uniform CD-ROM driver Revision:
3.20
Jul 15 19:20:35 kernel: [ 8.032391] sr 0:0:0:0: Attached scsi CD-ROM sr0
Jul 15 19:20:35 kernel: [ 8.032526] sr 0:0:0:0: Attached scsi generic sg0
type 5
Jul 15 19:20:35 kernel: [ 8.083910] sr 0:0:0:1: [sr1] scsi-1 drive
Jul 15 19:20:35 kernel: [ 8.084253] sr 0:0:0:1: Attached scsi CD-ROM sr1
Jul 15 19:20:35 kernel: [ 8.084359] sr 0:0:0:1: Attached scsi generic sg1
type 5
Jul 15 19:20:35 kernel: [ 8.112910] sr 0:0:0:2: [sr2] scsi-1 drive
Jul 15 19:20:35 kernel: [ 8.113230] sr 0:0:0:2: Attached scsi CD-ROM sr2
Jul 15 19:20:35 kernel: [ 8.113349] sr 0:0:0:2: Attached scsi generic sg2
type 5
Jul 15 19:20:35 kernel: [ 8.124786] sr 0:0:0:3: [sr3] scsi-1 drive
Jul 15 19:20:35 kernel: [ 8.125418] sr 0:0:0:3: Attached scsi CD-ROM sr3
Jul 15 19:20:35 kernel: [ 8.125523] sr 0:0:0:3: Attached scsi generic sg3
type 5
Jul 15 19:20:35 kernel: [ 8.144632] sd 1:0:0:0: Attached scsi generic sg4
type 0
Jul 15 19:20:35 kernel: [ 8.147850] sd 1:0:0:1: Attached scsi generic sg5
type 0
Jul 15 19:20:35 kernel: [ 8.149422] sd 1:0:0:0: [sda] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.150210] sd 1:0:0:2: Attached scsi generic sg6
type 0
Jul 15 19:20:35 kernel: [ 8.153482] sd 1:0:0:3: Attached scsi generic sg7
type 0
Jul 15 19:20:35 kernel: [ 8.156756] sd 1:0:0:1: [sdb] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.160922] sd 1:0:0:2: [sdc] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.229248] sd 1:0:0:3: [sdd] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.513434] sd 2:0:0:0: Attached scsi generic sg8
type 0
Jul 15 19:20:35 kernel: [ 8.518483] sd 2:0:0:0: [sde] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.578842] sd 2:0:0:1: Attached scsi generic sg9
type 0
Jul 15 19:20:35 kernel: [ 8.582943] sd 2:0:0:1: [sdf] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.583545] sd 2:0:0:2: Attached scsi generic sg10
type 0
Jul 15 19:20:35 kernel: [ 8.584187] sd 2:0:0:3: Attached scsi generic sg11
type 0
Jul 15 19:20:35 kernel: [ 8.584734] sd 2:0:0:4: Attached scsi generic sg12
type 0
Jul 15 19:20:35 kernel: [ 8.631208] sd 2:0:0:2: [sdg] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.632455] sd 2:0:0:3: [sdh] Attached SCSI
removable disk
Jul 15 19:20:35 kernel: [ 8.633703] sd 2:0:0:4: [sdi] Attached SCSI
removable disk
Notice, 4 virtual CD-ROM devices (sr0-sr3), 4 virtual floppy (!!)
devices (sda-sdd), 5 virtual hdisks (sde-sdi), which is why the first
physical disk is sdj.
I don't believe this is obviously a kernel bug, but could easily be an
issue in fw (which is where I think this data comes from). Digging ...
== Comment: #8 - NISHANTH ARAVAMUDAN <[email protected]> - 2015-07-16
12:17:34 ==
A bit more:
Jul 15 19:20:35 kernel: [ 5.770556] usb 1-3.1: New USB device found,
idVendor=046b, idProduct=ff20
Jul 15 19:20:35 kernel: [ 5.770559] usb 1-3.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Jul 15 19:20:35 kernel: [ 5.770562] usb 1-3.1: Product: Virtual Cdrom
Device
Jul 15 19:20:35 kernel: [ 5.770565] usb 1-3.1: Manufacturer: American
Megatrends Inc.
Jul 15 19:20:35 kernel: [ 5.770568] usb 1-3.1: SerialNumber: AAAABBBBCCCC1
Jul 15 19:20:35 kernel: [ 5.863316] usb 1-3.2: new high-speed USB device
number 4 using xhci_hcd
Jul 15 19:20:35 kernel: [ 5.974569] usb 1-3.2: New USB device found,
idVendor=046b, idProduct=ff40
Jul 15 19:20:35 kernel: [ 5.974786] usb 1-3.2: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Jul 15 19:20:35 kernel: [ 5.986439] usb 1-3.2: Product: Virtual Floppy
Device
Jul 15 19:20:35 kernel: [ 5.988236] usb 1-3.2: Manufacturer: American
Megatrends Inc.
Jul 15 19:20:35 kernel: [ 5.991003] usb 1-3.2: SerialNumber: AAAABBBBCCCC2
Jul 15 19:20:35 kernel: [ 6.083322] usb 1-3.3: new high-speed USB device
number 5 using xhci_hcd
Jul 15 19:20:35 kernel: [ 6.194573] usb 1-3.3: New USB device found,
idVendor=046b, idProduct=ff31
Jul 15 19:20:35 kernel: [ 6.194819] usb 1-3.3: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Jul 15 19:20:35 kernel: [ 6.196691] usb 1-3.3: Product: Virtual HardDisk
Device
Jul 15 19:20:35 kernel: [ 6.198020] usb 1-3.3: Manufacturer: American
Megatrends Inc.
Jul 15 19:20:35 kernel: [ 6.199590] usb 1-3.3: SerialNumber: AAAABBBBCCCC3
Jul 15 19:20:35 kernel: [ 6.367331] usb 1-3.4: new low-speed USB device
number 6 using xhci_hcd
Jul 15 19:20:35 kernel: [ 6.510087] usb 1-3.4: New USB device found,
idVendor=046b, idProduct=ff10
Jul 15 19:20:35 kernel: [ 6.510376] usb 1-3.4: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Jul 15 19:20:35 kernel: [ 6.512161] usb 1-3.4: Product: Virtual Keyboard
and Mouse
Jul 15 19:20:35 kernel: [ 6.513504] usb 1-3.4: Manufacturer: American
Megatrends Inc.
So these are all USB attached, I think. Is there an external USB
device on the Garrison machines?
== Comment: #16 - MICHAEL BRINGMANN <[email protected]> - 2015-07-16
17:20:21 ==
(In reply to comment #14)
> (In reply to comment #9)
> > On our Garrison machine, the default installer with Ubuntu 15.04 (kernel
> > 3.19.0-16) does not find devices /dev/sda through /dev/sdi. It claims to
> > find device /dev/sdj, but then 'parted' fails trying to partition it. The
> > remainder of the installation process is aborted.
>
> Well, it finds those devices, but they are empty, right?
Yes, they are empty.
>
> > Using the later installation of Ubuntu 15.04 (kernel 3.19.0-22) from
> > ports.ubuntu.com, the installer finds device /dev/sda and creates a
> > partition on /dev/sda2. The installation process completes, and the
system
> > boots up.
>
> What do you mean by "later installation"? Do you mean a more recent ISO
> image?
Sorry, I should have phrased it as later build of the kernel (-22) and the
associated
infrastructure, where we are using the "-16" build in our Autotest/Cobbler
installs.
>
> Is Garrison intended to be supported with 15.04? Or 15.10? If 15.10, we
> should be testing that early ISO.
Michael
>
> -Nish
== Comment: #28 - Lucas J. Schroeder <[email protected]> -
2016-03-23 12:04:44 ==
Re-tested with the Mar22 build of 16.04. The problem is still valid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561447/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp