https://bugzilla.novell.com/show_bug.cgi?id=326372#c1 --- Comment #1 from Klaus Kämpf 2007-09-19 07:08:10 MST --- Created an attachment (id=173343) --> (https://bugzilla.novell.com/attachment.cgi?id=173343) /etc/grub.conf -- 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=326372#c3 --- Comment #3 from Klaus Kämpf 2007-09-19 07:09:48 MST --- Created an attachment (id=173346) --> (https://bugzilla.novell.com/attachment.cgi?id=173346) y2log from installed system (/mnt) -- 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=326372#c5 --- Comment #5 from Klaus Kämpf 2007-09-19 07:13:06 MST --- Created an attachment (id=173348) --> (https://bugzilla.novell.com/attachment.cgi?id=173348) menu.lst from system in question I do not think that all those '/dev/sda2' are right ... -- 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=326372 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |odabrunz@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=326372#c8 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #8 from Alexander Osthof 2007-09-20 01:01:28 MST --- Maybe also related to #309837. Will take care as soon as mentioned bug is fixed, cos it's a blocker, too. :( But if I'm fortunate, this one will also be resolved by this fix. We'll see. -- 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=326372#c10 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kkaempf@novell.com | --- Comment #10 from Klaus Kämpf 2007-09-24 09:22:42 MST --- See https://bugzilla.novell.com/show_bug.cgi?id=304269, thats all I 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=326372#c12 --- Comment #12 from Olaf Dabrunz 2007-09-24 11:05:07 MST --- (Notes on the logs in this bug, comment #2: First a device mapping is detected here: ------------------------------------------------------------------ 2007-09-19 08:29:35 <1> 10.10.0.65(3548) [YCP] bootloader/routines/lilolike.ycp:1210 Detected device mapping: $[ "/dev/fd0":"fd0", "/dev/sda":"hd0", "/dev/sdb":"hd1" ] ------------------------------------------------------------------ This looks correct but is irrelevant, because it is overridden by the device map read from the target system a bit later: ------------------------------------------------------------------ 2007-09-19 08:29:37 <1> 10.10.0.65(3548) [YCP] bootloader/routines/lib_iface.ycp:256 Reading device mapping 2007-09-19 08:29:37 <1> 10.10.0.65(3548) [wfm] Y2SystemFunction.cc(useRemote):129 'getDeviceMapping': switched to remote 2007-09-19 08:29:37 <1> 10.10.0.65(3548) [wfm] Y2StdioFunction.cc(evaluateCall):137 Evaluating remote call to 'Bootloader_API::getDeviceMapping' 2007-09-19 08:29:37 <1> 10.10.0.65(3548) [YCP] bootloader/routines/lib_iface.ycp:263 Read device mapping: $[ "/dev/fd0":"fd0", "/dev/sdb":"hd1" ] ------------------------------------------------------------------ The error immediately afterwards is ugly but does not matter (it redefines the global variable device_mapping as a local variable, but the contents of the global variable remain intact, as shown in my tests and later in the logs): ------------------------------------------------------------------ 2007-09-19 08:29:37 <3> 10.10.0.65(3548) [Interpreter] BootCommon.ycp:629 YEVariable::evaluate (device_mapping) is not initialized 2007-09-19 08:29:37 <3> 10.10.0.65(3548) [Interpreter] BootCommon.ycp:629 Argument (device_mapping) to mapmap(...) is nil ------------------------------------------------------------------ A bit later the device map reappears twice, the last time here: ------------------------------------------------------------------ 2007-09-19 08:29:37 <1> 10.10.0.65(3548) [YCP] bootloader/routines/lilolike.ycp:956 Updated device map: $[ "/dev/fd0":"fd0", "/dev/sdb":"hd1" ] ------------------------------------------------------------------ )

From bug 304269, comment #8 and at the end of the logs in same bug 304269, comment #13 I can only see that the device.map still contained a mapping for "/dev/sda":

------------------------------------------------------------------ 2007-08-24 08:17:07 <1> 10.10.0.65(3527) [YCP] bootloader/routines/lilolike.ycp:873 Updated device map: $[ "/dev/fd0":"fd0", "/dev/sda":"hd0", "/dev/sdb":"hd1" ] ------------------------------------------------------------------ So somewhere between the run of YaST2 in bug 304269 and the logs in this bug here, "/dev/sda" disappears from the device.map. As perl-Bootloader does not write device.map, it seems this was changed outside of YaST and perl-Bootloader, e.g. manually? But juhliarik@ can reproduce the bug, looking at the logs in comment #11. -- 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=326372#c14 Olaf Dabrunz changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical Summary|Beta3->RC1 upgrade: Error occured while |Beta3->RC1 upgrade: Error occured while |installing Grub, error while parsing number |installing Grub, error while parsing number: | |device missing from device.map before update | |starts --- Comment #14 from Olaf Dabrunz 2007-09-24 13:12:48 MST --- As we did not reproduce this bug ("device missing from device.map before update starts") so far, I am downgrading it to critical. -- 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=326372#c16 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker --- Comment #16 from Klaus Kämpf 2007-09-25 01:52:20 MST --- opensuse-updater offered me a kernel update (to kernel-default-2.6.22.5-29) which I installed and rebooted. The reboot failed with grub saying "Error parsing number" because the 'root' line again contains: root (/dev/sda2,1) Raising to blocker again. -- 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=326372#c18 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kkaempf@novell.com | --- Comment #18 from Klaus Kämpf 2007-09-25 03:49:47 MST --- No. I'm testing RC1 + online updates. -- 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=326372#c20 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|kkaempf@novell.com | Resolution| |FIXED --- Comment #20 from Stephan Kulow 2007-09-25 04:05:39 MST --- Your case is very likely just a cause of the RC1 being broken. -- 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=326372#c22 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Beta3->RC1 upgrade: Error occured while |RC1->RC2 upgrade: Error occured while installing |installing Grub, error while parsing number: |Grub, error while parsing number: device missing |device missing from device.map before update |from device.map before update starts |starts | --- Comment #22 from Klaus Kämpf 2007-09-26 05:22:41 MST --- Adapting summary, logs will follow -- 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=326372#c24 --- Comment #24 from Klaus Kämpf 2007-09-26 05:27:46 MST --- Created an attachment (id=174816) --> (https://bugzilla.novell.com/attachment.cgi?id=174816) tar.gz from 1st stage install (instsys) -- 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=326372#c26 --- Comment #26 from Klaus Kämpf 2007-09-26 05:29:42 MST --- comment #23: correction: /dev/sda1 is in /etc/grub.conf, /boot/grub/menu.lst shows /dev/sda2 instead of hd0 -- 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=326372#c28 --- Comment #28 from Klaus Kämpf 2007-09-26 05:32:59 MST --- Created an attachment (id=174820) --> (https://bugzilla.novell.com/attachment.cgi?id=174820) /boot/grub/device.map, missing hd0 ?! -- 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=326372 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- 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=326372#c31 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kkaempf@novell.com | --- Comment #31 from Klaus Kämpf 2007-09-27 03:53:09 MST --- Sorry, no improvement in RC3. Still the same error. -- 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=326372#c33 --- Comment #33 from Stephan Kulow 2007-09-27 05:12:11 MST --- ok. We will have to wait with any kernel updates with the fix of this - unless of course Klaus installs RC3 and everything is fine. -- 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=326372#c36 --- Comment #36 from Klaus Kämpf 2007-09-27 05:33:12 MST --- The wrong device.map might be the result of earlier upgrades. (??) Running "grub --device-map=/tmp/device.map" in the final system does create a correct map. -- 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=326372#c38 Klaus Kämpf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mantel@novell.com, snwint@novell.com --- Comment #38 from Klaus Kämpf 2007-09-27 05:42:38 MST --- Its probably an inst-sys / chroot problem. Doing a chroot /mnt grub --device-map=/tmp/device.map results in _just_ (fd0) /dev/fd0 in /tmp/device.map proc is mounted, seems as if more filesystems must be mounted in order to make grub behave. -- 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=326372#c40 --- Comment #40 from Klaus Kämpf 2007-09-27 05:44:27 MST --- comment #38: The chroot-ed system has proc, sysfs and udev mounted. -- 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=326372#c43 --- Comment #43 from Klaus Kämpf 2007-09-27 05:54:01 MST --- Running "mount --bind /dev /mnt/dev" before chroot results in grub finding all devices and writing a correct device.map. Is the bind mount issued too late ? If a user-created device.map is merged with the detected device map, why are devices missing ? -- 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=326372#c45 --- Comment #45 from Klaus Kämpf 2007-09-27 05:59:47 MST --- Looking at y2log-1, it seems the bind mount is issued wrongly. Look for clients/bootloader_finish.ycp:75 unable to bind mount /dev in chroot -- 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=326372#c47 --- Comment #47 from Klaus Kämpf 2007-09-27 06:16:23 MST --- Manually fixing /boot/grub/device.map and running (RC3->RC3) upgrade again does not show this error. So its indeed triggered by a wrong device.map. I'll re-run the (RC3->RC3) upgrade now once more, this time with pre-10.3 device names (namely /dev/hdX for the ATA drive) in device.map. If bootloader config copes with this, I do not consider this a blocker any more. -- 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=326372#c49 Olaf Dabrunz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kkaempf@novell.com --- Comment #49 from Olaf Dabrunz 2007-09-27 06:31:12 MST --- Did the actual mapping of Linux devices names to GRUB device names change, or only the order of the entries in the device.map? -- 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=326372#c51 --- Comment #51 from Klaus Kämpf 2007-09-27 06:36:33 MST --- My second test, with (assumed 10.2 setup with hd0 ATA, hd1 SATA) (hd0) /dev/hda (hd1) /dev/sda _FAILED_ -- 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=326372#c53 --- Comment #53 from Klaus Kämpf 2007-09-27 06:40:02 MST --- Created an attachment (id=175153) --> (https://bugzilla.novell.com/attachment.cgi?id=175153) manually edited device.map -- 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=326372#c55 --- Comment #55 from Klaus Kämpf 2007-09-27 06:41:33 MST --- Created an attachment (id=175155) --> (https://bugzilla.novell.com/attachment.cgi?id=175155) grub error message -- 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=326372#c57 --- Comment #57 from Klaus Kämpf 2007-09-27 06:44:28 MST --- With the device.map from comment #51, grub.conf and menu.list get 'hd1' where '/dev/sda1' was filled in before. Both values are wrong, the correct value should be 'hd0'. -- 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=326372#c59 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #59 from Alexander Osthof 2007-09-27 07:52:17 MST --- Ok, I've tried to reproduce this bug using a system with nearly the same configuration, thus an IDE harddisk for installation and an additionally SATA harddisk with a former SLES10-SP1 on it. I've installed a fresh 10.2 and subsequently updated to 10.3 RC3. Everything went fine, system booted normally. No mess up of device.map. Here are some logs, first the ones from fresh 10.2 installation: device.map: ----------- (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/hda fstab: ------ /dev/hda1 / ext3 acl,user_xattr 1 1 /dev/hda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 menu.lst: --------- # Modified by YaST2. Last modification on Thu Sep 27 11:58:43 UTC 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda1 vga=normal console=tty0 console=ttyS0,57600 sysreq=1 resume=/dev/hda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: SUSE Linux Enterprise Server 10 SP1 (/dev/sda1)### title SUSE Linux Enterprise Server 10 SP1 (/dev/sda1) kernel (hd0,0)/boot/vmlinuz-2.6.16.46-0.12-smp root=/dev/disk/by-id/scsi-SATA_Maxtor_7L250S0_L59NYFHG_L59NYFHG-part1 vga=normal sysreq=1 resume=/dev/sd a2 splash=silent showopts initrd (hd0,0)/boot/initrd-2.6.16.46-0.12-smp ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default /proc/partitions: ----------------- major minor #blocks name 7 0 72424 loop0 3 0 60051600 hda 3 1 10490413 hda1 3 2 4200997 hda2 8 0 244140625 sda 8 1 10490413 sda1 8 2 2104515 sda2 And now the ones from update to 10.3 RC3: device.map: ----------- (fd0) /dev/fd0 (hd1) /dev/sda (hd0) /dev/sdb fstab: ------ /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 menu.lst: --------- # Modified by YaST2. Last modification on Thu Sep 27 15:02:50 CEST 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd1,0) kernel /boot/vmlinuz-2.6.22.5-31-default root=/dev/disk/by-id/scsi-SATA_IC35L060AVER07-_SZPTZTAH755-part1 console=ttyS0,57600 console=tty0 sysreq=1 resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.22.5-31-default ###Don't change this comment - YaST2 identifier: Original name: SUSE Linux Enterprise Server 10 SP1 (/dev/sda1)### title SUSE Linux Enterprise Server 10 SP1 (/dev/sda1) rootnoverify (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd1,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd1,0) kernel /boot/vmlinuz-2.6.22.5-31-default root=/dev/disk/by-id/scsi-SATA_IC35L060AVER07-_SZPTZTAH755-part1 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.22.5-31-default ###Don't change this comment - YaST2 identifier: Original name: xen### title XEN root (hd1,0) kernel /boot/xen.gz console=com1 com1=57600 module /boot/vmlinuz-xen root=/dev/disk/by-id/scsi-SATA_IC35L060AVER07-_SZPTZTAH755-part1 console=ttyS0,57600 console=tty0 sysreq=1 resume=/dev/sda2 splash=silent showopts module /boot/initrd-xen /proc/partitions: ----------------- major minor #blocks name 7 0 69660 loop0 8 0 60051600 sda 8 1 10490413 sda1 8 2 4200997 sda2 8 16 244140625 sdb 8 17 10490413 sdb1 8 18 2104515 sdb2

From my point of view, everything looks fine. I assume there has been a fault derived from a former installation or maybe user intervention.

As I can't reproduce, I close this bug RESOLVED INVALID. -- 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.