http://qa.mandrakesoft.com/show_bug.cgi?id=4465
------- Additional Comments From [EMAIL PROTECTED] 2003-02-10 18:46 ------- Not sure whether this is a separate bug or not, but the symptoms are similar - Have Windows NT4 on /dev/hda1, Windows 2000 on /dev/hdg, Xandros on /dev/hda5, and Mandrake on /dev/hde. When I upgraded from 8.2 to 9.1, grub was installed on /dev/hde or /dev/hde3 (not sure which), on the secondary (Promise) controller. And it worked! The disk got full, so I got a larger disk, partitioned it (without the Windows partitions), which made /boot on /dev/hde1 (instead of /dev/hde3) and / on /dev/hde5 (same as before) and swap on /dev/hde6 (same as before), and copied the files over with tar through a pipe. (So, the boot sectors were not copied). Problem is, running the 9.2 rc2 installer, it decided to install grub back on /dev/hda or /dev/hda2 (not sure which) - but it didn't work. Running "Reinstall boot loader" with CD in rescue mode didn't help - couldn't find the bios drive. Running grub-install fails, as it looks for sed and uniq, which aren't in the rescue ramdisk. Was able to create a grub floppy by running grub directly in rescue environment, like grub> root=(hd1,0) grub> setup (fd0) , which made a nonworking menu (bunch of cdrom junk from the grub.conf in the rescue ramdisk I suspect) but I was able to boot by dropping into the grub command line and issuing grub> root=(hd1,0) grub> kernel=/grub/vmlinuz-2.4.22-6 devfs=mount root=/dev/hde5 grub> boot Still can't seem to find a way to get either drakboot or grub to write the bootloader with a working menu. I guess if I can find the grub.conf and modify it, that might help, but this could be a bit more automatic. HTH -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEEDINFO creation_date: description: The "bootloader" is now before the "summary screen". When selecting a bootloader, we see a visualization and report of pushing the bootloader to the selected partition. The summary screen allows to modify the bootloader options, e.g. to select `grub` or to select linux-nonfb as the default loader mode. However, these changes will not take effect as it seems the bootloader is not reinstalled after doing any changes here.
