Two things. SCSI_SCAN_ASYNC=y is set from xenial to bionic.
If we believe this is what is causing the race here, we can try booting d-i with a kernel parameter 'scsi_mod.scan=sync' specified. (or i can rebuild d-i with such kernel cmdline built-in if required). And check if that helps to resolve this case. I do wonder, if d-i should be taking the control of the scan itself, meaning, booting with scsi_mod.scan=none and doing `echo "- - -" > /sys/class/scsi_host/*/scan` at the appropriate stage of disk-detect. Or if we do async scan, trigger a rescan at disk-detect stage. `echo 1 > /sys/class/scsi_device/device/rescan` Will be checking the disk-detect / scsi code, to see if it does trigger scans, and if it correctly blocks on said scans to complete. -- 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/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed Bug description: ---Problem Description--- Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based HDD/RAID arrays Tried with current bionic and current bionic-proposed installers wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e ---uname output--- uname -a Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:05:20 UTC 2018 ppc64le GNU/Linux Machine Type = 8247-22L (S822L) ---boot type--- Network boot ---bootloader--- petitboot shell ---Kernel cmdline used to launch install--- #cat /proc/cmdline ---Bootloader protocol--- http ---Install repository type--- Internet repository ---Install repository Location--- US ---Point of failure--- Problem during post-install (stage 2) configuration or other problem seen after reboot =======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: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? ? ? <Go Back> ? ? ? ??????????????????????????????????????????????????????????????????????????? <Tab> moves; <Space> selects; <Enter> activates buttons ~ # lsmod | grep -i ipr ipr 148677 0 ~ # modinfo ipr filename: /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko version: 2.6.4 license: GPL description: IBM Power RAID SCSI Adapter Driver author: Brian King <brk...@us.ibm.com> srcversion: 05BB872A11F65B3A73AB352 alias: pci:v00001014d000004DAsv00001014sd000004FBbc*sc*i* alias: pci:v00001014d000004DAsv00001014sd000004FCbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000004C9bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000004C8bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000004C7bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000049Cbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000049Bbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000049Abc*sc*i* alias: pci:v00001014d0000034Asv00001014sd00000499bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd00000475bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd00000474bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000004CAbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000046Dbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000003FEbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000003FFbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000003FCbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd000003FBbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000035Ebc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000035Dbc*sc*i* alias: pci:v00001014d0000034Asv00001014sd00000357bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd00000355bc*sc*i* alias: pci:v00001014d0000034Asv00001014sd0000033Bbc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd00000354bc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd00000353bc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd00000352bc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd0000035Fbc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd00000356bc*sc*i* alias: pci:v00001014d0000033Dsv00001014sd0000033Cbc*sc*i* alias: pci:v00009005d00000503sv00001014sd000002C3bc*sc*i* alias: pci:v00009005d00000503sv00001014sd000002D5bc*sc*i* alias: pci:v00009005d00000503sv00001014sd000002BFbc*sc*i* alias: pci:v00001014d00000180sv00001014sd00000264bc*sc*i* alias: pci:v00001014d00000339sv00001014sd00000360bc*sc*i* alias: pci:v00001014d00000339sv00001014sd0000035Cbc*sc*i* alias: pci:v00001014d00000339sv00001014sd0000033Abc*sc*i* alias: pci:v00001014d00000339sv00001014sd0000030Abc*sc*i* alias: pci:v00001014d000002BDsv00001014sd00000338bc*sc*i* alias: pci:v00001014d000002BDsv00001014sd000002C2bc*sc*i* alias: pci:v00001014d000002BDsv00001014sd000002C1bc*sc*i* alias: pci:v00009005d00000500sv00001014sd00000338bc*sc*i* alias: pci:v00009005d00000500sv00001014sd000002C2bc*sc*i* alias: pci:v00009005d00000500sv00001014sd000002C1bc*sc*i* alias: pci:v00001014d0000028Csv00001014sd0000030Dbc*sc*i* alias: pci:v00001014d0000028Csv00001014sd000002C0bc*sc*i* alias: pci:v00001014d0000028Csv00001014sd0000028Dbc*sc*i* alias: pci:v00001014d0000028Csv00001014sd000002BEbc*sc*i* alias: pci:v00001069d0000B166sv00001014sd000002D3bc*sc*i* alias: pci:v00001069d0000B166sv00001014sd000002D4bc*sc*i* alias: pci:v00001069d0000B166sv00001014sd00000278bc*sc*i* alias: pci:v00001069d0000B166sv00001014sd00000266bc*sc*i* depends: intree: Y name: ipr vermagic: 4.13.0-32-generic SMP mod_unload mprofile-kernel signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: max_speed:Maximum bus speed (0-2). Default: 1=U160. Speeds: 0=80 MB/s, 1=U160, 2=U320 (uint) parm: log_level:Set to 0 - 4 for increasing verbosity of device driver (uint) parm: testmode:DANGEROUS!!! Allows unsupported configurations (int) parm: fastfail:Reduce timeouts and retries (int) parm: transop_timeout:Time in seconds to wait for adapter to come operational (default: 300) (int) parm: debug:Enable device driver debugging logging. Set to 1 to enable. (default: 0) (int) parm: dual_ioa_raid:Enable dual adapter RAID support. Set to 1 to enable. (default: 1) (int) parm: max_devs:Specify the maximum number of physical devices. [Default=1024] (int) parm: number_of_msix:Specify the number of MSIX interrupts to use on capable adapters (1 - 16). (default:16) (int) parm: fast_reboot:Skip adapter shutdown during reboot. Set to 1 to enable. (default: 0) (int) ~ # ~ # lsscsi [4:3:0:0] no dev IBM 57B4001SISIOA 0150 <-- its detecting one IPR card. ~ # ======================== == Comment: #1 - NAVEED A. UPPINANGADY SALIH <naveed...@in.ibm.com> - 2018-02-21 06:01:18 == Was able to make installer detect IPR based drive Work around is <Go_Back> Detect disks-->Guided partitioning--> Guided - use entire disk ========console logs =========== ?????????????????????????? [!!] 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: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? SCSI3 (2,0,0) (sdc) - 571.3 GB IBM IPR-0 6A98C700 ? ? ? SCSI3 (2,1,0) (sdd) - 1.1 TB IBM IPR-0 6A98C700 ? ? ? SCSI4 (2,0,0) (sde) - 571.3 GB IBM IPR-0 6A985000 ? ? ? SCSI4 (2,1,0) (sdf) - 571.3 GB IBM IPR-0 6A985000 ? ? ? SCSI4 (2,2,0) (sdg) - 571.3 GB IBM IPR-0 6A985000 ? ? ? SCSI4 (2,3,0) (sdh) - 571.3 GB IBM IPR-0 6A985000 ? ? ? SCSI5 (2,0,0) (sdi) - 283.8 GB IBM IPR-0 58E4D100 ? ? ? SCSI5 (2,1,0) (sdj) - 283.8 GB IBM IPR-0 58E4D100 ? ? ? ? <Go Back> ? ? ? ??????????????????????????????????????????????????????????????????????????? <Tab> moves; <Space> selects; <Enter> activates buttons ============================================ == Comment: #5 - Breno Leitao <bren...@br.ibm.com> - 2018-02-26 08:48:31 == it looks like that the ipr driver is loaded in the installer. I am wondering where the problem is. == Comment: #6 - Vaishnavi Bhat <vaish...@in.ibm.com> - 2018-02-26 09:04:33 == Since the IPR based drive is not detectable in the general scenario but only with the workaround, it might be an issue with the installer or the driver being obsolete. But otherwise the ipr module is loaded fine during the installation. Mirroring this bug to the distro for their awareness and being investigated in the IBM side as well. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp