Description of problem: mkinitrd does not support systems where the root filesystem is on a raid10 array when used without arguments in a normal kernel upgrade Version-Release number of selected component (if applicable): mkinitrd-4.2.15-1 How reproducible: Set up a system with a raid10 root filesystem and try it. However. that is a lot effort given the simplicity of the patch Actual results: Creates an initrd with no raid10.ko module and with the related steps in init missing. Expected results: Should include the module in initrd /lib/, then include lines in init to insmod the module and raidautorun the md device Additional info: The following patch fixes the bug: --- mkinitrd 2006-01-21 11:28:42.000000000 +0000 +++ mkinitrd.new 2006-01-21 11:30:47.000000000 +0000 @@ -450,7 +450,7 @@ findmodule multipath startraid=1 ;; - raid[01456]) + raid[01456] | raid10) findmodule $level startraid=1 ;; However, the whole case statement causing the problem could simply be removed. Why try checking the contents of /proc/mdstat? Are you worried that it might be wrong? God help us if it is!
Created attachment 123525 [details] Patch given in text
More worried that something will be added that we can't handle and wanting to fail somewhat gracefully. Thanks for the patch, it'll be in the next build I do (5.0.22-1, probably sometime next week).