https://bugzilla.novell.com/show_bug.cgi?id=438998 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |fred.blaise@gmail.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=438998 User fred.blaise@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=438998#c3 Fred Blaise changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|fred.blaise@gmail.com | --- Comment #3 from Fred Blaise 2008-10-28 13:34:01 MDT --- Created an attachment (id=248411) --> (https://bugzilla.novell.com/attachment.cgi?id=248411) /var/log/YaST2 directory I installed vanilla kernel 2.6.27-4, ultimately ran make install, which trigged mkinitrd.. The new grub stanza shows root (hd1,1), instead of (hd0,1) in this current case. Attached is the yast2 directory. -- 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=438998 User fred.blaise@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=438998#c5 Fred Blaise changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|fred.blaise@gmail.com | --- Comment #5 from Fred Blaise 2008-10-29 03:32:10 MDT --- Very simple indeed.. Either take a vanilla kernel (make, make install) or another kernel rpm (rpm -ivh), and install it. Of course, my disk layout is a bit special maybe. I have 3 disks. / and /boot on raid1 over the 3 disks. But on the first disk, very first partition is a windows partition (since I install it first), /boot is second, / is third. On the 2nd and 3rd disk, /boot is first and / is second. Apparently, in my case, grub sets root (hd1,1), which means it picks up the 2nd disk and the second partition, which would be correct on the first disk, but unfortunately, not the second one. -- 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=438998 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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=438998 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=438998#c8 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|juhliarik@novell.com |snwint@novell.com --- Comment #8 from Jozef Uhliarik 2009-01-15 04:45:59 MST --- Josef device map is correct and order of disks depend on bios_id. It means if /dev/sda has bios_id 0x81 it is the second disk in order. The first disk in order (from target map) is /dev/sdc (0x80). IMO device map is correct. There can be wrong detection of order by hwinfo or user change order of booting before he start with installation (after installation return back previous booting order). Next: "/boot" is on /dev/md0 which is sw riad (raid version 1) and it is necessary select only one real partition from /dev/md0. "/dev/md0":[ "/dev/sda2", "/dev/sdb1", "/dev/sdc1" ], (hd1,1) in this case mean /dev/sda2 which is from /dev/md0. I hope that now it is clear. If there exist problem with wrong detection of order (see comment #3) reassing to snwint. Steffen it seems that problem is in wrong detection of order. (see comment #3) -- 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.