Bug 121980 - GRUB configuration is overwriting LILO in MBR, causing inability to boot anything else)
Summary: GRUB configuration is overwriting LILO in MBR, causing inability to boot anyt...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: i686 All
: P5 - None : Major
Target Milestone: ---
Assignee: Olaf Dabrunz
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 15:00 UTC by Ulrich Windl
Modified: 2006-04-21 14:19 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/etc/grub.conf from /dev/sda9 (54 bytes, text/plain)
2006-04-13 08:55 UTC, Ulrich Windl 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2005-10-10 15:00:43 UTC 
After update (from 9.2) on /dev/sda9 (2nd disk) GRUB has been installed in
/dev/sda9 (as before), but silently also to /dev/hda (1st disk). In my special
configuration, this caused only the new system to be listed for booting.

My configuration before update was this:
/dev/hda: LILO in MBR, hda1 is Windows/XP, hda5 is FAT32 (data)
/dev/sda: boot partition is sda1, root in sda5, sda6 is swap, sda7 is home, sda9
is the experimental system with GRUB in the pertition's boot sector
(GRUB on sda9 is started from LILO on sda1 (via MBR of hda))

After update /etc/grub.conf had install instreuctions for both, sda9 and hda.
Comment 1 Michael Radziej 2005-10-10 17:22:26 UTC 
Can you please attach the /var/log/YaST2 directory (as a tar file)?
Please take a look at http://www.opensuse.org/Bug_Reporting_FAQ#YaST
if you have any problems.
Comment 2 Ulrich Windl 2005-10-12 06:38:02 UTC 
Please see ttachment #53799 to Bug #121990. (I think it makes little sense to
attach the same file multiple times.)
Comment 3 Jiri Srain 2005-12-15 12:11:10 UTC 
Reasigning to new maintainer
Comment 4 Ulrich Windl 2006-01-23 07:25:15 UTC 
Ststus update: The problem happened again for the recent GRUB online update, resulting in unbootable Windows (until repair).
Comment 5 Torsten Duwe 2006-04-03 12:36:38 UTC 
According to your Yast2 logs, lilo is used to boot the system!?
Can you paste /etc/grub.conf from /dev/sda9 here?
Comment 6 Ulrich Windl 2006-04-03 13:52:00 UTC 
Providing grub.conf from /dev/sda9 is quite difficult, because I've sold the PC in the meantime and /dev/sda is lying around outside of any PC. I'll see if I can arrange some access to the hardware.
Comment 7 Ulrich Windl 2006-04-13 08:55:28 UTC 
Created attachment 78150 [details]
/etc/grub.conf from /dev/sda9

Revived /dev/sda to get the file
Comment 8 Ulrich Windl 2006-04-13 08:57:48 UTC 
Notes to comment #5 and comment #9: /etc/grub.conf may be rewritten during online-update. Maybe I changed it after that. I can vaguely remember two "setup" lines: One for /dev/hda, and one for /dev/sda9
Comment 9 Torsten Duwe 2006-04-21 14:19:18 UTC 
There's no way an RPM update of grub changes your /etc/grub.conf . If update via YOU or similar does that, please re-open. The attachment from Comment #7 is perfectly fine and will leave your MBR intact, agreed. When /dev/hda reappears, re-open.