chreipl aborts - Installation workaround for NVMe IPL
This document (000020258) is provided subject to the disclaimer at the end of this document.
It is typically run at the end of an installer workflow, when the installed system is started for the first time.
Starting with version 2.14, the chreipl tool supports specifying NVMe devices as boot device.
When the target NVMe device supports multipathing, that is when the device's Controller Multi-Path I/O and Namespace Sharing Capabilities indicates that the NVMe subsystem may contain two or more controllers (CMIC bit 1 set).
The chreipl tool aborts with an error message:
chreipl: Could not read from "/sys/block/nvme0n1/device/device/function_id" (No such file or directory)
The target NVMe device is not correctly selected for reboot and the guest will not automatically boot into the installed system.
This is needed for the installer only, not for the installed system.
The actual firmware boot support is not affected.
Assuming everything else is setup properly, a manually initiated boot from the associated NVMe device should still succeed.
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:000020258
- Creation Date: 25-May-2021
- Modified Date:22-Jun-2021
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com