SUSE Support

Here When You Need Us

The boot.log file is missing with s390x systems

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

Environment

SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)

Situation

There is no /var/log/boot.log file found / present on s390x systems.

Resolution

Not having a /var/log/boot.log file created is by default expected with IBM Z systems.

Cause

The Plymouth services are failing on s390x IBM Z Systems with SLES12SPx since these systems do not have any graphics components.

Additional Information

As an alternative it is possible to get the /var/log/boot.log created by removing the plymouth package and instead adding the package blog-plymouth:

zypper rm plymouth plymouth-dracut
zypper in blog blog-plymouth
mkinitrd

On reboot the /var/log/boot.log should then be created. Also see the SLES12 SP3 Release Notes.

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:7023356
  • Creation Date: 17-Sep-2018
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

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

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.

Open an Incident

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