← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

 

This bug was fixed in the package systemd - 237-3ubuntu10.3

---------------
systemd (237-3ubuntu10.3) bionic; urgency=medium

  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin
    to the kernel (we previously only set it in modprobe.d) LP: #1779815

 -- Adam Conrad <adconrad@xxxxxxxxxx>  Fri, 20 Jul 2018 11:13:58 -0600

** Changed in: systemd (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - ABDUL HALEEM <abdhalee@xxxxxxxxxx> - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / MD RAID devices 

  Used 20101020ubuntu543 version to install
  http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdhalee@xxxxxxxxxx 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  =======console error log=======

    ?????????????????????????? [!!] Partition disks ???????????????????????????
    ?                                                                         ?
    ? Note that all data on the disk you select will be erased, but not       ?
    ? before you have confirmed that you really want to make the changes.     ?
    ?                                                                         ?
    ? Select disk to partition:                                               ?
    ?                                                                         ?
    ?                 /dev/nvme0n1 - 491.5 GB NVMe Device                     ?
    ?                 /dev/nvme1n1 - 98.3 GB NVMe Device                      ?
    ?                                                                         ?
    ?     <Go Back>                                                           ?
    ?                                                                         ?
    ???????????????????????????????????????????????????????????????????????????



  <Tab> moves; <Space> selects; <Enter> activates buttons

  
  To make sure it detects the disks I had to 
  <Go back >
  <Go back >
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
    ?????????????????????????? [!!] Partition disks ???????????????????????????
    ?                                                                         ?
    ? Note that all data on the disk you select will be erased, but not       ?
    ? before you have confirmed that you really want to make the changes.     ?
    ?                                                                         ?
    ? Select disk to partition:                                               ?
    ?                                                                         ?
    ?          /dev/nvme0n1 - 491.5 GB NVMe Device                            ?
    ?          /dev/nvme1n1 - 98.3 GB NVMe Device                             ?
    ?          SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075              ?
    ?          SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume              ?
    ?          SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ              ?
    ?                                                                         ?
    ?     <Go Back>                                                           ?
    ?                                                                         ?
    ???????????????????????????????????????????????????????????????????????????

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK <sthoufee@xxxxxxxxxx> - 2018-07-03 02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK <sthoufee@xxxxxxxxxx> - 2018-07-03 02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 (pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 4 (/dev/hvc0) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 5 (/dev/hvc0) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 6 (/dev/hvc0) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 (pipe:[38926]) leaked on pvs invocation. Parent PID 9224: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 4 (/dev/hvc0) leaked on pvs invocation. Parent PID 9224: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 5 (/dev/hvc0) leaked on pvs invocation. Parent PID 9224: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 6 (/dev/hvc0) leaked on pvs invocation. Parent PID 9224: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 (pipe:[38926]) leaked on pvs invocation. Parent PID 9401: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 4 (/dev/hvc0) leaked on pvs invocation. Parent PID 9401: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 5 (/dev/hvc0) leaked on pvs invocation. Parent PID 9401: /bin/sh
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 6 (/dev/hvc0) leaked on pvs invocation. Parent PID 9401: /bin/sh
  Jul  2 08:49:54 main-menu[1425]: INFO: Menu item 'partman-base' selected
  Jul  2 08:52:55 main-menu[1425]: (process:9704): mount: mounting /dev/nvme1n1p1 on /tmp/tmp.6DICJ7 failed: Invalid argument

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