[Bug 532551] New: Kernel updates break GRUB parameters preventing reboot
http://bugzilla.novell.com/show_bug.cgi?id=532551 Summary: Kernel updates break GRUB parameters preventing reboot Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: anilm2@yahoo.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13 This is a continuing and serious issue that prevents systems from rebooting (this is a critical issue for remote systems). It revolves around a non-standard system configuration. My Linux system is located on my 2nd harddrive. When YaST2 updates my kernel it follows that up by re-writing my GRUB boot parameters in the /boot/grub/menu.lst file. My Linux partition is on (hd1,1). However, YaST2 re-writes ALL of GRUB's linux boot menu options with (hd0,0). If I fail to manually update the menu.lst file myself after a kernel update, i can not reboot my system with any Linux menu option. The system will simply fail to find the kernel, since it is looking in the wrong place. Only recovery for this is to enter rescue mode and fix the file... I know to do that now, but the 1st time I did this it was very hard to identify the error (especially since the machine it happened on was in another state, and I had to drive there to get on the console and fix it). Reproducible: Always Steps to Reproduce: 1. update to newest kernel via YaST2's online update 2. allow YaST2 to complete and exit normally. 3. reboot the system Actual Results: system fails to reboot. optionally (and simpler) would be to just look at the /boot/grub/menu.lst file and see all the linux kernel's being identified on (hd0,0) instead of (hd1.1). Expected Results: menu.lst file should maintain the proper linux partition information for reaching the linux kernel. System should reboot without need for 'rescue'. This is a critical failure on a remote server. The system will not recover from any type of reboot/power failure/etc and needs skilled manual intervention to recover. -- 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=532551 shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |jsrain@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.
http://bugzilla.novell.com/show_bug.cgi?id=532551 User jsrain@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=532551#c1 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |anilm2@yahoo.com --- Comment #1 from Jiri Srain <jsrain@novell.com> 2009-09-02 23:57:50 MDT --- Are you sure your device map is correct? Can you attach YaST logs from installation, as well as all bootloader configuration files (/etc/grub.conf, /boot/grub/menu.lst, /boot/grub/device.map) and /etc/fstab? -- 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=532551 User jsrain@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=532551#c2 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|anilm2@yahoo.com | Resolution| |NORESPONSE --- Comment #2 from Jiri Srain <jsrain@novell.com> 2009-10-08 02:38:40 MDT --- No information provided, closing. If you can provide requested information (previous comment), please, reopen. -- 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.
participants (1)
-
bugzilla_noreply@novell.com