[Bug 1769039] Comment bridged from LTC Bugzilla

bugproxy bugproxy at us.ibm.com
Wed May 16 14:50:44 UTC 2018


------- Comment From indira.priya at in.ibm.com 2018-05-16 10:36 EDT-------
I am able to install other guests which are using SAS disks /qemu images using netboot installer method.

------- Comment From FREDERIC at fr.ibm.com 2018-05-16 10:44 EDT-------
Hi Indira,
after connecting to the vm, I see that the kernel that the installer runs is 4.15.0-15
which is not the one used by the latest netboot which uses 4.15.0-20.
Also, the logs show "no packages matching running kernel 4.15.0-13-generic in archive"
which is not a good sign as it fails to find several kernel udebs that may lead to missing support.

Could you try with the latest netboot ?
Thanks,

F.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1769039

Title:
  Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks)
  with 'No disk drive was detected' message.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in debian-installer package in Ubuntu:
  Incomplete

Bug description:
  Problem Description:
  ===================
  Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message.

  Steps to re-create:
  ==================

  > on Witherspoon test system, tried to install latest ubuntu1804 build
  using netboot install.

  > Selected appropriate fields and then when it entres detect disk
  screen

  > It throws below messgae

  
    lqqqqqqqqqqqqqqqqqqqqqqqqqqu [!] Detect disks tqqqqqqqqqqqqqqqqqqqqqqqqqqqk
    x                                                                         x
    x No disk drive was detected. If you know the name of the driver needed   x
    x by your disk drive, you can select it from the list.                    x
    x                                                                         x
    x Driver needed for your disk drive:                                      x
    x                                                                         x
    x                     continue with no disk drive                         x
    x                     login to iSCSI targets                              x
    x                     cryptoloop                                          x
    x                     ipr                                                 x
    x                     virtio_scsi                                         x
    x                     none of the above                                   x
    x                                                                         x
    x     <Go Back>                                                           x
    x                                                                         x
    mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

  > Installer not able to detect the SAN disk(mulitpath disks) and so
  not able to proceed with installation.

  > Unable to proceed with ubutnu1804 installation as installer not able
  to detect the disk (SAN disks) using netboot install method

  > Attached /var/log/syslog messages from installer

  Attached /var/log/syslog files from installer shell prompt

  == Comment: #13 - Frederic Bonnard <FREDERIC at fr.ibm.com> - 2018-04-30 09:00:21 ==
  Hi,
  - did you install install with "disk-detect/multipath/enable=true" ? ( https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath.html.en )
  - check /var/log/syslog to see you didn't fail to download any udeb related to disk management and make sure there isn't any error .
  - check availability of disks with lsblk or "find /dev/disk/ -ls"

  F.

  == Comment: #14 - INDIRA P. JOGA <indira.priya at in.ibm.com> - 2018-05-02 04:55:55 ==
  (In reply to comment #12)
  > Hi Indira, thanks for the bug. I have some questions I would like to
  > understand better:
  > 
  > What are the device subsystem that this disks are connected to? Is it a
  > Fibre Channel connection?
  > 
  > Do you have explicit two connections to the same disk? I.e, you would see
  > two disks that the multipathd would need to detect that they are the same,
  > or, your subsystem would handle the multi path configuration? 
  > 
  > How many disks do you have?

  Hi Breno,

  System has both SAS card  with mulitpath & SAN card with mulitpath.
  Yes we have two connections to same disk. 

  FYI -

  SAN -
  mpathb (3600507680183050d28000000000002a3) dm-1 IBM,2145
  size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw
  |-+- policy='service-time 0' prio=50 status=active
  | |- 2:0:1:1  sdaa 65:160 active ready running
  | `- 3:0:1:1  sdag 66:0   active ready running
  `-+- policy='service-time 0' prio=10 status=enabled
    |- 2:0:0:1  sdx  65:112 active ready running
    `- 3:0:0:1  sdad 65:208 active ready running

  SAS -
  mpathl (35000c50076564663) dm-35 IBM,ST300MP0064
  size=279G features='0' hwhandler='0' wp=rw
  |-+- policy='service-time 0' prio=1 status=active
  | `- 1:0:8:0  sdi  8:128  active ready running
  `-+- policy='service-time 0' prio=1 status=enabled
    `- 1:0:19:0 sds  65:32  active ready running

  == Comment: #15 - INDIRA P. JOGA <indira.priya at in.ibm.com> - 2018-05-02 05:01:21 ==
  (In reply to comment #13)
  > Hi,
  > - did you install install with "disk-detect/multipath/enable=true" ? (
  > https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath.
  > html.en )
  > - check /var/log/syslog to see you didn't fail to download any udeb related
  > to disk management and make sure there isn't any error .
  > - check availability of disks with lsblk or "find /dev/disk/ -ls"
  > 
  > F.

  Yes i have tried both with multipath enable true & without multipath
  in both cases it failed. when problem reported guest has 3 disks and
  still not able to detect those disks.

  == Comment: #19 - Breno Leitao <brenohl at br.ibm.com> - 2018-05-03 09:02:54 ==
  Let's get this mirrored to canonical for their awareness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1769039/+subscriptions



More information about the foundations-bugs mailing list