------- Comment From [email protected] 2025-06-18 07:34 EDT------- (In reply to comment #74) > Found a possible fix for this bug > =========================== > > I tried adding multipath module to the installer initrd via initramfs-tools. > This had the effect of initializing multipath during early initrd and before > dm-multipath and lvm were initialized. With this change ( also a possible > bug fix in initramfs-tools described below ) the dm-multipath disks were > properly probed and recognized by probert. > > Possible issue with initramfs-tools > =============================== > > I see initramfs-tools ( to be more accurate ubuntu's multipath-tools > package) only add two scripts: > * init-top to invoke multipathd > * local-bottom to kill the instance of multipathd > > However since local-bottom script will only be invoked if initrd is directly > booting from a multipath disk hence its never invoked during installation > and running instance of multipathd is never killed. This has an unfortunate > side effect of interfering with curtin's multipathd service which fails due > to an existing instance of multipathd running. > > Fixing the possible issue with initramfs-tools and multipath-tools > ======================================================== > To fix this, I copied the local-bottom copy of multipath script to > 'init-bottom' which would be invoked before curtin's init is invoked. This > change ensured that early-init instance of multipathd will be terminated and > new instance of multipath.service from curtin comes up fine. > > Changes suggested > ================ > * Add multipath module to installer initrd via initramfs-tools. So that > multipath volumes are initialized before lvm is initialized. > * Update multipath-tools to also add a init-bottom script to initramfs-tool > scripts so that early-initrd instance of multipathd is terminated before > curtin's multipathd daemon is invoked.
Hello Ubuntu Team, Do you have any updates/suggestions on this possible solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080474 Title: ubuntu installation failing for systems having SAN disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2080474/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
