[Bug 1797979] Re: [ppc64el] multipath install fails with bad UUID root= setting

[Mathieu Trudel-Lapierre]

It's not reproducible every time; I've done a few more installs and it
looks fine now. Perhaps it's racy.

I was using a VM with 2 disks multipathed.

** Changed in: multipath-tools (Ubuntu)
       Status: New => Incomplete

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

Title:
  [ppc64el] multipath install fails with bad UUID root= setting

Status in multipath-tools package in Ubuntu:
  Incomplete

Bug description:
  I'm unsure what piece is actually causing this, possibly multipath
  postinst for mini.iso:

  instantiating rtas at 0x000000002fff0000... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Quiescing Open Firmware ...
  #11-Ubuntu SMP T[    0.800451] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [    0.800453] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [    2.095870] vio vio: uevent: failed to send synthetic uevent
  fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/sdb2
  fsck exited with status code 8

  mount: mounting /dev/sdb2 on /root failed: Device or resource busy
  mount: mounting /dev on /root/dev failed: No such file or directory
  mount: mounting /dev on /root/dev failed: No such file or directory
  mount: mounting /run on /root/run failed: No such file or directory
  run-init: current directory on the same filesystem as the root: error 0
  Target filesystem doesn't have requested /sbin/init.
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  No init found. Try passing init= bootarg.

  
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  
  None of the very very many options shown (another bug, in os-prober probably) allow the system to boot successfully, but changing root=UUID=whatever to root=/dev/mapper/mpatha-part2 does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1797979/+subscriptions