<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=ISO-8859-1" http-equiv=content-type>
<META name=GENERATOR content="MSHTML 8.00.6001.19258">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV><FONT size=2 face=Arial>Thanks Gerald for this info. By bizzare
coincodence I lost one disk from my RAID1 pair on Saturday morning
(might have been before) and have a plan to sort it on Friday (so this
email may have saved me a mass of grief). Running only the reporting
command from the email, I get this:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>[root@s6 boot]# find /boot -name 'initramfs*.img'
-print -exec lsinitrd {} \; | grep
dracut-0<BR>dracut-004-256.el6<BR>-rw-r--r-- 1
root
root 19 Dec 11
2011 dracut-004-256.el6<BR>dracut-004-256.el6<BR>-rw-r--r-- 1
root
root 19 Dec 11
2011 dracut-004-256.el6<BR>dracut-004-256.el6<BR>-rw-r--r-- 1
root
root 19 Dec 11
2011 dracut-004-256.el6</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>As this is below the -283.el6 that's marked as
fixed I'm guessing there will be a problem when I try to reboot - even with a
new disk in situ.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So, my question... is the procedure in the email
Gerald kindly forwarded both safe and recommended - or is there something else
that can be done?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Many thanks, Richard</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=gwaugh@frontstreetnetworks.com
href="mailto:gwaugh@frontstreetnetworks.com">Gerald Waugh</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=blueonyx@mail.blueonyx.it
href="mailto:blueonyx@mail.blueonyx.it">BlueOnyx General Mailing List</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, August 06, 2012 1:47
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [BlueOnyx:11107] SL6.2 no boot
from degraded RAID1... with fix...BTW 6.3 is OK</DIV>
<DIV><BR></DIV><PRE wrap=""><B>I M P O R T A N T ! ! !
Note: copied from Scientific Linux list</B> Konstantin Olchanski <A class=moz-txt-link-rfc2396E href="mailto:olchansk@triumf.ca>"><olchansk@triumf.ca></A>
"======================================
FYI, as a regression from SL6.0 and SL6.1, SL6.2 does not boot from degraded RAID1 devices.
If your "/" is on a RAID1 mirrored across 2 disks and <B>1 of the 2 disks dies,</B> <B>your system will
not boot</B> because dracut does not activate the required md devices.
This is a very serious problem because RAID1 (mirroring) of "/" and "swap" is a popular
solution for protecting against single-disk failures. The present bug defeats this protection
and makes the situation worse because failure of either of the 2 disks makes your system
unbootable.
It is astonishing that this problem was not caught by anybody's QA, did not receive
wide publicity <B class=moz-txt-star><SPAN class=moz-txt-tag>*</SPAN>and<SPAN class=moz-txt-tag>*</SPAN></B> the solution was not pushed into the current release of SL.
Bug report against dracut was filed in January:
<A class=moz-txt-link-freetext href="https://bugzilla.redhat.com/show_bug.cgi?id=772926">https://bugzilla.redhat.com/show_bug.cgi?id=772926</A>
marked as duplicate of secret bug:
<A class=moz-txt-link-freetext href="https://bugzilla.redhat.com/show_bug.cgi?id=761584">https://bugzilla.redhat.com/show_bug.cgi?id=761584</A>
solution made available in July for (the best I can tell) the 6.3 release:
<A class=moz-txt-link-freetext href="http://rhn.redhat.com/errata/RHBA-2012-0839.html">http://rhn.redhat.com/errata/RHBA-2012-0839.html</A> (dracut-004-283.el6.src.rpm)
<A class=moz-txt-link-freetext href="http://rhn.redhat.com/errata/RHBA-2012-1078.html">http://rhn.redhat.com/errata/RHBA-2012-1078.html</A> (dracut-004-284.el6_3.src.rpm)
These RPMs are available in SL6 .../6rolling/x86_64/updates/fastbugs/
I confirm that dracut-004-284.el6_3 can boot SL6.2 from degraded "/" (one disk missing).
Note that applying the fix on affected systems is not trivial:
1) rpm -vh --upgrade dracut-004-284.el6_3.noarch.rpm dracut-kernel-004-284.el6_3.noarch.rpm
2) bad dracut is still present inside the /boot/initramfs files, your system is still broken
3) dracut -v -f ### this rebuilds the initramfs for the ***presently running*** kernel, not necessarily the one used for the next reboot
4) find /boot -name 'initramfs*.img' -print -exec lsinitrd {} \; | grep dracut-0 ### report dracut version inside all /boot/initramfs files
5) dracut -v -f /boot/initramfs-2.6.32-279.1.1.el6.x86_64.img 2.6.32-279.1.1.el6.x86_64 ### rebuild initramfs for the latest update kernel
"=======================================
Is fixed is SL6-3
Looks like CentOS with its 6,3 version is OK
</PRE><PRE class=moz-signature cols="72"></PRE>
<P>
<HR>
<P></P>_______________________________________________<BR>Blueonyx mailing
list<BR>Blueonyx@mail.blueonyx.it<BR>http://mail.blueonyx.it/mailman/listinfo/blueonyx<BR></BLOCKQUOTE></BODY></HTML>