[Bug 511319] New: kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting!

newer
[Bug 559619] New: pm-hibernate:...

older
[Bug 546086] VUL-0: Unbound DNSSEC...

bugzilla_noreply＠novell.com

9 Jun 2009 9 Jun '09

15:44

http://bugzilla.novell.com/show_bug.cgi?id=511319 Summary: kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting! Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-1.1.1 Firefox/3.0.10 The latest kernel update (from 2.6.27.21 to 2.6.27.23) hosed by grub config (menu.lst). Specifically, here are (a subset) of the changes: -title openSUSE 11.1 - 2.6.27.21-0.1 +title openSUSE 11.1 - 2.6.27.23-0.1 root (hd0,2) - kernel /vmlinuz-2.6.27.21-0.1-default root=/dev/system/root splash=silent showopts elevator=as luks_lukspv=/dev/sda4 - initrd /initrd-2.6.27.21-0.1-default + kernel /vmlinuz-2.6.27.23-0.1-default root=/dev/system/root resume=/dev/sda2 splash=silent showopts elevator=as + initrd /initrd-2.6.27.23-0.1-default 1. Why was a 'resume' parameter added? I removed that on purpose! 2. Why was the luks_lukspv param removed? That's a critical parameter for me to boot with encrypted root support! I spent 2 hours trying to find out what went wrong here. kernel updates should **not** spuriously add or remove kernel command line options. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.

Show replies by date

bugzilla_noreply＠novell.com

10 Jun 10 Jun

09:54

New subject: [Bug 511319] kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting!

http://bugzilla.novell.com/show_bug.cgi?id=511319 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com AssignedTo|bnc-team-screening@forge.pr |jreidinger@novell.com |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.

bugzilla_noreply＠novell.com

17:10

New subject: [Bug 511319] kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting!

http://bugzilla.novell.com/show_bug.cgi?id=511319 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=511319#c1 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Josef Reidinger 2009-06-10 11:10:49 MDT --- Hi, In 11.1 is added new default kernel parameters which is configured by yast to avoid some problems with update, so now is used kernel parameters from /etc/sysconfig/bootloader if parameters there doens't match newly added one please reopen with y2logs or if you add luks parameter with yast and sysconfig is not properly updated. -- 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.

bugzilla_noreply＠novell.com

17:48

New subject: [Bug 511319] kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting!

http://bugzilla.novell.com/show_bug.cgi?id=511319 User jnelson-suse@jamponi.net added comment http://bugzilla.novell.com/show_bug.cgi?id=511319#c2 --- Comment #2 from Jon Nelson 2009-06-10 11:48:48 MDT --- Then I contend that there *really* needs to be a big fat warning in /boot/grub/menu.lst which states something like: # THIS FILE WILL BE OVERWRITTEN by YaST # Configure custom boot parameters in /etc/sysconfig/bootloader # I guess I don't understand why it needed to do that. Why do boot params need to be stored in sysconfig? It doesn't touch other entries in the file. sigh. -- 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.

bugzilla_noreply＠novell.com

11 Jun 11 Jun

09:56

New subject: [Bug 511319] kernel 2.6.27.23 update hosed by grub config, preventing my encrypted partitions from booting!

http://bugzilla.novell.com/show_bug.cgi?id=511319 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=511319#c3 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|RESOLVED |REOPENED Resolution|INVALID | Severity|Major |Enhancement --- Comment #3 from Josef Reidinger 2009-06-11 03:56:03 MDT --- Good idea add this warning to configuration file. But text is not correct, it doesn't overwrite file, only remove old kernel when you uninstall it and install new one with default parameters from sysconfig. Reason why boot parameters is stored in sysconfig is two. First is easy decision what use if user has more boot entries with different kernel parameters. Second is that in some case is old kernel uninstalled before installing new one and then nothing store old boot parameters. -- 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.