Freshly installed SLES system does not start correctly on IBM mainframe

This document (7001198) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Server 9
 

Situation

The installed system does not boot completely after installation: some services are missing and the login prompt does not appear on the 3270 terminal. The last messages on the 3270 terminal are some kernel messages, input on the terminal does not have any effect. However, SSH login is possible. Executing the command runlevel outputs unknown.

Resolution

The reason is that the installation has not finished yet. This happens automatically on all architectures that have a graphical display or a non-block mode text mode terminal. However, since the S/390 or zSeries does not have either and Linux cannot use the 3270 terminal fully, some user interaction is necessary:

X11 Installation

Make sure the X11 server is running on the same system used to install the system when IPLing the installed system. A window with YaST2 will open and finish the installation.

VNC Installation

A message on the 3270 terminal will ask you to connect with a VNC client to the Linux system. The message is probably hidden between kernel messages and is easily missed or the terminal clears the screen before you can read it. In that case, connect the VNC viewer to the Linux system if nothing seems to happen for more than five minutes.

SSH Installation

Same effect as with the VNC installation: the message to connect to the Linux system with SSH can be missed easily. Perform the following steps when the system seems to have stopped:

  1. Use SSH to log in to the Linux system as user root. If you get a connection time-out or connection refused message, try again after a couple minutes
  2. Run the command "/usr/lib/YaST2/bin/YaST2.sshinstall" (not just "yast")
  3. After YaST2 has finished the initialization, log out of the session (if the system does not do it for you). Watch the 3270 terminal: the system should now change to a runlevel and complete the boot process.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7001198
  • Creation Date: 22-Aug-2008
  • Modified Date:06-Mar-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center