I read that this bug can be fixed by changing the order in which the
BIOS reads the disks. I have not tested it. Since Hoary I have never
successfully install Ubuntu on this PC without first disconnecting my
300G drive and installing on one of the two 80G drives. Only
afterwards can I reconnect my 300G. I think GRUB misreads what the
BIOS thinks is sda and what the first hard disk actually is. I don't
think this problem has anything to do with IDE and SATA disks
conflicting with each other as someone suggested.

On 4/4/07, resume-writer <email address hidden> wrote:
> I know what a bios is, and I do recall something cool about my boot messages
> saying RAID Bios, blah blah. But, that's all I can say. To fix the problem,
> I just know that my boyfriend had to use some syntax from this post
> http://ubuntuforums.org/showthread.php?t=224351. I must admit, Windows would
> overwrite the Ubuntu bootloader if I had only Ubuntu installed at the time
> that I tried to create a dual boot. So, Windows doesn't handle this
> situation any better either. I have higher expectations for Unix then
> Windows. That's not very nice, and I apologize. I just got frustrated
> because I really wanted to install Ubuntu on my own, without needing my
> techie boyfriend to jump in an rescue me. I did do the partition on my own
> (though I was very scared). I appreciated the messages that told me the
> recommended swap, and stuff--for whatever that's worth. Good luck
> troubleshooting. Better you than me. :)
>
> Angela
>
> On 4/4/07, Roland Orre <email address hidden> wrote:
> >
> > Apology to Angela Akridge, I claimed that the bug you described was not
> > relevant. Sorry for this, I noticed that you had described the same
> > problem.
> >
> > Anyway,  may  guess is simply that the "--force-lba" option may be needed
> > in some script, and in that case it could possible be experienced as a bug
> > even though it wouldn't really be a bug in grub but in the bios then...
> >
> > Best regards
> > Roland
> >
> > On 4/4/07, Roland Orre < <email address hidden>> wrote:
> > > On 4/4/07, resume-writer <email address hidden> wrote:
> > > > I don't know. What I do know is that I received that message. My
> > boyfriend
> > > > (Solaris kernel engineer, thank God) had to edit some grub files or
> > > > something because Ubuntu overwrote my Windows boot loader with its
> > Ubuntu
> > > > bootloader. Then, he had to manually edit some files to tell the boot
> > loader
> > > > where to find the Windows partition. It was a total mess. I don't
> > understand
> > > > most of what went wrong. But, the bottom line is that it wasn't
> > Windows that
> > > > messed up. Ubuntu just doesn't know how to handle things when  Windows
> > is
> > > > installed prior to Ubuntu. Things are working well now. It's really
> > not an
> > > > OS for human beings. I'll stick with my Windows, thank you.
> > >
> > > Sorry, but the way the person named Angela Akridge describe this make
> > you
> > > sound more like a troll than anything else. I have used many different
> > distros
> > > on plenty of machines since 1996 using both lilo and grub but never ever
> > > had the problem that  a windows or dos partition would be ignored or the
> >
> > > boot loader overwritten in the installation. On the other hand if you
> > > first install
> > > a linux distro and after that a window you get problems.
> > > Anyway, what you describe has nothing with this hanging to do so the
> > place
> > > to write about this is not relevant.
> > >
> > > About the actual bug, I start suspect that it could be a problem
> > with  the
> > > bios on the actual M2N8-VMX motherboard where I experienced the
> > > hanging problem. After a kernel rebuild (to 2.6.20) the machine refused
> > > to boot, and it entered the grub shell all the time. Then I rerun the
> > > grub-install with the --force-lba option, and then it started smoothly.
> > >
> > > >
> > > > On 4/4/07, Steven Harms < <email address hidden>> wrote:
> > > > >
> > > > > Is this bug still present in Feisty Beta?
> > > > >
> > > > > --
> > > > > GRUB hangs on "please wait" on ASUS K8V-SE Deluxe
> > > > > https://bugs.launchpad.net/bugs/10535
> > > > > You received this bug notification because you are a direct
> > subscriber
> > > > > of the bug.
> > > > >
> > > >
> > > >
> > > > --
> > > > Angela Akridge
> > > > <email address hidden>
> > > > 408/393-9249 (cell)
> > > >
> > > > --
> > > > GRUB hangs on "please wait" on ASUS K8V-SE Deluxe
> > > > https://bugs.launchpad.net/bugs/10535
> > > > You received this bug notification because you are a direct subscriber
> >
> > > > of the bug.
> > > >
> > >
> >
> > --
> > GRUB hangs on "please wait" on ASUS K8V-SE Deluxe
> > https://bugs.launchpad.net/bugs/10535
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Angela Akridge
> <email address hidden>
> 408/393-9249 (cell)
>
> --
> GRUB hangs on "please wait" on ASUS K8V-SE Deluxe
> https://bugs.launchpad.net/bugs/10535
> You received this bug notification because you are a direct subscriber
> of the bug.
>