IMPORTANT: For example, if the array consists of two devices, the command output will not display three lines in the mdadm.conf file–

one line for the array, and a line for each device.

Ensure that those lines are added to the mdadm.conf file so it matches the output of the command.

For more details, see the mdadm and mdadm.conf manpages for your distribution. With these changes, on most systems the RAID 0 array will be created automatically upon restart.

6.If you cannot access /dev/md0 after restart, run the following command: $ mdadm --assemble--scan

You might also want to disable udev loading of the IO Accelerator driver, if needed, and then use the init script provided for driver loading. For more information, see "Using the Init Script (on page 19)."

Making an array persistent

NOTE: On some versions of Linux, the configuration file is located in the /etc/mdadm/mdadm.conf, not /etc/mdadm.conf directory.

Inspect /etc/mdadm.conf. If one or more lines declare the devices to inspect, be sure one of those lines specifies "partitions" as an option by adding a new DEVICE line to the file specifying the "partitions" option:

DEVICE partitions

Add a device specifier for the fio ioMemory devices:

DEVICE /dev/fio*

To verify whether any updates are needed to /etc/mdadm.conf, issue the following command:

$ mdadm --detail --scan

Compare the output of this command to what currently exists in mdadm.conf and add any needed sections to /etc/mdadm.conf.

IMPORTANT: For example, if the array consists of two devices, the command output will not display three lines in the mdadm.conf file–

one line for the array, and a line for each device.

Ensure that those lines are added to the mdadm.conf file so it matches the output of the command.

For more details, see the mdadm and mdadm.conf man pages for your distribution.

With these changes, the RAID 0 array will be created automatically upon restart on most systems. If you have problems accessing /dev/md0 after restart, run the following command:

$ mdadm --assemble --scan

If needed, you can also disable udev loading of the IO Accelerator driver. To load the driver, use the init script.

IMPORTANT: In SLES 11, to be sure these services are run on boot, you might have to run the following commands:

•chkconfig boot.md on

•chkconfig mdadmd on

Software installation 24