[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
Hi Amit, work on this had to be paused due to the 25.04 release and Sprints, but will likely be picked up again soon in July. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
Note that when installing Ubuntu with LVM + multipath, curtin adds a filter for LVM. This allows the target system to avoid the situation where LVM "steals" /dev/sdN devices that would normally be used by multipath. $ grep filter /target/etc/lvm/lvm.conf filter = [ "a|/dev/disk/by-id/dm-uuid-.*mpath-.*|", "a|/dev/disk/by-id/.*dm_crypt-.*|", "r|.*|" ] Unfortunately, we can't really use that filter in the live environment - since it would prevent LVM to work when multipath is not involved. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
I did further analysis on amd64 + qemu today. I figured that the EBUSY error is caused by LVM creating a DM entry (e.g. ubuntu--vg-ubuntu--lvm on a typical install) using paths such as /dev/sda and /dev/sdb - before multipathd has a chance to start and create the /dev/mapper/mpatha device. After boot: $ multipath -ll $ pvs WARNING: Not using device /dev/sdb3 for PV [...] WARNING: PV [...] prefers device /dev/sda3 because device is used by LVM. PV VGFmt Attr PSize PFree /dev/sda3 ubuntu-vg lvm2 a-- <6.25g0 $ journalctl -u multipathd ubuntu-server multipathd[941]: mpatha: addmap [0 16777216 multipath 0 0 2 1 service-time 0 1 1 8:0 1 service-time 0 1 1 8:16 1] ubuntu-server multipathd[941]: libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:1) failed: Device or resource busy ubuntu-server multipathd[941]: dm_addmap: libdm task=0 error: Device or resource busy ubuntu-server multipathd[941]: mpatha: ignoring map $ ls /dev/mapper/ control ubuntu--vg-ubuntu--lv At this point restarting multipathd does not help - it still fails with EBUSY. However, after removing the /dev/mapper entry created by LVM and restarting multipathd, the situation becomes as expected, and the installation can proceed. $ dmsetup remove /dev/mapper/ubuntu--vg-ubuntu--lv $ systemctl restart multipathd $ multipath -ll mpatha (0QEMU_QEMU_HARDDISK_MPIO) dm-0 QEMU,QEMU HARDDISK size=8.0G features='0' hwhandler='0' wp=rw |-+- policy='service-time 0' prio=1 status=active | `- 0:0:0:0 sda 8:0 active ready running `-+- policy='service-time 0' prio=1 status=enabled `- 0:0:1:0 sdb 8:16 active ready running $ ls /dev/mapper control mpatha mpatha-part1 mpatha-part2 mpatha-part3 ubuntu--vg-ubuntu--lv $ pvs PV VGFmt Attr PSize PFree /dev/mapper/mpatha-part3 ubuntu-vg lvm2 a-- <6.25g0 I wonder if we should make multipathd run before LVM? And is it going to address the issue originally reported - or only what we were able to reproduce using qemu on amd64. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
For some reason, running the above steps without involving LVM (i.e., [ ] Set up this disk as an LVM group) allows the disk to be detected properly during the second installation ; and then it succeeds. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
I run the same steps as Christian did and observed the same symptoms. However > [...] the installer properly detected the disk state. Only on actually going to deployment did it crash. Yes, it crashes but the state of the disks were not correctly detected during the second install. Instead of a single multipath disk, it detected two separate disks with the same label, offering to partition each disk separately. See the list of "USED DEVICES" in https://bugs.launchpad.net/subiquity/+bug/2080474/comments/48 compared to https://bugs.launchpad.net/subiquity/+bug/2080474/comments/47. The type "local disk" should also be "multipath device". The installation errors when we attempt to run `lvcreate`: Running command ['lvcreate', 'ubuntu-vg-1', '--name', 'ubuntu-lv', '--zero=y', '--wipesignatures=y', '--yes', '--size', '6706692096B'] with allowed codes [0] (capture=False) WARNING: Not using device /dev/sda3 for PV 5tXJHt-wdEZ-WBCP-BFQ6-GVGL-IyWe-UUH32z WARNING: PV 5tXJHt-wdEZ-WBCP-BFQ6-GVGL-IyWe-UUH32z prefers device /dev/sdb3 because device is used by LV. Cannot update volume group ubunt-vg-1 with duplicate PV devices. Now, the crash is different from what was originally reported (here's it's failing when installing vs the original report is about failure during detection). But I suspect that being unable to see the device has a multipath device is at least part of the problem in both scenarios. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: multipath-tools (Ubuntu) Status: Incomplete => New ** Changed in: subiquity Status: Incomplete => New ** Changed in: subiquity (Ubuntu) Milestone: None => ubuntu-25.10 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
No, it's not fixed yet - we are still investigating whether we can tackle the root course of the issue, or just catch the error and go with the suggested workaround. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Attachment added: "initial storage config in install #1" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2080474/+attachment/5863776/+files/Screenshot%20from%202025-03-10%2018-28-41.png -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Attachment added: "initial storage config detail in install #1" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2080474/+attachment/5863777/+files/Screenshot%20from%202025-03-10%2018-29-07.png -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
I was retrying the same on x86 just t see if it is arch depending at all. But to start with, when using disks as fake multipath via kvm they should not use metadata (qcow2) nor caching. Hence changing that to format=raw,cache=none $ qemu-img create -f raw /tmp/ubuntu-disk.raw 8G Formatting '/tmp/ubuntu-disk.raw', fmt=raw size=858993459 $ qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -boot menu=on \ -device virtio-scsi-pci,id=scsi -drive if=none,id=mpatha,file=/tmp/ubuntu-disk.raw,format=raw,cache=none,file.locking=off \ -device scsi-hd,drive=mpatha,serial=MPIO \ -drive if=none,id=mpathb,file=/tmp/ubuntu-disk.raw,format=raw,cache=none,file.locking=off \ -drive file=/tmp/ubuntu-24.04.2-live-server-amd64.iso,media=cdrom \ -device scsi-hd,drive=mpathb,serial=MPIO \ -net nic,model=virtio \ -net user,hostfwd=::-:22 \ ... I ran this right on my system, so no need to mess with -nographic. In hindsight that made copying output screenshots :-/ Install #1 worked fine I tried to stay as default as possible, which in regard to disks gave me (see screenshots that follow) Install #2 onto the same - for a more relaxed approach than hitting keys fast I added "-boot d" to this second invocation of qemu It fails and I see the same -EBUSY messages. But aren't those red-herrings as that is from boot and the installer properly detected the disk state. Only on actually going to deployment did it crash. I've sent the full report so Dan can compare that with what was attached by IBM. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Attachment added: "install #2 - crash handler popup" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2080474/+attachment/5863779/+files/Screenshot%20from%202025-03-10%2018-51-27.png -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Attachment added: "storage config detail in install #2 (one can see it detected the former state)" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2080474/+attachment/5863778/+files/Screenshot%20from%202025-03-10%2018-50-07.png -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
--- Comment From amit.machhi...@ibm.com 2025-02-18 14:00 EDT---
Hi Olivier,
I further tried recreating this installer crash with multipath disks on a Qemu
setup. I followed the below steps:
1. Download the Ubuntu 24.04.1 iso from here:
https://cdimage.ubuntu.com/releases/noble/release/ubuntu-24.04.1-live-server-ppc64el.iso
2. Create a qcow2 for provisioning a Ubuntu 24.04.1 guest
qemu-img create -f qcow2 /home/amachhiw/images/ubunut-disk.qcow2 10G
3. Provision a guest with multipath disk configuration by running the
following Qemu command line. The guest provisioning goes fine as
expected.
qemu-system-ppc64 \
-enable-kvm \
-m 4G \
-smp 2 \
-boot menu=on \
-device spapr-vscsi,id=scsi \
-drive
if=none,id=mpatha,file=/home/amachhiw/images/multipath-disk.qcow2,format=qcow2,file.locking=off
\
-device scsi-hd,drive=mpatha,serial=MPIO \
-drive
if=none,id=mpathb,file=/home/amachhiw/images/multipath-disk.qcow2,format=qcow2,file.locking=off
\
-drive
file=/home/amachhiw/images/ubuntu-24.04.1-live-server-ppc64el.iso,media=cdrom \
-device scsi-hd,drive=mpathb,serial=MPIO \
-net nic,model=virtio \
-net user,hostfwd=::15447-:22 \
-nographic
5. Try a re-provision of the guest:
a. Once provisioning completes and reach to the login prompt, just login
and reboot.
b. Keep hitting F12 for getting into the boot menu and boot from the
cdrom
6. Follow the on-screen instructions for proceeding on the installer.
Eventually, during the installation, the installer crashes with the below
Traceback
Traceback (most recent call last):
File
"/snap/subiquity/6065/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File "/snap/subiquity/6065/lib/python3.10/site-packages/curtin/log.py", line
97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File "/snap/subiquity/6065/lib/python3.10/site-packages/curtin/log.py", line
79, in log_time
return func(*args, **kwargs)
File
"/snap/subiquity/6065/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 118, in block_meta
meta_clear(devices, state.get('report_stack_prefix', ''))
File
"/snap/subiquity/6065/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 2213, in meta_clear
clear_holders.clear_holders(devices)
File
"/snap/subiquity/6065/lib/python3.10/site-packages/curtin/block/clear_holders.py",
line 638, in clear_holders
shutdown_function(dev_info['device'])
File
"/snap/subiquity/6065/lib/python3.10/site-packages/curtin/block/clear_holders.py",
line 138, in shutdown_lvm
util.subp(['lvremove', '--force', '--force', vg_lv_name])
File "/snap/subiquity/6065/lib/python3.10/site-packages/curtin/util.py", line
323, in subp
return _subp(*args, **kwargs)
File "/snap/subiquity/6065/lib/python3.10/site-packages/curtin/util.py", line
172, in _subp
raise ProcessExecutionError(stdout=out, stderr=err,
curtin.util.ProcessExecutionError: Unexpected error while running command.
Command: ['lvremove', '--force', '--force', 'ubuntu-vg/ubuntu-lv']
Though this is not exactly the same as the original issue being discussed in the
bugzilla, I have again been able to recreate this installer crash with 100% hit.
Additionally, I observe the above errors mentioned in
https://bugzilla.linux.ibm.com/show_bug.cgi?id=208604#c51
as well. Pasting the snippet of those errors below:
dmesg
-
root@ubuntu:~# cat dmesg.log | grep -i device-mapper
[0.148915] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled.
Duplicate IMA measurements will not be recorded in the IMA log.
[0.148929] device-mapper: uevent: version 1.0.3
[0.148993] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised:
dm-de...@redhat.com
[8.671602] systemd[1]: Listening on dm-event.socket - Device-mapper event
daemon FIFOs.
[8.937037] systemd[1]: Starting multipathd.service - Device-Mapper
Multipath Device Controller...
[9.628257] device-mapper: multipath service-time: version 0.3.0 loaded
[9.628444] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[9.628553] device-mapper: ioctl: error adding target to table
[9.650510] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[9.650593] device-mapper: ioctl: error adding target to table
[24100.057137] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[24100.057146] device-mapper: ioctl: error adding target to table
[24100.058323] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[24100.058328] device-mapper: ioctl: error adding target to table
[24230.276605] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[24230.276612] device-mapper: ioctl: error adding target to table
[24230.284808] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[24230.284812] device-mapper: ioctl: error adding target to table
multipath-tools
---
root@ubuntu:~# systemctl status multipath-tools
* multipathd.service - Device-Mapper Multipath
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
Hello,
I tried to reproduce the issue again today. Although this time the
installer didn't crash ("$ vgs" and "$ lvs" returned valid information),
I was in a scenario somewhat similar to what I described in comment 29:
$ dmesg
[ 1221.355112] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[ 1221.355116] device-mapper: ioctl: error adding target to table
[ 1221.32] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[ 1221.34] device-mapper: ioctl: error adding target to table
[ 1232.281218] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[ 1232.281223] device-mapper: ioctl: error adding target to table
[ 1232.281668] device-mapper: table: 252:1: multipath: error getting device
(-EBUSY)
[ 1232.281670] device-mapper: ioctl: error adding target to table
$ systemctl status multipath-tools
* multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled;
preset: enabled)
Active: active (running) since Wed 2025-02-12 12:36:57 UTC; 20min ago
TriggeredBy: * multipathd.socket
Main PID: 911 (multipathd)
Status: "up"
Tasks: 7
Memory: 20.3M (peak: 20.5M)
CPU: 213ms
CGroup: /system.slice/multipathd.service
`-911 /sbin/multipathd -d -s
Feb 12 12:36:57 ubuntu-server multipathd[911]: libdevmapper:
ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:1)
failed: Device or resource busy
Feb 12 12:36:57 ubuntu-server multipathd[911]: dm_addmap: libdm task=0 error:
Device or resource busy
Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: ignoring map
Feb 12 12:36:57 ubuntu-server multipathd[911]: sda: setting scsi timeouts is
unsupported for protocol scsi:unspec
Feb 12 12:36:57 ubuntu-server multipathd[911]: sdb: setting scsi timeouts is
unsupported for protocol scsi:unspec
Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: addmap [0 25165824
multipath 0 0 2 1 service-time 0 1 1 8:0 1 service-time 0 1 1 8:16 1]
Feb 12 12:36:57 ubuntu-server multipathd[911]: libdevmapper:
ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:1)
failed: Device or resource busy
Feb 12 12:36:57 ubuntu-server multipathd[911]: dm_addmap: libdm task=0 error:
Device or resource busy
Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: ignoring map
Feb 12 12:36:57 ubuntu-server systemd[1]: Started multipathd.service -
Device-Mapper Multipath Device Controller.
$ multipath
1232.283332 | sda: setting scsi timeouts is unsupported for protocol scsi:unspec
1232.283343 | sdb: setting scsi timeouts is unsupported for protocol scsi:unspec
1232.283368 | mpatha: addmap [0 25165824 multipath 0 0 2 1 service-time 0 1 1
8:0 1 service-time 0 1 1 8:16 1]
1232.283518 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload
ioctl on mpatha (252:1) failed: Device or resource busy
1232.283568 | dm_addmap: libdm task=0 error: Device or resource busy
1232.283604 | mpatha: ignoring map
1232.283906 | sda: setting scsi timeouts is unsupported for protocol scsi:unspec
1232.283909 | sdb: setting scsi timeouts is unsupported for protocol scsi:unspec
1232.283918 | mpatha: addmap [0 25165824 multipath 0 0 2 1 service-time 0 1 1
8:0 1 service-time 0 1 1 8:16 1]
1232.283963 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload
ioctl on mpatha (252:1) failed: Device or resource busy
1232.283988 | dm_addmap: libdm task=0 error: Device or resource busy
1232.284177 | mpatha: ignoring map
Could you check if you're seeing any of the above errors? Ideally, would
you mind sharing the journal logs + dmesg.log?
Thank you,
Olivier
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Changed in: multipath-tools (Ubuntu) Status: New => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
Hi Amit, so far we faild to recreate this case, neither on ppc64el nor on a different platform. So first of all the recommendation (and to unblock in such cases) is still the workaround mentioned here: https://bugs.launchpad.net/subiquity/+bug/2080474/comments/4 We briefly discussed if the disk setup was maybe created by a different OS (like AIX) and that we may could implement the workaround in a better way. You mentioned that this also happens with FC40, that might be an indication that is only happens with a relatively modern multipath stack. Do you have mor information about the FC40 case, maybe an upstream bug, that allows to join forces? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Changed in: ubuntu-power-systems Status: In Progress => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Changed in: subiquity Status: New => Incomplete -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
@iranna It looks like sent some questions on the 11th, would you review those? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
Now trying to find some differences in the systems, you already shared the lsblk output in comment #26. Would you mind also sharing the output of: multipath -ll lscpu and lsmem ? And the existing disk configuration (before the wipefs), where did it came from - or how was it generated? Was it a previous Ubuntu installation (which release), or a different Linux OS (like RH, which release?) or even a different OS (partially), like AIX? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
FYI Frank and I tried to recreate for debugging, but failed to trigger the symptom so far. Used a multipath setup with 4 paths and 5 disks, passed into a KVM guest for some debuggability. Inside the guest we created PV/VG/LV to represent the issues that were described. Then we started the installation from a ISO on that system (10 times), but it always came up with all mpaths detected. Next we changed resources to be really tight - in case that would be the reason, still working. Next we broke some of the VG/LVM config, but while VG/LVM partially broke it never affected probert and/or subiquity in any way. For comparison purpose here the config used and the detection the guest then had on the devices. root@ubuntu-server:/# multipath -ll mpatha (36005076306ffd6b62402) dm-0 IBM,2107900 size=10G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 1:0:0:0 sdn 8:208 active ready running |- 1:0:0:5 sdp 8:240 active ready running |- 0:0:0:3 sde 8:64 active ready running `- 2:0:0:1 sdl 8:176 active ready running mpathb (36005076306ffd6b62403) dm-1 IBM,2107900 size=10G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 1:0:0:1 sdt 65:48 active ready running |- 1:0:0:6 sdo 8:224 active ready running |- 0:0:0:4 sdd 8:48 active ready running `- 2:0:0:2 sdm 8:192 active ready running mpathc (36005076306ffd6b6240a) dm-2 IBM,2107900 size=10G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 1:0:0:2 sds 65:32 active ready running |- 0:0:0:0 sda 8:0 active ready running |- 0:0:0:5 sdc 8:32 active ready running `- 2:0:0:3 sdk 8:160 active ready running mpathd (36005076306ffd6b62423) dm-3 IBM,2107900 size=64G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 1:0:0:3 sdr 65:16 active ready running |- 0:0:0:1 sdg 8:96 active ready running |- 0:0:0:6 sdb 8:16 active ready running `- 2:0:0:4 sdj 8:144 active ready running mpathe (36005076306ffd6b62424) dm-4 IBM,2107900 size=64G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 1:0:0:4 sdq 65:0 active ready running |- 0:0:0:2 sdf 8:80 active ready running |- 2:0:0:0 sdh 8:112 active ready running `- 2:0:0:5 sdi 8:128 active ready running n-testmultipath 8 8 4 hvm destroy restart destroy /usr/bin/qemu-system-s390x -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Tags added: installation -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
here's what I remember observing on the platform where we reproduced the issue. If more is needed, we need to redo the same setup * dmesg was showing the following errors: > device-mapper: multipath: error getting device > device-mapper: ioctl: error adding target to table * restarting multipathd (systemctl restart multipathd) would cause the above errors to be shown again. * fdisk would show sda, sdb, sdc, sdd but no mpatha device. * LVM tools (vgs, pvs, lvms) would return no output; although udev would show partitions used as PVs as "lvm_member" -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
It looks like we could reproduce this on a different platform. And it seems to be a race condition in multipath itself, hence adding multipath-tools as affected package. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Also affects: subiquity Importance: Undecided Status: New ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: ubuntu-power-systems Importance: Undecided => High -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
