https://bugzilla.novell.com/show_bug.cgi?id=381726 Robert Vojcik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rvojcik@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |juhliarik@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=381726 User gilles.sabourin@free.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c2 --- Comment #2 from Gilles Sabourin 2008-04-24 11:03:14 MST --- Created an attachment (id=210281) --> (https://bugzilla.novell.com/attachment.cgi?id=210281) YaST2 logs -- 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=381726 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c4 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |aschnell@novell.com --- Comment #4 from Jozef Uhliarik 2008-04-25 06:06:39 MST --- Ordering of disks in device.map is by bios_id. (fd0) /dev/fd0 (hd1) /dev/sda (hd0) /dev/sdc (hd2) /dev/sdb is correct by Target Map from yast2-storage. Also proposed boot sections is OK. You can check end of y2log-1 from attachment. IMO wrong device.map is responsible for broken menu.lst But it is question for Alexander (perl-Bootloader) Arvin could you check why storage returns wrong ordering(bios_id) of disks please? -- 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=381726 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c6 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|juhliarik@novell.com |snwint@novell.com --- Comment #6 from Jozef Uhliarik 2008-04-28 02:45:44 MST --- I wrote it wrong sorry. BIOS ID is number indicates order of disk by BIOS. 0x80 - first 0x81 - second .. yast2-storage returns information where is wrong BIOS ID. It means that yast2-bootloader had wrong info that the first disk is /dev/sdc (0x80) the second /dev/sda (0x81) and finally /dev/sdb (0x82). yast2-bootloader creates "wrong" device.map (order of disks) by BIOS ID. Reporter wrote (Description) that the correct device map and also order of disks is: (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdc hwinfo provides BIOS ID for yast2-storage. reassign to Steffen (hwinfo) Steffen could you verify why yast2-storage provides wrong BIOS ID please? -- 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=381726 User gilles.sabourin@free.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c8 --- Comment #8 from Gilles Sabourin 2008-04-28 10:18:34 MST --- Created an attachment (id=210917) --> (https://bugzilla.novell.com/attachment.cgi?id=210917) hwinfo disk from openSUSE 11b1 -- 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=381726 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c10 Mark Gray changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markgray+to-suse@puck.nac.net --- Comment #10 from Mark Gray 2008-04-28 10:58:31 MST --- (In reply to comment #0 from Gilles Sabourin) [snip]

Now, I am not able to boot openSUSE 11 anymore; whenever I select "openSUSE 11" in grub menu, I get this error :

Bad File or directory. Error 2.

This is a different bug entirely: see Bug #358483 - add grub support for 256-byte inodes. 10.3's grub cannot read the 256-byte inodes created by default by 11.0's mkfs.ext3 (I ran into the same problem but was lucky enough to have seen it mentioned on a mailing list :-) -- 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=381726 User gilles.sabourin@free.fr added comment https://bugzilla.novell.com/show_bug.cgi?id=381726#c12 Gilles Sabourin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|gilles.sabourin@free.fr | --- Comment #12 from Gilles Sabourin 2008-04-29 09:20:08 MST --- Sorry, I was a bit long. I was searching a mean to reinstall suse 11 bootloader and I have failed to do so. I reinstalled opensuse 11. As Mark told us, my problem came in fact from Bug #358483. opensuse 11 used to boot, but I did not see any grub menu to boot windows or opensuse 10.3 : I should have pressed <ESC> to see it. So I supposed badly that a better way was to reinstall 10.3 bootloader, but I fell into Bug #358483. Next, I had a look to device.map and supposed wrongly this was the origin of my problem. You can close this bug report : sorry for the disturbance. -- 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.