<font color='black' size='2' face='arial'>
<div> <font size="2"><font face="Arial, Helvetica, sans-serif">Oh yea, now that I'm thinking about it I forgot to mention that when the installer gets to the partitioner, choose manual to set the mount points. The one install I tried with this installer that failed, I chose the second option, which was "Empty and use entire disk". I though I would try letting the installer do everything. Didn't work.</font></font><br>
</div>
<div> <br>
</div>
<div> <br>
</div>
-----Original Message-----<br>
From: Tom H <tomh0665@gmail.com><br>
To: ubuntu-users@lists.ubuntu.com<br>
Sent: Fri, Oct 30, 2009 7:53 am<br>
Subject: Re: boot loader not installed (solved)<br>
<br>
<div id="AOLMsgPart_0_13527426-08a3-4746-9bcf-d8fc4ff8b92a" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<pre style="font-size: 9pt;"><tt>On Fri, Oct 30, 2009 at 3:43 AM, <<a href="mailto:fyrbrds@netscape.net">fyrbrds@netscape.net</a>> wrote:<br>
> Ok, finally got it to work. In the midst of all the troubleshooting today,<br>
> the final 9.10 was released. Since I had never even booted into the old<br>
> install, I cut my losses and reinstalled with a freshly downloaded copy.<br>
> This had the exact same problem and would not boot so my hopes that this<br>
> would be fixed in the release version were not realized. Then I found this<br>
> document:<br>
> <a href="http://grub.enbug.org/BIOS_Boot_Partition" target="_blank">http://grub.enbug.org/BIOS_Boot_Partition</a><br>
> It talks about setting aside space for grub to install itself on the raid in<br>
> a special partition with the boot flag set. It says that if grub sees such a<br>
> partition it will automatically install itself there thus overwriting<br>
> whatever was there before. So here is what I did:<br>
> Fired up the live cd. Ran the partitioner directly. I wiped all the old<br>
> partitions from the drive.<br>
> I made an extended partition using the entire drive<br>
> I made a small ext4 logical partition (the instruction says no file system<br>
> is needed but I took no chances) using the minimum 8MB<br>
> The example command given on the howto page DID NOT WORK. Just right<br>
> click the partition after it is created and select Flag->boot<br>
> Made an ext4 partition for the root fs.<br>
> Made a 8GB swap partition and a 8GB ext4 /tmp partition<br>
> I committed the changes and let the partitions be formatted<br>
> I started the installer<br>
> At the partitioning section I set the small 8MB partition as "unused" by<br>
> highlighting it and clicking "Change"<br>
> I assigned the mount points for the other partitions and left the format<br>
> unchecked since that was just done.<br>
> At the Summary screen that displays before the copy process starts, I<br>
> clicked "Advanced." Here you have to select the boot partition.<br>
> Here were two new options I did not have before<br>
> /dev/mapper/nvidia_fhgbbaae (dmraid)<br>
> /dev/mapper/nvidia_fhgbbaae (linear)<br>
> I overrode (hd0) which had always failed, and selected<br>
> /dev/mapper/nvidia_fhgbbaae (linear)<br>
> for this choice I assumed that the dmraid option would depend on the raid<br>
> being mounted properly and the linear method would keep it simple.<br>
> Then I clicked forward to let the installation commence. When it was<br>
> finished I opened a file manager and looked in the new file system at<br>
> /target/boot/grub/. Where it had always been empty before, now it had 13<br>
> files in it.<br>
> These included default, device.map, menu.lst, stage1, stage2, etc. I<br>
> immediately recognized these as files other troubleshooting howtos had<br>
> referenced. Also encouraging was the device.map containing this entry:<br>
> (hd0) /dev/mapper/nvidia_fhgbbaae<br>
> It is possible that leaving the (hd0) in the advanced setting earlier would<br>
> have worked with this value being set. It had never been set before. But<br>
> there is no guarantee that it would not have chosen the dmraid option and<br>
> that it would still have worked.<br>
><br>
> Here is the entry in menu.lst that makes this work.<br>
> title Ubuntu 9.10, kernel 2.6.31-14-generic<br>
> root (hd0,5)<br>
> kernel /boot/vmlinuz-2.6.31-14-generic<br>
> root=/dev/mapper/nvidia_fhgbbaae6 ro quiet splash<br>
> initrd /boot/initrd.img-2.6.31-14-generic<br>
><br>
> Before rebooting, I opened a terminal for good measure and typed<br>
> # sudo update-grub<br>
><br>
> Then I rebooted and everything worked. The caveat is that my Vista boot<br>
> loader is on hd1, which is the default in my bios. To boot linux I have to<br>
> hit escape to manually select the boot drive. I can change that any time by<br>
> modifying the order of preference. I only mention that in case someone<br>
> follows this method and sets their raid as the boot drive as I did but<br>
> forgets that they were actually booting from their Windows or old OS drive.<br>
> Grub added an entry for Windows on the boot menu but I haven't tested it<br>
> yet. After I do, I will switch the boot order.<br>
><br>
> I now have a fully functioning Ubuntu 9.10<br>
><br>
> Thanks for all who offered assistance especially Tom and Goh Lip. It was the<br>
> documents you guys pointed out that led me to the fix. You also taught me a<br>
> lot about grub on the way. Thanks.<br>
<br>
:)<br>
<br>
I had read the <a href="http://grub.enbug.org/BIOS_Boot_Partition" target="_blank">http://grub.enbug.org/BIOS_Boot_Partition</a> in the past<br>
but would never have tried it for DMRAID because I associated it with<br>
GPT and EFI (helping a friend install Linux on a Mac Mini...). Thanks<br>
for the (surprising) info.<br>
<br>
-- <br>
ubuntu-users mailing list<br>
<a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a><br>
</tt></pre>
</div>
<!-- end of AOLMsgPart_0_13527426-08a3-4746-9bcf-d8fc4ff8b92a -->
</font>