http://bugzilla.novell.com/show_bug.cgi?id=541684 zhu rensheng changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541684 http://bugzilla.novell.com/show_bug.cgi?id=541684#c4 Olaf Zander changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Olaf.Zander@t-online.de | --- Comment #4 from Olaf Zander 2010-01-28 12:43:33 UTC --- Created an attachment (id=339354) --> (http://bugzilla.novell.com/attachment.cgi?id=339354) /var/log/YaST2 archive This should contain all the y2logs you were requesting. Just prior to this I upgraded to kernel 2.6.27.42-0.1. The result was the same: no initrd created and /boot/grub/menu.lst has no entries. The file mkinitrd.log in the YaST2 directory contains entries of the failed upgrade and then the successful manual initrd creation through calling mkinitrd -d /dev/md6. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541684 http://bugzilla.novell.com/show_bug.cgi?id=541684#c6 --- Comment #6 from Olaf Zander 2010-01-28 12:47:24 UTC --- Created an attachment (id=339361) --> (http://bugzilla.novell.com/attachment.cgi?id=339361) /boot/grub/menu.lst after failed kernel upgrade (all boot entries are removed) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541684 http://bugzilla.novell.com/show_bug.cgi?id=541684#c Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Olaf.Zander@t-online.de -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=541684 http://bugzilla.novell.com/show_bug.cgi?id=541684#c9 --- Comment #9 from Dennis Olsson 2010-04-14 15:39:09 CEST --- Created an attachment (id=354353) --> (http://bugzilla.novell.com/attachment.cgi?id=354353) Configuration file for "mkinitrd" to work-around bug in "mkinitrd", when kernel is updated. When I encounter this bug, I just create a configuration file for "mkinitrd" in "/etc/sysconfig/initrd" (see attachment), where I set the "rootdev=" and "resumedev=" to the devices actual used. The reason, why "mkinitrd" does everything wrong, is that "mkinitrd" cannot figure out what the "rootdev" and (sometimes also) what the "resumedev" should be set to. Using a "/etc/sysconfig/initrd" file enables you to work-around this bug by settings these devices and thus enabling that each time a kernel update has been performed, "mkinitrd" will also generate a working "initrd" resp. having a correct "/boot/grub/menu.lst" file. In fact, I wonder why the "mkinitrd" RPM package does not already contain a "/etc/sysconfig/initrd" file already?!??! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.