Bug 789085

Summary: md: personality for level 10 is not loaded
Product: [Fedora] Fedora Reporter: Clyde E. Kunkel <clydekunkel7734>
Component: dracutAssignee: dracut-maint
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: dracut-maint, harald, jonathan, v
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-10 20:25:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
RDSOS Report none

Description Clyde E. Kunkel 2012-02-09 18:20:32 UTC 
Description of problem:
during dracut time, the raid 10 PV for the root dir LV is not started and thus dracut drops to a shell after issuing msg that personality for level 10 is not loaded

Version-Release number of selected component (if applicable):
dracut-015-3.git20120208.fc18.noarch

How reproducible:
every time, even after recreating the initramfs with:
# dracut -v -f -a mdraid --add-drivers raid10 /boot/initramfs-3.3.0-0.rc2.git6.1.fc18.x86_64.img 3.3.0-0.rc2.git6.1.fc18.x86_64


Steps to Reproduce:
1. boot system
2.
3.
  
Actual results:
drops to a shell after msg: md: Personality for level 10 is not loaded and root file system cannot be found

Expected results:
normal startup

Additional info:

While in the shell, the raid 10 device can be seen with mdadm --detail /dev/md127.  It shows a proper device, but inactive.  trying mdmadm --run leads to a repeat of the personality msg.
Comment 1 Clyde E. Kunkel 2012-02-10 20:25:33 UTC 
Appears fixed with dracut-015-7.git20120209.fc18.noarch.  closing
Comment 2 Harald Hoyer 2012-02-13 10:11:17 UTC 
the fix was most likely kmod-5-6
Comment 3 Clyde E. Kunkel 2012-02-13 13:47:46 UTC 
(In reply to comment #2)
> the fix was most likely kmod-5-6

Yes, I agree.  I see it was in the same rawhide report....
Comment 4 Vasco Rodrigues 2015-09-24 00:39:04 UTC 
Just got this on my raid5, it gives the same error.
Comment 5 Vasco Rodrigues 2015-09-24 00:39:44 UTC 
Created attachment 1076322 [details]
RDSOS Report
Comment 6 Vasco Rodrigues 2015-09-24 01:07:54 UTC 
Fixed it with a chroot from a livecd and

dracut -v -f -a "lvm mdraid" --add-drivers raid456 -kver 4.1.6-201.fc22.x86_64

Problem came from moving PV on LVM, where the root filesystem LV was on a non-raid, them moved to a PV on raid. Must edit the rules for dracut, when moving rootfs in this situation.