AutoYaST control file fails to detect Multipath devices
This document (7021221) is provided subject to the disclaimer at the end of this document.
Environment
AutoYaST
Device Mapper Multipath Path (DM-MPIO)
Situation
The autoyast file contained the following sections:
<general> <storage> <start_multipath config:type="boolean">true</start_multipath> </storage> </general>
<partitioning config:type="list">
<drive>
<!--
<device>/dev/mapper/3600507680190014da000000000000337</device>
-->
<type config:type="symbol">CT_DISK</type>
</drive>
</partitioning>
Likewise, LIBSTORAGE_MULTIPATH_AUTOSTART=ON was added to the kernel command line using uppercase letters, since the option is case sensitive.
If the <device><drive> is specified, the MPIO device is used for the installation, but fails if it's commented out. Since the customer wants to install many servers, they require the <drive> be commented out so autoyast will auto detect the MPIO drive.
Resolution
Change from this:
<type config:type="symbol">CT_DISK</type>To this:
<type config:type="symbol">CT_DMMULTIPATH</type>
Cause
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:7021221
- Creation Date: 22-Aug-2017
- Modified Date:03-Mar-2020
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com