[Bug 463450] New: 6 grub entries after kernel install
https://bugzilla.novell.com/show_bug.cgi?id=463450 Summary: 6 grub entries after kernel install Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- after updating from 11.0 to 11.1 I found 6 kernel entries in grub menu.lst: three identical entries with "Original name: linux" and three with "Original name: failsafe". later I installed the kernel-default and I got 6 more entries -- 3 for linux-default and 3 for failsafe-default. I can reproduce this by running (after deleting the pae kernel packages) kernel-pae-2.6.27.7-9.1.i586.rpm kernel-pae-base-2.6.27.7-9.1.i586.rpm kernel-pae-extra-2.6.27.7-9.1.i586.rpm after every single rpm being installed I see mkinitrd being run and finally I got again 6 pae entries in grub :-( -- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c1 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@novell.com Status|NEW |NEEDINFO Info Provider| |koenig@linux.de --- Comment #1 from Josef Reidinger <jreidinger@novell.com> 2009-01-05 01:29:19 MST --- This looks like problem with detection disks (it think, that previous entries is on another disk). Please attach yast logs http://en.opensuse.org/Bugs/YaST -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c2 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|koenig@linux.de | --- Comment #2 from Harald Koenig <koenig@linux.de> 2009-01-05 02:06:04 MST --- Created an attachment (id=263155) --> (https://bugzilla.novell.com/attachment.cgi?id=263155) y2log please note that the following two rpm commands will create the 6 grub entries too (sorry for the cut'n'paste typo in the original report), no yast involved in this case: rpm -e kernel-pae kernel-pae-base kernel-pae-extra rpm -i kernel-pae-2.6.27.7-9.1.i586.rpm kernel-pae-base-2.6.27.7-9.1.i586.rpm kernel-pae-extra-2.6.27.7-9.1.i586.rpm -- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c3 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Josef Reidinger <jreidinger@novell.com> 2009-01-05 02:13:58 MST --- Thanks for logs. yes, it also runs perl-Bootloader, which stores logs to yast dir. (it runs in rpm post script). Only way to avoid it is direct copy via cpio. -- 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=463450 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jreidinger@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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c4 --- Comment #4 from Harald Koenig <koenig@linux.de> 2009-01-05 02:49:07 MST --- (In reply to comment #3 from Josef Reidinger)
Thanks for logs. yes, it also runs perl-Bootloader, which stores logs to yast dir. (it runs in rpm post script).
do you need perl-BL-standalone-log ?
Only way to avoid it is direct copy via cpio.
not really an option because rpm database will be wrong, no updates...! you should check for identical entries in menu.lst and not create a 2nd identical copy (or find some other fix)... right now the grub menu looks pretty poor and might distrub plain users due to the multiple entries. -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c5 --- Comment #5 from Harald Koenig <koenig@linux.de> 2009-01-05 02:50:33 MST --- Created an attachment (id=263164) --> (https://bugzilla.novell.com/attachment.cgi?id=263164) perl-BL-standalone-log oops, just notice the "needinfo", so here is the next log... -- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c6 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |koenig@linux.de --- Comment #6 from Josef Reidinger <jreidinger@novell.com> 2009-01-05 02:59:32 MST --- One interesting think, you have more disks then noticed in device.map...and first disk looks like usb stick (hardisk or usb memory card reader), am I right? This looks like it cause problems. Because current root cannot be translated to grub device (perl-Bootloader translate using device.map). This should not happen in future, because you have hd0 <-> sda, but now is by default during propose using udev, so it correctly map hd0<-> disk-by-id. -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c7 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|koenig@linux.de | --- Comment #7 from Harald Koenig <koenig@linux.de> 2009-01-05 03:09:54 MST --- (In reply to comment #6 from Josef Reidinger)
One interesting think, you have more disks then noticed in device.map...and first disk looks like usb stick (hardisk or usb memory card reader), am I right?
correct. sda is the internal 3ware raid, sdb..sde are 4 external usb disks
This looks like it cause problems. Because current root cannot be translated to grub device (perl-Bootloader translate using device.map). This should not happen in future, because you have hd0 <-> sda, but now is by default during propose using udev, so it correctly map hd0<-> disk-by-id.
-- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c8 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |koenig@linux.de --- Comment #8 from Josef Reidinger <jreidinger@novell.com> 2009-01-05 04:38:07 MST --- Interesting think is that as hd0 is /dev/disk/by-id/usb-Maxtor_OneTouch_II_B41M9YBH-0:0, but I expect, that you have your /boot on /dev/sda5, which is on raid...so you have your boot partition on your raid, correct? (I am little confused by many devices you have :) -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c9 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|koenig@linux.de | --- Comment #9 from Harald Koenig <koenig@linux.de> 2009-01-05 10:38:33 MST --- (In reply to comment #8 from Josef Reidinger)
Interesting think is that as hd0 is /dev/disk/by-id/usb-Maxtor_OneTouch_II_B41M9YBH-0:0,
Maxtor_OneTouch_II is only hd0 when booting form DVD9 for update. I guess that's because the 3ware driver (3w_xxxx) gets loaded _after_ the usb storage modules. so the usb disks are detected first and the internal raid later (too late). during update the internal raid is sdc (boot partition was sdc5, now back as sda5)
but I expect, that you have your /boot on /dev/sda5, which is on raid...so you have your boot partition on your raid, correct? (I am little confused by many devices you have :)
correct! it's not only you being confused;) but it's quite easy (TM) to fix fstab and menu.lst after update -- not sure if this is really worth a bug report (though it's really annoying and IMHO a nasty bug) because my setup s a bit exotic and it's hard to describe and test (well, now this happend, so you can fix that bug too;)) unfortuneately(?) the 3ware raid partitions do not show up in /dev/disk/by-id/ (only LVM PV sda7 shows up as /dev/disk/by-id/lvm2-pvuuid-*) the boot partition sda5 only shows up in /dev/disk/by-path/ and /dev/disk/by-uuid/ (but I don't like those long paths in fstab and menu.st anyway for "optical" reasons -- so I myself can live with those renaming problems;) -- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c10 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jreidinger@novell.com |juhliarik@novell.com Status|ASSIGNED |NEW --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2009-01-06 07:50:56 MST --- OK, so it looks like problem of yast part of upgrade, which change device map. I reassign it to jozo. -- 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=463450 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c11 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #11 from Jozef Uhliarik <juhliarik@novell.com> 2009-01-06 08:48:34 MST --- I am sorry the problem is that your old device.map included /dev/sda like hd0 without your USB devices. It is disk where you had 11.0. Your changes (adding new USB devices) are cause of problem with updating device.map /dev/sda is now your USB device and it means that device exist but it is different from previous meaning /dev/sda :( I used it like valid disk but... during update it is /dev/sdc not /dev/sda :( The problem is solved by using persistent device names in 11.1. I am sorry. If you want continue with your own way (adding new devices) please take care about necessary changes in device.map. In your case change /dev/sda to /dev/sdc. Your changes are not handled automatic. It is really hard to detect that /dev/sda is now /dev/sdc :( The idea is use persistent device names but it is implement in 11.1 :( -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c12 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #12 from Harald Koenig <koenig@linux.de> 2009-01-06 10:20:59 MST --- I reopen this ticket because the main topic/bug (see summary) is the creation of 3 identical copies of grub entries (one for each kernel rpm) and not the issue of disk devices (re)naming... (In reply to comment #11 from Jozef Uhliarik)
I am sorry the problem is that your old device.map included /dev/sda like hd0 without your USB devices. It is disk where you had 11.0. Your changes (adding new USB devices) are cause of problem with updating device.map /dev/sda is now your USB device and it means that device exist but it is different from previous meaning /dev/sda :( I used it like valid disk but... during update it is /dev/sdc not /dev/sda :(
The problem is solved by using persistent device names in 11.1. I am sorry.
If you want continue with your own way (adding new devices) please take care about necessary changes in device.map. In your case change /dev/sda to /dev/sdc.
sda is perfectly correct for normal operation because in myinitrd I load driver "3w-xxxx" before any usb driver, so my internal raid is sda. unfortuneately this is not true when booting from DVD. but as stated before, I can live with that (or switch using persistent device names, I have to sleep on that once more ... ;-))
Your changes are not handled automatic. It is really hard to detect that /dev/sda is now /dev/sdc :( The idea is use persistent device names but it is implement in 11.1 :(
totally agreed. but: is this (wrong?) device map entry the reason for creating multiple grub entries ? FYI: I just noticed that after update the devices.map entry now is (hd0) /dev/disk/by-id/usb-Maxtor_OneTouch_II_B41M9YBH-0:0 so for now I changed it back to (hd0) /dev/sda because there seems to be no real persistent name for "sda" (I can't put my raid controller into another PCI slot without running into trouble): # find /dev/ -lname \*sda /dev/disk/by-path/pci-0000:02:0d.0-scsi-0:0:0:0 /dev/disk/by-uuid/d5dd2a9b-8322-47db-bd02-2004f69f7b27 only the boot partition sda5 can be found via /dev/disk/by-uuid/... : # find /dev/ -lname \*sda5 -ls 821 0 lrwxrwxrwx 1 koenig root 10 Jan 4 17:36 /dev/disk/by-uuid/d5dd2a9b-8322-47db-bd02-2004f69f7b27 -> ../../sda5 819 0 lrwxrwxrwx 1 koenig root 10 Jan 4 17:36 /dev/disk/by-path/pci-0000:02:0d.0-scsi-0:0:0:0-part5 -> ../../sda5 -- 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=463450 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c13 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #13 from Josef Reidinger <jreidinger@novell.com> 2009-01-06 10:29:45 MST --- Yes, that is reason, because translating from current '/' (which is on raid /dev/sda) failed (not in device map)...and fallback to hd0. but hd0 is from device map translated as usb disk (sdb). So when another kernel is added (now there is three kernels base,normal and extra (depends on how many modules it have)) I check if that kernel is not already added...and find only image section with hd0 and think, that that entry is for boot another disk (usb disk sdb) and add new section with fallbackem hd0. So yes, it is reason for this multiple entry (I hope I start some discussion about changing fallbacking, because it sometime very confuse). -- 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=463450 User koenig@linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=463450#c14 --- Comment #14 from Harald Koenig <koenig@linux.de> 2009-01-06 17:37:34 MST --- (In reply to comment #13 from Josef Reidinger)
Yes, that is reason, because translating from current '/' (which is on raid /dev/sda) failed (not in device map)...and fallback to hd0. but hd0 is from device map translated as usb disk (sdb).
ACK: after fixing device.map I don't get any additional grub entries anymore. thanks for the explanation! -- 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