There is an error in the mkinitrd script which causes it to try and explicitly activate the subsets of a (nested) raid 10 set, causing error messaged during boot like these ones: https://bugzilla.redhat.com/attachment.cgi?id=354680 These errors are ugly, but otherwise 100% harmless. This patch fixes these error messages: https://bugzilla.redhat.com/attachment.cgi?id=355550
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
As I filed this I guess I should take care of it. Note, in case you beat me to fixing this, the proposed patch: https://bugzilla.redhat.com/attachment.cgi?id=355550 Has 2 issues: 1) dmraid should be invoked with -i 2) The output of dmraid should be checked to not be "no dmraid disks"
This is fixed in mkinitrd-5.1.19.6-55 .
Hans, any hints how we can test this?
Hi, (In reply to comment #6) > Hans, > any hints how we can test this? Take a machine with Intel BIOS RAID, put 4 disks in it, make it a RAID10 set in the Intel OROM, install 5.4, boot, watch ugly error messages. Install 5.5, boot again, error messages are gone. Note that I have such a machine and have already gone through the above motions, iow the fix actually fixing things was already verified by me. Regards, Hans
OK, moving to VERIFIED then. RTT doesn't have easy access to systems with Intel BIOS RAID anyway.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0295.html