UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm new here so I'm just trying to get an older version of ubuntu up.
I have run the install to the end, rebooted and came up with 'GRUB Loading, Please wait... Error 17.
I just followed the default settings; I hope I didn't miss anything.
This went onto a slave drive (which has XP) beside the master which has 98. It looks like all the partitioning went ok (to me, anyway) but when I rebooted it came up with that statement and hung.
Thanks. mmm. Maybe there's a better one to try out the Linux type system.
I ran into this problem, and while I am not 100% on what of the things I did was the actual fix, here is a list of things I had to do:
1)I re-installed ~3 times trying to get grub into the MBR correctly, which wasn't the correct solution and ultimately I ended up unplugging the HDD's I wasn't using to get Ubuntu to boot. The first master is a SATA drive with the slave on IDE, which may have had something to do with it. After I plugged my extra HDD's back in, I got the error message again.
2)Made sure the BIOS saw the drive with Ubuntu as the primary boot device.
3)Tried to run the grub install from the Ubuntu live cd, following some commands from my Linux Cookbook.
4)Finally I installed XP on the extra HDD in order to play games, which blew away the MBR, then I re-ran the grub installation from the live cd, made sure it booted Ubuntu and edited the menu.lst file to include the XP drive and now everything's good.
Hope some of this rambling may have helped. Like I said, not sure what actually fixed the problem but I'm pretty sure it was the MBR being hosed that caused it all as I was able to boot fine with only 1 HDD plugged in.