[Bug 1918970] Re: Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition

[Dimitri John Ledkov]

In https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu3 in
eoan+ manual chzdev -e got added to activate qeth devices, if they have
been specified in the ip= command, i.e. if enc300 is the device in the
ip= command.

This has not been backported to bionic.

To boot without specifying the device name, i.e. with just mac address
one will need automatic chzdev device configuration via
/sys/firmware/sclp_sd/config/data that was added in s390-tools v2.5.0
fist available in cosmic+

but that also needs kernel support for sclp_sd driver to exist, i.e
first added in v4.16.

Thus if one wants this support one will need to backport
1) initramfs-tools changes
2) s390-tools changes
3) linux sclp_sd driver from linux-hwe to GA


** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: s390-tools (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition
+ Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1918970

Title:
  Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition -
  no manual nor automatic qeth device configuration

Status in MAAS:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14
  DPM Partition.  The initrd fails to bring up network and thus fails to
  boot in MAAS. I haven't tried older versions of Ubuntu but suspect
  they also have the same bug.

  mount: mounting /dev on /root/dev failed: No such file or directory
  done.
  mount: mounting /run on /root/run failed: No such file or directory
  run-init: current directory on the same filesystem as the root: error 0
  Target filesystem doesn't have requested /sbin/init.
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  chvt: can't open console
  No init found. Try passing init= bootarg.
  Couldn't get a file descriptor referring to the console
  /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o
  r address
  /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad
  dress
   
   
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
   
  (initramfs) [6n
  [   78.114530] random: crng init done
  [   78.114538] random: 7 urandom warning(s) missed due to ratelimiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions