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

[Mathieu Trudel-Lapierre]

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.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1797979

[Andreas Hasenack (ahasenack)]

Is this reproduceable in a ppc64el vm by using the mini.iso to perform an installation? Can you detail what type of installation, disk layout, etc? When does multipath come into play?

[Mathieu Trudel-Lapierre (cyphermox)]

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.

[Christian Ehrhardt  (paelzer)]

I was using your scripts to give it a double check.
I can confirm it used 2 disks with 2 paths each, but it worked every time for me (5x).

I always reached:
  "Please unlock disk mpatha3_crypt:"

No message about "integrity:" seen in any runs.
Your message was super early as the "Quiescing Open Firmware" was just before, or did you remove some lines?

So either there was a setup change since then, or it is racy with a low chance to occur.

[Launchpad Janitor (janitor)]

[Expired for multipath-tools (Ubuntu) because there has been no activity for 60 days.]