Home > Error 17 > Ubuntu Grub Error 18

Ubuntu Grub Error 18


share|improve this answer answered Jun 26 '12 at 23:00 psusi 26.8k13675 But he tried so many other CDs, and none of them would work. Reply With Quote « Previous Thread | Next Thread » Tags for this Thread boot, boot loader, grub, opensuse, problem View Tag Cloud Bookmarks Bookmarks Digg del.icio.us StumbleUpon Google Facebook Twitter Entering rescue mode... I thought I was almost there using the "Samsumg" software found on UBCD (Ultimate Bootable CD) - the lost HD was a Samsumg one. http://centralpedia.com/error-17/ubuntu-12-04-grub-error-17.html

After several Error 17 failures, the error changed to Error 18 - and this is the error it shows now. Bruni Jun 26 '12 at 22:21 add a comment| 4 Answers 4 active oldest votes up vote 3 down vote accepted From what you say, it doesn't sound like a problem I still cannot get my head around why NT can see the drives, and boot from the drives successfully, yet Grub cannot. It can't start, saying: Welcome to GRUB! https://ubuntuforums.org/showthread.php?t=1343458

Grub Error 17 Fix

Ubuntu Logo, Ubuntu and Canonical Canonical Ltd. Use the mailing list till I unfreeze it » Super Grub(2) Disk Support Boards » Super Grub(2) Disk (English) » Error 18 Grub loading please wait SMF 2.0.9 | SMF Maybe since it is still being actively developed :Grub 2 Basicshttp://ubuntuforums.org/showthread.php?t=1195275 Back to top #7 prillio prillio Topic Starter Members 8 posts OFFLINE Local time:05:58 PM Posted 29 April 2010 Register now!

  1. If instead of the recover command-line, I try to install the system, the same diskpart thing happens in the partition selection step.
  2. I've seen some pretty clogged-up laptops in my time. –Marty Fried Jun 26 '12 at 23:48 true, that would explain the fact that he can find the drives but
  3. Want to know if that peripheral is compatible with Linux?
  4. Re: Error 18 Grub loading please wait « Reply #1 on: 2009/09/28, 16:51:04 pm » Quote from: chef11994 on 2009/09/26, 18:06:40 pmWow I knew super grub existed but I just created
  5. Click Here to receive this Complete Guide absolutely free.
  6. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root

Probably means you need to edit the BIOS. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started But in this case, he has already tried currently supported versions, and has been unable to even boot the CD. Grub Loading Please Wait Error 17 Please visit this page to clear all LQ-related cookies.

Try to disable it in the BIOS or in the kernel. Grub Error 17 Android X86 User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. Make sure the disk size settings include *LBA* instead of *NORMAL* or something else, to get past the 1024 cylinder limit. http://www.linuxquestions.org/questions/linux-hardware-18/grub-loading-please-wait-error-18-a-343280/ Check if you have any BIOS update for the controller from the vendor site.

So hopefully nothing is wrong with it. Android Grub Loading Error 17 Arch Linux HomePackagesForumsWikiBugsAURDownload Index Rules Search Register Login You are not logged in. Username Forum Password I've forgotten my password Remember me This is not recommended for shared computers Sign in anonymously Don't add me to the active users list Privacy Policy

Regarding this question, I'm not entirely sure. –Aaron Jul 25 '09 at 16:35 add a comment| up vote 1 down vote Have you considered Super Grub?

Grub Error 17 Android X86

Thanks! http://arstechnica.com/civis/viewtopic.php?f=16&t=294358 It also looks like your drive may be failing. Grub Error 17 Fix Ok, booting the kernel Situation The system hangs after displaying the following line: Uncompressing Linux... Grub Loading Error 17 Windows 7 Use the mailing list till I unfreeze it » Super Grub(2) Disk Support Boards » Super Grub(2) Disk (English) » Error 18 Grub loading please wait « previous next » Print

Xel'naga666 View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Visit Xel'naga666's homepage! http://centralpedia.com/error-17/ubuntu-error-17-grub.html Advanced Search

Forum English Get Technical Help Here Install/Boot/Login Problems with GRUB Error 18 Welcome! alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. Windows works but Linux does not Is there another boot method other than Grub / Lilo that works in a different way (other than NTloader!)? Grub Loading Error 17 Android X86

It is also known that grub-0.94-r1 and grub-0.94-r2 should work correctly. All i did with opensuse 11.0 was run the dvd install and everything installed normally. What I would like to know is is this card to old to work with Debian 3.1? this contact form Intel mainboard P4 3.2GHZ running Debian 3.1.

Although the current GRUB ebuild filters out-fstack-protector, it can't hurt to recompile GRUB with clean CFLAGS if nothing else helps. Grub Loading Stage 1.5 Error 17 root #CFLAGS="-O2 -march=i686 -fomit-frame-pointer -pipe" emerge grub:0 --ask This problem appeared on a dell r320 server, caused by having serial and terminal options in grub.conf, problem disappeared after removing those options. Error 18 and it just sits at this screen Adv Reply December 3rd, 2009 #2 namok View Profile View Forum Posts Private Message Just Give Me the Beans!

And im doing the same thing on another lappy right now.....

If doing so would I still be able to reenable the Windows boot manager with fixboot/fixmbr? First boot ... Output a googol copies of a string Split python tuple in subtuples with capacity limit in functional programming style more hot questions question feed about us tour help blog chat data Grub Error 17 Windows 10 The error message you have obtained is purely related to the hard disk being used.

The installation ran to completion and the system booted up just fine. (By the way, a K6-III/450 with 384MB of RAM makes a pretty nice Ubuntu system.) Possible solutions: * make Check out bug #79378 for additional information. Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. navigate here They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro ## default grub root device ## e.g. Solution cyrillic provides information that it is possible to "map" the disks in a different order by changing grub.conf's Windows entry like so: FILE grub.confMapping diskstitle Windows XP map (hd0) (hd1) Also, hda5 is a fat32 partition because at the time I was writing back and forth from winXP and Linux (not now, lol) and I havent been able to change it

This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general). How to select citizen justices? I have one box with two complete xp partitions and one ubuntu partition on it. Had the message and figured it was a bad install so installed Slackware 10.1 had the same error.

Why don't miners get boiled to death at 4 km deep? My 21-year-old adult son hates me Instruments that don't require hand strength Why is C# Dim a Chord in B Minor? lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. It worked until 10.04, I think, but nothing seems to work with it now.

Registration is quick, simple and absolutely free. So when grub tries to get the required information, it fails because of corrupted sector in the hard disk. It installed fine, but after rebooting, I got that darned error message. Try an update for the BIOS and/or move the boot partition to the front (or at least into the appropriate range).

Be sure to check the root(x,y) settings in grub.conf. Even bytes get lonely for a little bit! share|improve this answer answered Jul 25 '09 at 13:54 Aaron 66321324 How could that help me? Posting in the Forums implies acceptance of the Terms and Conditions.

Find More Posts by Xel'naga666 10-26-2006, 04:34 AM #10 Xel'naga666 Member Registered: Sep 2005 Location: UK Distribution: Debian 4.0 Etch /Everywhere Posts: 51 Rep: Quote: Originally Posted by Folbo