https://bugzilla.novell.com/show_bug.cgi?id=408724 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c1 --- Comment #1 from Christian Boltz 2008-07-13 08:26:48 MDT --- Created an attachment (id=227467) --> (https://bugzilla.novell.com/attachment.cgi?id=227467) y2logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c3 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com Status|NEW |NEEDINFO Info Provider| |suse-beta@cboltz.de --- Comment #3 from Marcus Meissner 2008-07-13 13:38:35 MDT --- curious. what is "uname -a" output? perhaps the old kernel is still running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c5 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |suse-beta@cboltz.de --- Comment #5 from Cyril Hrubis 2008-07-17 02:21:58 MDT --- That's the question because uname is often used to determine path to modules, so it's important which kernel version it prints. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c7 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chrubis@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com --- Comment #7 from Cyril Hrubis 2008-07-18 03:01:28 MDT --- Okay looks like uname gets this info from uname system call, so this is most likely kernel compilation bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c9 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|suse-beta@cboltz.de | --- Comment #9 from Christian Boltz 2008-07-23 12:57:58 MDT --- Created an attachment (id=229594) --> (https://bugzilla.novell.com/attachment.cgi?id=229594) menu.lst -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c11 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #229594|0 |1 is obsolete| | --- Comment #11 from Christian Boltz 2008-07-31 15:00:00 MDT --- Created an attachment (id=231139) --> (https://bugzilla.novell.com/attachment.cgi?id=231139) lilo.conf Argghhh :-( Now that you mention it: the system uses lilo as bootloader because grub did not really work. I forgot this detail since it is not my machine :-( Here's the lilo.conf it uses, and it even contains image = /boot/vmlinuz-2.6.18.8-0.10-default ###Don't change this comment - YaST2 identifier: Original name: linux### label = LinuxV2 append = "resume=/dev/sda1 splash=silent showopts" initrd = /boot/initrd-2.6.18.8-0.10-default root = /dev/md0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c12 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |suse-beta@cboltz.de --- Comment #12 from Marcus Meissner 2008-07-31 15:03:15 MDT --- hmm. what type of RAID is md0? /proc/mdstat ? - lilo might not have been run - lilo might not have written the blockmap correctly -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c14 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|suse-beta@cboltz.de | --- Comment #14 from Christian Boltz 2008-08-14 14:02:25 MDT --- # cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [linear] md1 : active raid1 hda3[0] hdb3[1] 66637504 blocks [2/2] [UU] md0 : active raid1 hda2[0] hdb2[1] 10490368 blocks [2/2] [UU] unused devices: <none> -> looks OK If you need more information regarding lilo (see comment #12 and #13), please give me some hints how to obtain the requested information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c16 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|suse-beta@cboltz.de | --- Comment #16 from Christian Boltz 2008-09-23 14:59:47 MDT --- (In reply to comment #15 from Jeff Mahoney)

Yeah, the problem here is definitely that the old kernel is still being booted. The file is deleted, but it's still accessible. Or, well, it will be until the file system sees more activity. .. Running lilo again is really the best option here.

Seems your guess was right. # lilo Added LinuxV2 * Added FailsafeV1 Fatal: open /boot/initrd-2.6.18.8-0.7-default: No such file or directory (lilo.conf is attached to this bugreport already) After updating the version to ...0.10-default lilo could be installed successfully. And after a reboot uname -a even reports the correct kernel version :-) This means the kernel itself is OK and this bug is a candidate for the "most weird problem of the year" award ;-) The only remaining question is: Why was the version number not updated in all lilo.conf sections? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c18 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aosthof@novell.com |jreidinger@novell.com --- Comment #18 from Alexander Osthof 2008-09-24 00:36:58 MDT --- If it's a perl-Bootloader problem, I'm not the right assignee anymore. Josef Reidinger is now the new maintainer. Reassigning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c19 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |suse-beta@cboltz.de --- Comment #19 from Josef Reidinger 2008-09-26 04:37:19 MDT --- I find that initrd-2.6.18.8-0.7-default is in lilo.conf before kernel upgrade! So how this entry get there? do you manually add it? from logs I see that upgrade from 2.6.18.8-0.9 to 2.6.18.8-0.10 run correct (old remove new added). Problem with boot is that lilo fail when writing boot sector so it doesn't update initrd in boot sector so during boot it finding old initrd. So at first I must fix that failed lilo must not be silent (ideal is fail whole kernel upgrade, because without old initrd you have problems with booting). Second is find why 2.6.18.8-0.7-default entry is in lilo.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408724 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408724#c21 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #21 from Josef Reidinger 2008-09-26 05:46:32 MDT --- ok, in beta1 11.1 kernel install fail if fail updating bootloader configuration. (this is fixed maybe in 11.0, I am not sure when this fix was added). OK, so I close this bug, because if you manually add or copy non-existing initrd then lilo fail is expected until you fix it. If you want correct booting, then remove this entry and run lilo as root. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.