Ubuntu
linux package

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

Bug #1918970 reported by Lee Trager
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Incomplete
Undecided
Unassigned
Ubuntu on IBM z Systems
Triaged
Undecided
Skipper Bug Screeners
initramfs-tools (Ubuntu)
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned
s390-tools (Ubuntu)
New
Undecided
Unassigned

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

Frank Heimes (fheimes)
tags: added: s390x
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
Frank Heimes (fheimes)
tags: added: maas
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

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

summary: - 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
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Alternative to all of the above, you could choose to "enable all the devices" hack on 18.04.

Aka if the MAAS initrd includes a script to do `chzdev -e --all` by default on 18.04.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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
tags: added: bionic
Lee Trager (ltrager)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Frank Heimes (fheimes) wrote :

in response to comment #2)

That would be indeed a valid approach (and I think we already had that once in the z13s prototype),
since we run in such a situation always on a system in DPM mode, were one usually have only selected devices configured (compared to a system in PR/SM classic mode, where one often heavily shares devices).

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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
Frank Heimes (fheimes)
tags: added: bot-stop-nagging
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
Bill Wear (billwear)
Changed in maas:
status: New → Triaged
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Solution direction unclear, it does not appear to be a MAAS issue but could be mitigated with changes to MAAS. Perhaps Frank Heimes can advise on the next steps?

Changed in maas:
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.