DASD mapping within installed system does match mapping from installation

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

Environment

SUSE Linux Enterprise Server 10

Situation

Applies to IBM System z.
If installing a system with a fixed list of more than 26 DASDs, the order of the DASDs changes after installation, causing filesystem mounts to fail on the first boot.

Resolution

There are several ways to work around this limitation:

Specify less than 26 DASDs and add the other DASDs later to the installed system
Mount devices by volume label (/dev/disk/by-name/VOLUME), UUID (/dev/disk/by-uuid/UUID) or other persistent device name (e.g.,/dev/disk/by-path/ccw-CCW-part#)
Define the boot device as dasda and use LVM on all other partitions

Additional Information

The initial ramdisk (initrd) does not initialize the DASDs in the same order, resulting in different names for the block device names. An updated version of mkinitrd may be released with SUSE Linux Enterprise Server 10 Service Pack 1

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.