[Bug 290959] New: Update for kernel 2.6.18.8-0.3 to -0.5, system does not boot
https://bugzilla.novell.com/show_bug.cgi?id=290959 Summary: Update for kernel 2.6.18.8-0.3 to -0.5, system does not boot Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rmatov101@charter.net QAContact: qa@suse.de Found By: Other After update from 2.6.18.8-0.3 to 2.6.18.8-0.5 system can't boot in default configuration. ********************************** lin: # cat /boot/grub/menu.lst ********************************** # Modified by YaST2. Last modification on Mon Jul 9 19:23:17 CDT 2007 default 2 timeout 30 gfxmenu (hd0,5)/boot/message title openSUSE 10.2 - 2.6.18.8-0.5 root (hd0,5) kernel /boot/vmlinuz-2.6.18.8-0.5-default root=/dev/hda6 vga=0x317 noresume splash=silent showopts initrd /boot/initrd-2.6.18.8-0.5-default title Failsafe -- openSUSE 10.2 - 2.6.18.8-0.5 root (hd0,5) kernel /boot/vmlinuz-2.6.18.8-0.5-default root=/dev/hda6 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off initrd /boot/initrd-2.6.18.8-0.5-default title openSUSE 10.2 root (hd0,5) kernel /boot/vmlinuz root=/dev/hda6 vga=0x317 noresume splash=silent showopts initrd /boot/initrd-2.6.18.8-0.3-default .... etc ********************************** Which is incorrect: vmlinuz points to vmlinuz-2.6.18.8-0.5-default initrd-2.6.18.8-0.3-default, nor initrd-2.6.18.8-0.3-default.old do not exist ********************************** lin:~> ls -w1 /boot ********************************** backup_mbr boot config-2.6.18.8-0.5-default grub initrd initrd-2.6.18.8-0.5-default message symsets-2.6.18.8-0.5-default.tar.gz symtypes-2.6.18.8-0.5-default.gz symvers-2.6.18.8-0.5-default.gz System.map-2.6.18.8-0.3-default.old System.map-2.6.18.8-0.5-default vmlinux-2.6.18.8-0.5-default.gz vmlinuz vmlinuz-2.6.18.8-0.3-default.old vmlinuz-2.6.18.8-0.5-default ********************************** It is missing: initrd-2.6.18.8-0.3-default.old and config-2.6.18.8-0.3-default.old. Further patch postinstall script removed all default entries from /lib/modules/2.6.18.8-0.3-default/ except entries in extra subdirectory, 2 scsi and 2 sound that doesn't belong to default kernel in kernel subdirectory. Even if entries in menu.lst would be correct system still would not boot without modules for 2.6.18.8-0.3-default. It is good that extra modules are not removed as well, although they are useless in wrong directory and before recompilation with new kernel, but at least they are here as reminder. This makes "openSUSE 10.2" boot option useless and bad is that it is set to be default. New entry "openSUSE 10.2 - 2.6.18.8-0.5" boots fine, even Linuxant modem driver is recompiled on boot. -- 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=290959#c1 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #1 from Marcus Meissner <meissner@novell.com> 2007-07-10 23:30:41 MST --- left overs from bootloader problems. entry 3 has a wrong initrd line at least. and default should be 0 perhaps. -- 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=290959#c2 --- Comment #2 from Rajko Matovic <rmatov101@charter.net> 2007-07-11 18:04:55 MST --- I agree about default, the old kernel should be fallback option, not main one. BTW, i386 update went fine, but on that machine /boot directory is on different partition. The old kernel, modules and sources are deleted. Which would be a problem if old .config would not be in a shadow directory far from updater ;-) -- 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=290959 Matej Horvath <mhorvath@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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=290959#c3 Rajko Matovic <rmatov101@charter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #3 from Rajko Matovic <rmatov101@charter.net> 2007-09-02 11:08:05 MST --- I can't see problems in scripts delivered with current kernel rpm. I will close it now as worksforme. -- 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=290959#c4 --- Comment #4 from Richard Creighton <rccj@ricreig.com> 2007-09-02 13:05:16 MST --- I suggest the reason it 'works for you' has more to do with your equipment than the script. I believe the change from calling IDE drives HDn to SDn has caused many unanticipated side effects including this one. This bug will bite anyone that has a mixed hardware architecture, ie, 1 or more IDE drives and 1 or more SATA drives upon which the 10.3 upgrade is being installed. Because of the rename between versions, the script will write the changed files to the new SDAn drive which is the old physical HDAn device whih causes the failure. Unless you have a mixed hardware architecture when you test and unless you have the 10.3 on a SATA drive and the SATA is renamed by the kernel version upgrade, you will not experience the privilege of seeing the bug in action so of course, it will 'work for you'. I don't know who thought of renaming HDn to SDn in mixed architecture hardware systems, but it was ill conceived and has caused me and undoubtedly many thousands of others many headaches. When Novell upgrades from 10.2 and earlier to it's customers that have both IDE and SATA hardware, expect big problems unless you take the time to evalulate this renaming scheme a little more fully. Now is the time to take this bug and see it for what it really is and not dismiss it so casually as 'works for me'. Give it to someone that has the proper hardware to be affected by it and let them troubeshoot it. I assure you it is real. This bug has been reported in several dozen different forms in bugzilla and the root cause is the same in each case. I want SuSE and Novell to suceed which is why I am a beta tester and volunteer my equipment and time for free. I risk damage to my equipment knowing that beta software can damage it. I accept that. What I can't accept is 'works for me' without examining the root cause of reported failures. Now that I hope you understand that there is a root cause beyond the symptom of 'won't boot after upgrade', dig into it more deeply, but don't write it off. That makes your free beta testers feel worthless and ultimately dooms Novell to failure and with that failure, your job is moot as well. I hope you can see that. I know you are busy and probably under a lot of pressure with a large workload, but this one is very important, don't let it go so casually. -- 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=290959#c5 --- Comment #5 from Rajko Matovic <rmatov101@charter.net> 2007-09-02 16:32:48 MST --- Richard, this bug happend to be reported by me. It is not dismissed without reason. It was bug in scripts running after kernel installation and if it would be present I would see it again. Since this report I installed kernel few times and I found another bug, but not this one. I didn't fixed the bug, so I can't say it is fixed, but I can say it works for me and I'm pretty sure it will work for everybody. If anyone find same problem, bug can be reopened, so nothing horrible happened with one bug lesser on radar. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com