Description of problem: I just upgraded my workstation from F16 to F17 using the following yum howto: http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_16_-.3E_Fedora_17 Everything went well until the final reboot. There was no initramfs generated for the newly installed kernel 3.4.4-5. I started the system using the previous kernel/initramfs pair (3.3.8-1) and tried to generate the initramfs for 3.4.4-5 manually, but the result initramfs doesn't work. It's dropping me to the debug shell. It seems my md-raid array is not assembled well. I guess you would need more info. Please, ask what info could help you to identify the issue. Version-Release number of selected component (if applicable): dracut-018-78.git20120622.fc17 How reproducible: always
sorry ... ask -> tell me
Created attachment 597644 [details] screenshot ... sorry for the low quality
Created attachment 597645 [details] lsinitrd 3.3.8-1
Created attachment 597647 [details] lsinitrd 3.4.4-5
there are no modules in the 3.4.4-5 initrd. I would guess depmod was not run or you have a broken kmod. please run: # yum update kmod # depmod -ae -F /boot/System.map-3.4.4-5.fc17.x86_64 3.4.4-5.fc17.x86_64 \ && echo OK # dracut --force '' 3.4.4-5.fc17.x86_64 and check that the kernel modules are in the initramfs. # lsinitrd /boot/initramfs-3.4.4-5.fc17.x86_64.img | grep lib/modules
Hello Harald. Thanks, that helped. I don't know if it's a good idea to switch the component and search for the root cause or if we should rather update the F16->F17 update section on the Wiki ... What do you think? Regards, Jaromir.
(In reply to comment #6) > Hello Harald. > > Thanks, that helped. > I don't know if it's a good idea to switch the component and search for the > root cause or if we should rather update the F16->F17 update section on the > Wiki ... > > What do you think? > > Regards, > Jaromir. Well, in theory the "yum update" in the wiki should have pulled in the updated kmod. And in theory "depmod" should have been run by grubby's new-kernel-pkg after the whole yum update transaction. But the devil is in the details. What you can do, is to add a note to the wiki describing on how to check, that depmod was run properly and what to do if not.