[Bug 1918970] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1918970

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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:
  Incomplete
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