en-US/Grub.xml

[Rüdiger Landmann]

 en-US/Grub.xml |   10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

New commits:
commit 71c9e8722d7d32aa88b1aa9d5128a95bde39ecc9
Author: Ruediger Landmann <r.landmann at redhat.com>
Date:   Tue Jan 12 15:27:07 2010 +1000

    Explain RAID issues -- BZ#553509

diff --git a/en-US/Grub.xml b/en-US/Grub.xml
index 5646923..4fd33d8 100644
--- a/en-US/Grub.xml
+++ b/en-US/Grub.xml
@@ -316,13 +316,19 @@
 		</para>
 		 
 		<important>
-			<title>Important</title>
+			<title>Important — GRUB and RAID</title>
 			<indexterm significance="normal">
 			<primary>RAID</primary>
 			<secondary>system unbootable after disk failure</secondary>
 			</indexterm>
 			<para>
-				If GRUB is installed on a RAID 1 array, the system may become unbootable in the event of disk failure. The following Red Hat Knowledgebase article describes how to make the system bootable under these cirumstances: <ulink url="http://kbase.redhat.com/faq/docs/DOC-7095">http://kbase.redhat.com/faq/docs/DOC-7095</ulink> 
+				<application>GRUB</application> cannot construct a software RAID. Therefore, the <filename>/boot</filename> directory must reside on a single, specific disk partition. The <filename>/boot</filename> directory cannot be striped across multiple disks, as in a level 0 RAID. To use a level 0 RAID on your system, place /boot on a separate partition outside the RAID.
+			</para>
+			<para>
+				Similarly, because the <filename>/boot</filename> directory must reside on a single, specific disk partition, <application>GRUB</application> cannot boot the system if the disk holding that partition fails or is removed from the system. This is true even if the disk is mirrored in a level 1 RAID. The following Red Hat Knowledgebase article describes how to make the system bootable from another disk in the mirrored set: <ulink url="http://kbase.redhat.com/faq/docs/DOC-7095">http://kbase.redhat.com/faq/docs/DOC-7095</ulink> 
+			</para>
+			<para>
+				Note that these issues apply only to RAID that is implemented in software, where the individual disks that make up the array are still visible as individual disks on the system. These issues do not apply to hardware RAID where multiple disks are represented as a single device.
 			</para>
 		</important>
 	</section>