------- Comment From [email protected] 2024-12-02 03:12 EDT------- Hi Frank,
Sorry for the late reply. Please find the information below: (In reply to comment #44) > 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 > ? root@ubuntu-server:/# multipath -ll mpatha (360050768108001b3a8000000000002f5) dm-1 IBM,2145 size=20G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | `- 1:0:1:0 sdd 8:48 active ready running `-+- policy='service-time 0' prio=10 status=enabled `- 1:0:0:0 sdb 8:16 active ready running root@ubuntu-server:/# lscpu Architecture: ppc64le Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Model name: POWER10 (architected), altivec supported Model: 2.0 (pvr 0080 0200) Thread(s) per core: 8 Core(s) per socket: 3 Socket(s): 4 Virtualization features: Hypervisor vendor: pHyp Virtualization type: para Caches (sum of all): L1d: 768 KiB (24 instances) L1i: 1.1 MiB (24 instances) L2: 24 MiB (24 instances) L3: 96 MiB (24 instances) NUMA: NUMA node(s): 4 NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Reg file data sampling: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1: Mitigation; __user pointer sanitization, ori31 specula tion barrier enabled Spectre v2: Mitigation; Software count cache flush (hardware accel erated), Software link stack flush Srbds: Not affected Tsx async abort: Not affected root@ubuntu-server:/# lsmem RANGE SIZE STATE REMOVABLE BLOCK 0x0000000000000000-0x0000003fffffffff 256G online yes 0-1023 Memory block size: 256M Total online memory: 256G Total offline memory: 0B > > 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? Please note that we can recreate this problem consistently on our setup with Ubuntu 24.04.1 and Fedora 40 installations on the LPAR. In addition to that, it's just a single OS setup. Please let me know if there's any specific information I may help you with. Thanks, Amit -- 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
