Public bug reported:
Binary package hint: base-installer
The Edgy (beta) alternate installer cannot install grub into the system
root partition.
Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I
told the installer not to install GRUB on the MBR, but to install into
/dev/sda6 (the / partition I am installing Edgy on, filesystem is
reiserfs). It produced an error saying it could not install grub.
To gain a working installation, I had to complete the following steps:
Boot the alternate installer CD, choose rescue mode, and open a shell in
/dev/sda6. Issue the command "grub-install /dev/sda6". This installs
grub, but it still cannot boot because there is no menu.lst file.
Mount another Ubuntu install and copy the menu.lst file from there.
Edit menu.lst to reflect the actual kernel files present. This is not so
easy, as the shell that the rescue mode dumps you into is incapable of
using either vi or nano, so I had to boot a different OS, mount the new
partition and edit menu.lst from there. Call that a rescue disk? With no
working editor?
Edit the master bootloader to add Edgy to the menu and chainload the
partition - this step was expected of course.
** Affects: base-installer (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Description changed:
Binary package hint: base-installer
The Edgy (beta) alternate installer cannot install grub into the system
root partition.
Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I
told the installer not to install GRUB on the MBR, but to install into
/dev/sda6 (the / partition I am installing Edgy on, filesystem is
reiserfs). It produced an error saying it could not install grub.
To gain a working installation, I had to complete the following steps:
- Boot the alternate CD, choose rescue mode, and open a shell in
+ Boot the alternate installer CD, choose rescue mode, and open a shell in
/dev/sda6. Issue the command "grub-install /dev/sda6". This installs
grub, but there is still no menu.lst created.
Mount another Ubuntu install and copy the menu.lst file from there.
Edit menu.lst to reflect the actual kernel files present. This is not so
easy, as the shell that the rescue mode dumps you into is incapable of
using either vi or nano, so I had to boot a different OS, mount the new
partition and edit menu.lst from there. Call that a rescue disk? With no
working editor?
Edit the master bootloader to add Edgy to the menu and chainload the
partition - this step was expected of course.
** Description changed:
Binary package hint: base-installer
The Edgy (beta) alternate installer cannot install grub into the system
root partition.
Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I
told the installer not to install GRUB on the MBR, but to install into
/dev/sda6 (the / partition I am installing Edgy on, filesystem is
reiserfs). It produced an error saying it could not install grub.
To gain a working installation, I had to complete the following steps:
Boot the alternate installer CD, choose rescue mode, and open a shell in
/dev/sda6. Issue the command "grub-install /dev/sda6". This installs
- grub, but there is still no menu.lst created.
+ grub, but it still cannot boot because there is no menu.lst file.
Mount another Ubuntu install and copy the menu.lst file from there.
Edit menu.lst to reflect the actual kernel files present. This is not so
easy, as the shell that the rescue mode dumps you into is incapable of
using either vi or nano, so I had to boot a different OS, mount the new
partition and edit menu.lst from there. Call that a rescue disk? With no
working editor?
Edit the master bootloader to add Edgy to the menu and chainload the
partition - this step was expected of course.
--
Cannot install grub into root partition
https://launchpad.net/bugs/63869
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
