http://bugzilla.novell.com/show_bug.cgi?id=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c6 --- Comment #6 from Josef Reidinger <jreidinger@novell.com> 2010-03-30 08:46:10 UTC --- (In reply to comment #5)
(In reply to comment #4)
This should not be problem, as we use udev links.
Indeed. Linux is using by-id links and doesn't care about disk order.
But grub has huge problems.
Problem is that in some time hd0,0 is written instead of correct entry.
In my case, hd(0,0) is the right entry since hd(0,0) == first disk in BIOS boot order. The bug is that grubs menu.lst contained hd(1,0) since the 'boot' disk shows up as sdb in Linux
Actually, there are two bugs since menu.lst still contained the boot entries for the previous (Milestone 2) kernel !
Boot order is stored in /boot/grub/device.map so if you change boot order in BIOS you must regenerate whole boot configuration. Otherwise yast2-bootloader should store correct order and I use this order. It is not two bugs just two effects of one bug :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.