After the above broken autoinstall attempt, I was not able to wipe the disks directly, since I couldn't enter the console.
So I started an interactive install (of 26.10) expecting it to crash (and it did). FWIW I gathered the logs again, also the output of 'udevadm info --export-db' before and after the crash (the other two commands just showed the same). And btw. in the zdev screen all the multipath devices look okay. I then wiped out the disks and could successfully complete an interactive install with 26.10. So there seems to be something different between 26.04 (that allows to install over an existing installation) and 26.10 (that does crash). (While doing all that, I changed the LVM volume size, that is by default only 50% of the capacity, to the max by just deleting the size and I faced a crash. Since this is unrelated to this bug, I open a separate ticket about it ...) ** Attachment added: "logs_Sept_3rd.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/2165993/+attachment/5997231/+files/logs_Sept_3rd.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165993 Title: Ubuntu 26.10/stonking installation (image from Aug 31st) crashes on s390x (due to probert) To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2165993/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
