Bugzilla – Bug 299614
/boot/grub/menu.lst loses entries on update
Last modified: 2007-09-14 11:15:15 UTC
When updating from FACTORY as of mid last week (2008-08-07 or so) to today's version (2008-08-11) via "yast sw_single" and "Update package if newer version available" an entry I had manually added there to boot a copy of 10.2 on the same machine simply got lost. The entry looked like title openSUSE 10.2 - 2.6.18.8-0.5 root (hd0,1) kernel /boot/vmlinuz-2.6.18.8-0.5-default root=/dev/hda2 vga=0x317 resume=/dev/hda1 splash=silent showopts initrd /boot/initrd-2.6.18.8-0.5-default at the end of /boot/grup/menu.lst and I believe it did not have one of those lines starting with "###" above it. (YaST logs did not provide anything useful when grepping for "grub" or "kernel". Probably some post-install scripts?)
Not all entries will be deleted, as an example: In my case i had five entries in my old menu.lst, one for openSUSE, debian, Windows, Failsafe openSUSE and memtest86 . After Update from openSUSE Alpha 7 to Beta 1 via YaST Factory Update i had also five entries, but two for openSUSE (default and big-smp) and two for Failsafe openSUSE (default and big-smp) and still one for Windows. The entries for debian and memtest86 were erased completely (not only commented out). And like the original poster states: no entry with "grub" or "menu.lst" in any log within /var/log/YaST2.
Can you please add the yast2-logs?
Created attachment 157023 [details] This should contain the logs from the relevant point int time (for my system)
Created attachment 157024 [details] ...but for the sake of completness I'm also attaching later logs Jens, please also provide your logs in addition nevertheless!
Created attachment 157025 [details] YaST2-log After the above described update i tried several times to configure a wireless network chip, so maybe there is some useless info in these logs for this special bug.
Created attachment 157026 [details] second logfile from /var/log/YaST2
Created attachment 157027 [details] third and last logfile from /var/log/YaST2
Hmm - there should be a /var/log/YaST2/perl-BL-standalone-log logfile, if the update >= Beta1, if not booted off of CD. This is the one I need, as this is done by perl-Bootloader, not YaST
Created attachment 157036 [details] /var/log/YaST2/perl-BL-standalone-log I guess this explains why haven't seen anything in the regular YaST log files. ;-) One question: the regular log files are rw-r--r-- while this one is just rw-------. How about making it rw-r--r-- as well? Or is there sensitive data here? In that case rather not...
This logfile only shows an update from 2.6.22.1-14 -> 2.6.22.1.16 At this stage, there is no 10.2 entry anymore. Assigning to perl-Bootloader maintainer
Created attachment 157051 [details] config_diff_2007_08_11.log Sorry, i suppressed two logfiles, coz i thought (and i'm still doing so) that they havent any interesting info regarding this bug. But you have the knowledge and i dont want to be a brake, so here comes two more logfiles from /var/log/YaST2 and thats really the whole content of this drectory. regards, Jens
Created attachment 157052 [details] inst_rpmcopy_post.sh.log
*** This bug has been marked as a duplicate of bug 309837 ***