en-US/Grub.xml | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
New commits:
commit 14dc50f627151da3f38a5d7ef0bf91fcab1b83c6
Author: Ruediger Landmann <r.landmann(a)redhat.com>
Date: Mon Jan 11 10:05:45 2010 +1000
Link to Red Hat Knowledgebase article on RAID 1 failures BZ#553510
diff --git a/en-US/Grub.xml b/en-US/Grub.xml
index e016003..5646923 100644
--- a/en-US/Grub.xml
+++ b/en-US/Grub.xml
@@ -321,16 +321,8 @@
<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. <!-- DEAD LINK An unsupported workaround is provided online at the
following URL:
- </para>
-
- <para>
- <ulink
url="http://www.dur.ac.uk/a.d.stribblehill/mirrored_grub.html">http://www.dur.ac.uk/a.d.stribblehill/mirrored_grub.html</ulink>
-->
- </para>
<para>
- Installing GRUB on each disk in the array might ensure that your system can boot from
any of the disks individually if the array itself is inaccessible. Refer to <ulink
url="http://tldp.org/HOWTO/Software-RAID-HOWTO-7.html#ss7.3">...
for an explanation and example of this strategy.
+ 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...
</para>
</important>
</section>