Comment 6 for bug 1480399

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This appears to be reproducible again on 18.10, except at very early boot (premount):

Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0000000002000000 ...
Linux ppc64le
#11-Ubuntu SMP T[ 0.795638] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
[ 0.795640] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
[ 2.058041] vio vio: uevent: failed to send synthetic uevent
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: PV dgFjip-AMJ8-ZsA9-7e0j-fyJR-lodF-ASXSYz on /dev/sdb2 was already found on /dev/sda2.
  WARNING: PV dgFjip-AMJ8-ZsA9-7e0j-fyJR-lodF-ASXSYz prefers device /dev/sda2 because device was seen first.
  Cannot activate LVs in VG ubuntu-vg while PVs appear on duplicate devices.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: PV dgFjip-AMJ8-ZsA9-7e0j-fyJR-lodF-ASXSYz on /dev/sdb2 was already found on /dev/sda2.
  WARNING: PV dgFjip-AMJ8-ZsA9-7e0j-fyJR-lodF-ASXSYz prefers device /dev/sda2 because device was seen first.
  Cannot activate LVs in VG ubuntu-vg while PVs appear on duplicate devices.

Breaking at premount, to have multipath load before LVM gets to load the devices leads to a system that finishes booting but appears to be in read-only filesystem.