http://bugzilla.novell.com/show_bug.cgi?id=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c39 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kkaempf@novell.com --- Comment #39 from Josef Reidinger <jreidinger@novell.com> 2010-06-21 10:16:26 UTC --- (In reply to comment #38)
(In reply to comment #37)
Klaus - does zypper dup change device.map? How should I know ? It should not change it. Do you have correct one?
There is no 'correct' or 'wrong' device.map Whats wrong is the detection of which device was used for booting
device.map reflect order of booting for x86 based machines. BIOS code 0x80 is for first device to boot etc...it is important mainly when you write boot code to MBR.
I also cannot find any valid menu.lst each one which I see in logs has broken hd(0,0) so is menu.lst fixed before upgrade? I manually fix menu.lst because I cannot boot otherwise.
Interesting is that I cannot find correct one logs. Could you specify date when you update ( There is quite a lot of message, so time could help me to better identify it).
(perl-Bootloader during update/upgrade doesn't 'fix' menu, it just try to change in same way as it works before)
How does perl-Bootloader determine what to use as 'root' device ?
When you update the root device is device which is mounted under /boot (or / if /boot is not separated). So it try to find if there is some device which has as root device which is mounted as /boot. If it is not found then add default arguments and add it. Of course if it is broken before update it doesn't remove old entries as It think that it is for another system. -- 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.