GRUB hangs on "please wait" on ASUS K8V-SE Deluxe

I got the same problem.
I install Ubuntu and when I reboot I got "Grub Loading, please wait", and the
system stops.... :(
Have no idea about what is happening...

I try to install LILO during the instalation but it didn't work to.

I have an fat32 partition with winxp and a ntfs hd for backup. I did the auto
partition with the remaining space.

My computer:
ASUS p4c800 deluxe
p4 2400 ht
maxtor 6Y080L0
AMIBIOS
  Version: 08.00.09
  Build Date: 02/23/04
  ID: P4C81102

Any idea about what's happening?

Can I install another GRUB version from a floppy disk? I don't know how to do
that...

I have this same problem with Hoary (daily installer build 1/22/05 -- Warty does
not exhibit this issue for me). First stage installation goes fine and grub
install seems to proceed successfully with no errors (in fact after the grub
install process, I executed a shell and confirmed that
/target/boot/grub/menu.lst appeared normal). Upon the reboot to the second
stage, grub hangs with "Loading Stage 1.5".

Just installed on a msi neo2 board, and have the same problem, booted from cd,
activated my lvm2 partitions, mounted em in, ran grub and did:

root (hd0,0)
setup (hd0)
to see if that would help, the setup (hd0,0) caused a segfault in grub.

replying to myself as I figured out strace was in the default install.

the only interesting thing I can make out before the segfault is _llseek with
error ptrace:umoven input/output error.

> Just installed on a msi neo2 board, and have the same problem, booted from cd,
> activated my lvm2 partitions, mounted em in, ran grub and did:
>
> root (hd0,0)
> setup (hd0)
> to see if that would help, the setup (hd0,0) caused a segfault in grub.

(In reply to comment #3)
> Just installed on a msi neo2 board, and have the same problem, booted from cd,
> activated my lvm2 partitions, mounted em in, ran grub and did:
>
> root (hd0,0)
> setup (hd0)
> to see if that would help, the setup (hd0,0) caused a segfault in grub.

This and comment #2 are a different bug from that which was originally reported.
Please move discussion of them to bug #13156.

(In reply to comment #5)
> Please move discussion of them to bug #13156.

Sorry, make that bug #12459.

grub and lilo failed on my ASUS A8N SLI DELUXE. I have 3 disk drives, 80G as sda another identical 80G as sdb and a 300G as sdc, all of them are seagate disks. Installation of the boot loaders failed till I removed the 300G. What happend was that the Linux kernel read sda b c in the correct order, like the BIOS did, but grub and lilo read the 300G as sda. After inserting the 300G the problem didnt reoccur, so once the installation was successfull, the problem went away.

I also have an ASUS K8V-SE deluxe and having issues with the drives. If the motherboard/bios boots too fast into grub and I pick a ubuntu kernel, it will lock grub up at booting it. If I try again it works or if I wait for the timer to go down and boot it works. I think it's just a buggy motherboard which can't decide which drive should be default. I am running the latest stable bios flash as well.

If I have a usb drive plugged in it will replace sata default drives with pata ones, etc. and totally confuse grub.

Another issue that I will put in another bug report is my 200gb /dev/hdb1 ext3 pata is getting trashed by ubuntu for some odd reason.

I begin to be confused, so I take this bug on me the time to see if we can clarify things.

Kristof: Are you still there, any news?

Mistaed: "will lock grub at booting it", on the "Grub Loading, please wait" message?

Iwan: (about order of detection): By grub failed, I guess you was not blocking on "Grub Loading, please wait"? My Guess: Error 22.

If you are mixing sata and ide disk drives, then yes, grub assumes that the ide drive is your boot drive. If that is not the case, you need to tell grub that by editing /boot/grub/device.map, then reinstall grub. Alternatively you can go into your bios and make the ide drive the boot drive, then (re)install.

Also are any of you using the sata raid feature on that motherboard?

Oh, and Anders: your /boot partition is not an LVM volume is it? It should be the first primary partition on your first disk based on your grub command. Grub can not access LVM partitions so /boot must be a normal partition.

I'm going to try to forward this upstream.

Cheers,
Matt

Oops, wrong bug, my mistake.

Sorry,
Matt

I have the same problem on an ASUS M2N8-VMX motherboard.
After installation I could reach the boot menu occasionally, but most of the times it hang on
GRUB loading, please wait
for a while, about 20 s, then it enters the grub shell, where it
occasionally worked with a "reboot" but most of the times not.
This problem was noticed with grub 0.97.
The installation CD (6.06) booted flawlessly (ok had to
add noapic usb-handoff to not hang later)

To fix the grub hanging I copied grub 0.95 from another
64-bit machine (running debian sarge)
/lib/grub/x86_64-pc/*
/sbin/grub*
and reinstalled grub, then it worked.
Strange, however, is that it still takes a very long time (about 20 s) from "GRUB loading, please wait" until I get the boot menu. On other machines where I'm running grub I get the boot menu immediately.

/Roland

I too experienced this problem, except that I'm running Vista. I can't boot now. I just receive the GRUB please wait... error. I chose to install Ubuntu because it's the os "for human beings." Well, I guess technical human beings. I don't have the knowledge to fix the problem.

Is this bug still present in Feisty Beta?

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.

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)

Thank you for your quick response! Currently we have thousands of users who use Ubuntu alongside almost any version of windows you can think of. As we cannot confirm this bug in Feisty, I am going to mark it closed. Please open a new bug if new information is present.

> I'll stick with my Windows, thank you
Thanks for giving us a try, hopefully when you try again things will work as you expect. Each release we strive to make a better product, and a more compatible product.

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.
>

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.
> >
>

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 smo...

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 ...

Iwan,

Can you confirm that it won't boot with your 300G drive on feisty?

Yes, I did a dist-upgrade to Feisty.

It was not a clean install but it did not work. It could be due to me
running raid these days. From hoary to dapper to edgy I did not run
raid and the install did not work with the 300G. During edgy I
switched to software raid. I think the latest problem is more to do
with mdadm not working properly. During the dist-upgrade I tried once
with the 300G attached and once without as I did not have a writable
CD handy. I plan to do a clean install the 19th when Feisty is
released, and would follow a plan of installing and reporting
debugging information if you give me instructions. I don't want to
lose customizations and so on at later stages by reinstalling over and
over.

On 4/4/07, Steven Harms <email address hidden> wrote:
> Iwan,
>
> Can you confirm that it won't boot with your 300G drive on feisty?
>
> --
> 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.
>

I use to install on to a 80G. Sinec the raid I install /boot on to a
1G partition. I use the 300G to store media and to backup my 160G
non-redundant raid.

This is df -h

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 149952404 128583056 21369348 86% /
varrun 513440 164 513276 1% /var/run
varlock 513440 4 513436 1% /var/lock
procbususb 10240 164 10076 2% /proc/bus/usb
udev 10240 164 10076 2% /dev
devshm 513440 0 513440 0% /dev/shm
lrm 513440 20844 492596 5%
/lib/modules/2.6.17-10-generic/volatile
/dev/sdb1 918322 25740 843586 3% /boot
/dev/sdc1 918322 16463 852863 2% /media/sdb1
/dev/sda1 288435200 280238160 8197040 98% /mnt/01

Hard disk space - the final frontier.

I just rebooted to confirm that the BIOS reads the 300G as the 3rd
disk. Linux sees it as the first sata disk. /dev/sda1

So I think that is were the confusion comes in. during installation it
might detect it in the correct order, during the bootup to the
installed system it does not see it in the same order. Either way, the
order is wrong. I think the new
UUID=f8522cbc-a18c-49f9-bda5-6d1e6624ae51 thing should fix it but it
doesn't. I don't know much about IT since I'm an accountant. :-)

Changing status on Debian to match Ubuntu.

For confidentiality reasons, can you please remove my name from the 2007-02-12 post? You guys now know I'm not a troll. ;) Please. It's appearing in Google hits. At least remove my last name. Thank you.