System information

Encrypting Block Devices Using LUKS
Formatting a block device for encryption using LUKS/d m-crypt will destroy any existing formatting
on that device. As such, you should decide which devices to encrypt (if any) before the new system's
storage configuration is activated as part of the installation process.
Stale BIOS RAID Metadata
Moving a disk from a system configured for firmware RAID without removing the RAID metadata from
the disk can prevent An aco n d a from correctly detecting the disk.
Warning
Removing/deleting RAID metadata from disk could potentially destroy any stored data. Red
Hat recommends that you back up your data before proceeding.
To delete RAID metadata from the disk, use the following command:
d mrai d -r -E /device/
For more information about managing RAID devices, refer to man d mrai d and Chapter 17,
Redundant Array of Independent Disks (RAID).
iSCSI Detection and Configuration
For plug and play detection of iSCSI drives, configure them in the firmware of an iBFT boot-capable
network interface card (NIC). CHAP authentication of iSCSI targets is supported during installation.
However, iSNS discovery is not supported during installation.
FCoE Detection and Configuration
For plug and play detection of fibre-channel over ethernet (FCoE) drives, configure them in the firmware
of an EDD boot-capable NIC.
DASD
Direct-access storage devices (DASD) cannot be added/configured during installation. Such devices
are specified in the CMS configuration file.
Block Devices with DIF/DIX Enabled
DIF/DIX is a hardware checksum feature provided by certain SCSI host bus adapters and block
devices. When DIF/DIX is enabled, errors will occur if the block device is used as a general-purpose
block device. Buffered I/O or mmap(2)-based I/O will not work reliably, as there are no interlocks in
the buffered write path to prevent buffered data from being overwritten after the DIF/DIX checksum has
been calculated.
Encrypt ing Block Devices Using LUKS
83