After being back from a few days pto, I'm catching up on this now ... I redid my installation (on z/VM with FCP disks, but on a non-DPM system) leaving here some details: ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Willkommen! Bienvenue! Welcome! Добро пожаловать!┌──────────────────[ Help ]┐ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀│ Help choosing a language │▀ Use UP, DOWN and ENTER keys to select your langua│ Keyboard shortcuts │ │ Enter shell │ [ Asturianu │ View error reports │ [ Bahasa Indonesia ├──────────────────────────┤ [ Català │ About this installer │ [ Deutsch │ Help on SSH access │ [ English └──────────────────────────┘ [ English (UK) ▸ ]█ [ Español ▸ ]█ [ Français ▸ ]█ [ Galego ▸ ]█ [ Hrvatski ▸ ]█ [ Latviski ▸ ] [ Lietuviškai ▸ ] [ Magyar ▸ ] [ Nederlands ▸ ] [ Norsk bokmål ▸ ] [ Occitan (aprèp 1500) ▸ ] [ Polski ▸ ] [ Português ▸ ]▾ ... Installer shell session activated. This shell session is running inside the installer environment. You will be returned to the installer when this shell is exited, for example by typing Control-D or 'exit'. Be aware that this is an ephemeral environment. Changes to this environment will not survive a reboot. If the install has started, the installed system will be mounted at /target. root@ubuntu-server:/# cat /proc/cmdline %@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ root@ubuntu-server:/# uname -a Linux ubuntu-server 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux root@ubuntu-server:/# snap list subiquity Name Version Rev Tracking Publisher Notes subiquity 23.02.1 4383 latest/stable/… canonical** classic root@ubuntu-server:/# python3 --version Python 3.10.6 root@ubuntu-server:/# ls -lad /var/log drwxrwxr-x 1 root syslog 320 Apr 19 10:18 /var/log root@ubuntu-server:/# lszdev --online TYPE ID ON PERS NAMES qeth 0.0.0600:0.0.0601:0.0.0602 yes no enc600 generic-ccw 0.0.0009 yes no root@ubuntu-server:/# ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Zdev setup ┌──────────────[ Help ]┐ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀│ Help on this screen │▀ 0.0.0400 │ Keyboard shortcuts │ 0.0.0592 │ Enter shell │ │ View error reports │ qeth ├──────────────────────┤ 0.0.0600:0.0.0601:0.0.0602 enc600│ About this installer │ 0.0.0603:0.0.0604:0.0.0605 │ Help on SSH access │ └──────────────────────┘ dasd-eckd 0.0.1607 ▸ █ █ zfcp-host █ 0.0.f00b online ▸ █ 0x50050763060b16b6:0x4026400600000000 sdb sg1 █ 0x50050763061b16b6:0x4026400600000000 sda sg0 █ 0.0.f10b online ▸ █ 0x50050763060b16b6:0x4026400600000000 sdc sg2 █ 0x50050763061b16b6:0x4026400600000000 sdd sg3 ▾ [ Continue ] [ Back ] root@ubuntu-server:/# lszdev --online TYPE ID ON PERS NAMES zfcp-host 0.0.f00b yes yes zfcp-host 0.0.f10b yes yes zfcp-lun 0.0.f00b:0x50050763060b16b6:0x4026400600000000 yes no sdb sg1 zfcp-lun 0.0.f00b:0x50050763061b16b6:0x4026400600000000 yes no sda sg0 zfcp-lun 0.0.f10b:0x50050763060b16b6:0x4026400600000000 yes no sdc sg2 zfcp-lun 0.0.f10b:0x50050763061b16b6:0x4026400600000000 yes no sdd sg3 qeth 0.0.0600:0.0.0601:0.0.0602 yes no enc600 generic-ccw 0.0.0009 yes no root@ubuntu-server:/# multipath -ll mpatha (36005076306ffd6b60000000000002606) dm-0 IBM,2107900 size=64G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:1:1074151462 sdb 8:16 active ready running |- 0:0:0:1074151462 sda 8:0 active ready running |- 1:0:1:1074151462 sdd 8:48 active ready running `- 1:0:0:1074151462 sdc 8:32 active ready running root@ubuntu-server:/# ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Guided storage configuration [ Help ] ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Configure a guided storage layout, or create a custom one: (X) Use an entire disk ▴ █ [ 0x6005076306 multipath device 64.000G ▾ ]█ ffd6b6000000 █ 0000002606 █ █ [X] Set up this disk as an LVM group █ █ [ ] Encrypt the LVM group with LUKS █ █ Passphrase: █ █ Confirm passphrase: ▾ [ Done ] [ Back ] ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Storage configuration [ Help ] ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ FILE SYSTEM SUMMARY ▴ █ MOUNT POINT SIZE TYPE DEVICE TYPE █ [ / 30.996G new ext4 new LVM logical volume ▸ ] █ [ /boot 2.000G new ext4 new partition of multipath device ▸ ] █ █ █ AVAILABLE DEVICES █ █ DEVICE TYPE SIZE [ ubuntu-vg (new) LVM volume group 61.996G ▸ ] free space 31.000G ▸ [ Create software RAID (md) ▸ ] [ Create volume group (LVM) ▸ ] ▾ [ Done ] [ Reset ] [ Back ] ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Storage configuration [ Help ] ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ FILE SYSTEM SUMMARY ▴ █ ┌────────────────────── Confirm destructive action ──────────────────────┐ │ │ │ Selecting Continue below will begin the installation process and │ │ result in the loss of data on the disks selected to be formatted. │ │ │ │ You will not be able to return to this or a previous screen once the │ │ installation has started. │ │ │ │ Are you sure you want to continue? │ │ │ │ [ No ] │ │ [ Continue ] │ │ │ └────────────────────────────────────────────────────────────────────────┘ [ Reset ] [ Back ] ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Install complete! [ Help ] ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ┌──────────────────────────────────────────────────────────────────────────┐ │ configuring multipath ▴│ │ updating packages on target system │ │ configuring pollinate user-agent on target │ │ updating initramfs configuration │ │ configuring target system bootloader │ │final system configuration │ │ configuring cloud-init │ │ calculating extra packages to install │ │ installing openssh-server │ │ curtin command system-install │ │ downloading and installing security updates │ │ curtin command in-target │ │ restoring apt configuration │ │ curtin command in-target █│ │subiquity/Late/run ▾│ └──────────────────────────────────────────────────────────────────────────┘ [ View full log ] [ Reboot Now ] So all good here. But a couple of obversations / comments: You mentioned that wiping out older or addditional LUNs is not an option. And I think it's not needed, only thought about wiping the LUNs for the OS itself and only enable this OS LUN during installaltion. Any additional LUNs can be easily added post-install and should not be enabled at install time (here, for testing and to be on the safe side). (I think that's easier compared to disabling them on the SAN side ...) If you do a 'normal' install, there is no need to add anything to the parmfile, and by default the parmfile only containes a single line like this (without quotes): " --- " And make sure the parm file is in the correct encoding (fix length "F 80" or variable, "Trunc=80"): PARMFILE UBUNTU O1 F 80 Trunc=80 Size=4 Line=0 Col=1 Alt=0 00000 * * * Top of File * * * 00001 --- 00002 * * * End of File * * * The 3 dashes (" --- ") are to separate installer from kernel arguments. " --- " And if you do such a plain and simple install, you will be asked at the console to specify some basic network related data, incl. the qeth that should be used for the installation. (I guess I should double-check if this is clearly stated in the docs ...) If you don't want to specify this data manually at the early boot stage, you can add this to the parmfile (like I guess you tried). Looking at your parmfile: "ip=9.11.116.213::9.11.116.1:24:255.255.255.0:ilabg13:ence0f:none:9.11.227.25" I think it's not fully correct, since the ":24" is not needed or even wrong there. It should be like: "ip=9.11.116.213::9.11.116.1:255.255.255.0:ilabg13:ence0f:none:9.11.227.25 --- " (so in your case gw and dns are differen systems, right?) But again, for figuring out any install issues, I would go with a standard installation first (means with specifying this data at the early boot stage at the console.) At the early boot stage it's about "interactive netboot" and asks for network information only and all network devices are qeth (of course except RoCE) - so don't specify any other devices here (like HBAs or LUNS)'or whatever). And the term "zdev" comes from the lszdev and chzdev commands, hence it was also used for the 'zdev" UI installer screen, so in my case: " Attempt interactive netboot from a URL? yes no (default yes): yes Available qeth devices: 0.0.0600 0.0.0603 zdev to activate (comma separated, optional): " If you would like to see some changes in the terminology that is used here, we are of course open for any ... I believe that the content of the kernel parameter with all the "@" is more a representaton issue (nevertheless, not very nice though ...), but since it works for me on my system - and even with much more kernel args that are needed in case of a fully non-interactive "autoinstall". What I noticed in the crash file is the following snippet: " 2023-04-06 19:17:21,139 DEBUG subiquitycore.utils:77 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0 2023-04-06 19:17:21,139 ERROR subiquity.server.server:424 top level error Traceback (most recent call last): File "/snap/subiquity/4383/usr/lib/python3.8/asyncio/events.py", line 81, in _run self._context.run(self._callback, *self._args) File "/snap/subiquity/4383/lib/python3.8/site-packages/subiquity/server/controllers/filesystem.py", line 682, in _udev_event action, dev = self._monitor.receive_device() File "/snap/subiquity/4383/lib/python3.8/site-packages/pyudev/monitor.py", line 400, in receive_device device = self.poll() File "/snap/subiquity/4383/lib/python3.8/site-packages/pyudev/monitor.py", line 358, in poll if eintr_retry_call(poll.Poll.for_events((self, "r")).poll, timeout): File "/snap/subiquity/4383/lib/python3.8/site-packages/pyudev/_util.py", line 164, in eintr_retry_call return func(*args, **kwargs) File "/snap/subiquity/4383/lib/python3.8/site-packages/pyudev/_os/poll.py", line 94, in poll return list(self._parse_events(eintr_retry_call(self._notifier.poll, timeout))) File "/snap/subiquity/4383/lib/python3.8/site-packages/pyudev/_os/poll.py", line 109, in _parse_events raise IOError("Error while polling fd: {0!r}".format(fd)) OSError: Error while polling fd: 20 2023-04-06 19:17:21,142 DEBUG subiquity.common.errorreport:384 generating crash report 2023-04-06 19:17:21,143 INFO subiquity.common.errorreport:406 saving crash report 'unknown error crashed with OSError' to /var/crash/1680808641.142762184.unknown.crash 2023-04-06 19:17:21,143 INFO root:37 start: subiquity/ErrorReporter/1680808641.142762184.unknown/add_info: 2023-04-06 19:17:21,143 INFO root:37 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "ERROR", "confirming_tty": "", "error": {"state": "INCOMPLETE", "ba... 2023-04-06 19:17:21,144 INFO root:37 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "ERROR", "confirming_tty": "", "error": {"state": "INCOMPLETE", "ba... 2023-04-06 19:17:21,144 INFO root:37 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "ERROR", "confirming_tty": "", "error": {"state": "INCOMPLETE", "ba... 2023-04-06 19:17:21,144 INFO root:37 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "ERROR", "confirming_tty": "", "error": {"state": "INCOMPLETE", "ba... 2023-04-06 19:17:21,144 DEBUG subiquitycore.utils:64 run_command called: ['udevadm', 'settle', '-t', '0'] InstallerServerLogInfo: 2023-04-06 19:04:23,061 INFO subiquity:161 Starting Subiquity server revision 4383 " That could be a problem with asyncio (I remember that there was an issue with asyncio in the past) or a race condition. I'll ask my installer colleague to have a look at this ...