Bug 1085922
| Summary: | Unable to boot system with root on rmd raid1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan ONDREJ <ondrejj> |
| Component: | dracut | Assignee: | dracut-maint-list |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | awilliam, dracut-maint-list, gansalmon, harald, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, nicolas.moulonguet |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-17 18:18:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Let's start with dracut. It should have started mdadm. Confirming dracut bug. This helped me to solve my problem: yum downgrade dracut\* -y dracut /boot/initramfs-3.13.9-200.fc20.i686+PAE.img 3.13.9-200.fc20.i686+PAE -f Trying to diff working/non-working initramfs, but too many changes in dracut files. Latest working version: dracut-034-64.git20131205.fc20.i686 Wrong: dracut-037-10.git20140402.fc20.i686 Same problem here with Fedora 20 on RAID/LVM. Unable to boot automatically. Sounds as a problem with RAID (mirroring in my case). Same on 3 Fedora 20 mirrored servers. Works with old kernel : 3.13.7-200.fc20.i686 Do not work with new ones : 3.13.8-200.fc20.i686 3.13.9-200.fc20.i686 On 3.13.9-200.fc20.i686 systems hangs after : .... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. then after a few long minuts drops in dracut shell. In journalctl can see the line : dracut-cmdline[80]: dracut-20 (Heisenbug) dracut-037-10.git20140402.fc20 ... dracut-cmdline[80]:warn "Cancelling resume operation. Device not found."; ... dracut-pre-trigger[225]: rd.md=0: removing MD RAID activation ... ...strange because dracut-037-10 has been precedently removed with yum ...package exists in kernel ? From second line it seems system does not want raid If i assemble raid manually doing : mdadm --assemble /dev/md0 mdadm --assemble /dev/md1 mdadm --assemble /dev/md2 mdadm --assemble /dev/md3 exit exit boot goes on until success ! Same workaraound with 3.13.8-200.fc20.i686 Second line seems to be generated in dracut shell by parse-md.sh humhum... correction System works again effectively with dracut-034-64.git20131205.fc20.i686 and after regenerating initramfs with it No problem to take back dracut yum downgrade dracut parse-md.sh between the two versions dracut-034-64 and dracut-037-10 is the same, so fix is to be searched elsewhere than in parse-md.sh. Installing dracut-037-10.git20140402.fc20.i686 then dracut-037-10.git20140402.fc20.i686 installed In dracut/modules.d/90mdraid/module-setup.sh , commenting in install() procedure test lines as bellow: #if [[ $hostonly_cmdline == "yes" ]] ;then cmdline >> ............... echo >> .................. #fi makes the boot OK after generating a new initramfs with dracut In my case these are the faulty lines 037-10.git20140402.fc20 hangs on mirrored/lvm root disk https://bugzilla.redhat.com/show_bug.cgi?id=1084766 see: https://bugzilla.redhat.com/show_bug.cgi?id=1084766 please check, that your kernel command line contains all needed information. Install new dracut: # dracut --print-cmdline (In reply to Harald Hoyer from comment #7) > see: https://bugzilla.redhat.com/show_bug.cgi?id=1084766 > > please check, that your kernel command line contains all needed information. > > Install new dracut: > # dracut --print-cmdline When i run : dracut --print-cmdline <paquet iniramfs> <version> no initramfs is generated Is that what you say ? eileon: no, it doesn't generate an initramfs, just run "dracut --print-cmdline" and it should display some cmdline options dracut thinks you need to have set in your bootloader config. If they're not in there, that is the problem. See #1084766 for more details. *** This bug has been marked as a duplicate of bug 1084766 *** (In reply to Adam Williamson from comment #9) > eileon: no, it doesn't generate an initramfs, just run "dracut > --print-cmdline" and it should display some cmdline options dracut thinks > you need to have set in your bootloader config. If they're not in there, > that is the problem. > > See #1084766 for more details. > > *** This bug has been marked as a duplicate of bug 1084766 *** That's OK ! dracut --print-cmdline gives parameters to be set in /etc/default/grub (GRUB_CMDLINE_LINUX) Making a new grub.cfg file with grub2-mkconfig -o grub.cfg then reboot is straight fine. |
Description of problem: After update to latest kernel 3 my computers don't boot. All of them has system mirrored on 2 disks. /boot is a part of / and / is an raid1 device. Other systems without RAID boots ok. Version-Release number of selected component (if applicable): kernel-3.13.9-200.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. reboot latest kernel Actual results: ... Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ 307.919961] dracut-initqueue[218]: Warning: Could not boot. [ 307.930481] dracut-initqueue[218]: Warning: /dev/disk/by-uuid/032f2472-a64c-418c-8ab2-ed180ea1216b does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-uuid/032f2472-a64c-418c-8ab2-ed180ea1216b does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Expected results: normal boot Additional info: Unable to reproduce with older kernels, like kernel-3.13.8-200.fc20.x86_64 and before. I can attach rdsosreport.txt, if required. After running mdadm -A --scan, required /dev/disk... is available. Is this a dracut bug or a kernel bug?