Grub Error 17 No Cd Drive
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads grub error 17 android x86 with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question
Fix Grub Error 17
and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask grub error 17 windows 7 a question Anybody can answer The best answers are voted up and rise to the top How to fix “GRUB error 17” problem on laptop without working CD reader up vote 1 down vote favorite I broke the laptop. How did I
Grub Loading Please Wait Error 17
break it? I remember feeling happy about wubi. Now I feel bad about wubi and everything that I did. I used the partition editor within Windows (System Tools - administration) and removed my 11 GB partition of ubuntu. This was how my laptop has been partitioned EVER since I dual booted it three or so years ago. Now. This is what my LCD says:
GRUB 1.5 Loading GRUB Error 17I shall fix my laptop next weekend, when I have time. grub error 17 windows 10 I actually don't know if I should fix the CD, or try booting from a USB (Damn small linux on USB seems to run then it went blank as well), or get the hard drive swapped out, install linux through a computer which has a working CD Drive, re-insert it into the computer. Any suggestions? I want the easiest answers. linux laptop grub ubuntu-8.04 wubi share|improve this question asked Oct 29 '08 at 3:29 colemakker migrated from stackoverflow.com Sep 8 '12 at 9:59 This question came from our site for professional and enthusiast programmers. add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted If you have a Windows install CD, try booting recovery with that -- there should be some way of restoring the MBR, which will get you back to a booting Windows system for now. Wondering why you deleted the Linux partition, though? If you were planning on re-installing, you should have just done that and skipped the delete part. share|improve this answer answered Oct 29 '08 at 4:09 ephemient 14.6k31919 i was sleepy and didn't know what i was doing until i realized what i had done. too excited i guess.. i screwed init.d by deleting it (sudo rm /etc/init.d/apache2 ., which then led me to trying installing wubi.. then realized my Boot mbr would crash.. i guess will try super grub disk or rip linux –colemakker Oct 29 '08 at 5:42 add a comment| up vote 2 down
2008, 09:35 AMInstallation to USB stick works fine but I can't start Ubuntu from stick because the Grub error 17. The error appears before I can do anything
Grub Loading Error 17 Android X86
with Grub. I have even tried the Pendrivelinux way: http://www.pendrivelinux.com/2008/10/15/ubuntu-810-persistent-flash-drive-install-from-live-cd/ with same error. All
Grub Loading Stage 1.5 Error 17
3 computers report the Grub error 17 so something simple must be wrong. Before in this USB stick I hade Ubuntu 8.04 android grub loading error 17 installed as an real harddrive but I can't find the howto to install Ubuntu in that way. bobnutfieldNovember 17th, 2008, 09:48 AMI would recommend using UNETBOOTIN (http://lubi.sourceforge.net/unetbootin.html) It is a GUI makes installing to a http://superuser.com/questions/471633/how-to-fix-grub-error-17-problem-on-laptop-without-working-cd-reader USB stick a snap. C.S.CameronNovember 17th, 2008, 05:34 PMUsb-creator always seems to work for me after deleting the files from a Unetbootin install. Or if you wish you can make a Unetbootin install persistent. You can do a Full install to flash drive using the same method as to internal HDD. Boot from Live CD or Live USB and click install on the desktop. (I suggest disabling your internal HDD first https://ubuntuforums.org/archive/index.php/t-984869.html so you don't mess up it's MBR). When you get to partitioning you can choose any of the three methods, use full disk, use remaining space or manual. If you use remaining space or manual you can leave a little FAT32, (on the left side), so windows can see the flash drive. For manual partitioning on a 4G drive, (minimum), 500 MB FAT32, 1 GB /home and 2.5 GB root, (/), is a good starting point and can be adjusted later using gparted. Home and root can be formatted as ext3 or reiserfs. This should make a flash drive that works just like a HDD install only a little slower at times. aureliengNovember 17th, 2008, 07:20 PMThat's funny: I did the same thing today, and have the same "Grub error 17" message upon boot. @C.S.Cameron, I followed the procedure you decribed in your post: 1. unplug the internal hard disk for safety 2. boot on the liveCD (8.04.1, I want LTS) 3. partition the USB stick as follow: Disk /dev/sde: 8086 MB, 8086618112 bytes 255 heads, 63 sectors/track, 983 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000ec711 Device Boot Start End Blocks Id System /dev/sde1 1 92 738958+ b W95 FAT32 /dev/sde2 * 585 983 3204967+
Home Linux distributions Linux tutorials News Frequently Asked Questions Opensource Unix Ask/unixmen Home Linux tutorials Fixing a few common grub errors | Broken Bootloader and error 17/15 Fixing a few common grub errors | Broken Bootloader and error 17/15 By M.el Khamlichi Share on https://www.unixmen.com/fixing-a-few-common-grub-errors-broken-bootloader-and-error-1715/ Facebook Tweet on Twitter tweet Grub is short for GNU GRand Unified Bootloader. To be simply put, it’s a boot loader package from the GNU Linux project. It’s the common and reference implementation of a multiboot http://iknowkungfoo.com/blog/index.cfm/2008/6/16/Stupid-solution-for-Grub-error-17 Linux system. It allows you to choose which operating system or specific kernel to boot into.In this article, we’ll be looking into figuring out some common grub errors and hopefully, work out a fix for them. error 17 Repairing a broken Grub 2 bootloader: There are tons of us here who broke their grub thanks to autoupdates through apt or similar. Hopefully, this will allow them an way to fix their system without reinstall.Grub now features an advanced rescue mode, truly a godsend for people who somehow messed their MBR tables up.You want to trigger that and get into grub. Then execute the commands below to get back into an working grub error 17 desktop first.lsset prefix=(hdX,Y)/boot/grubset root=(hdX,Y)setls /bootinsmod /boot/grub/linux.modlinux /vmlinuz root=/dev/sdXY roinitrd /initrd.imgboot The X and Ys are to be filled in with your own HDD information. If you only have one HDD, it’ll be X=0, Y=1 and so on. At this point, you should atleast be able to boot up normally. You’re almost done. sudo update-grub sudo grub-install /dev/sdX Execute those two commands, replacing X with the partition your linux is installed on. For me, it was ‘a’. Voila! You’ve fixed your broken ‘auto-updated’ MBR records. Fixing grub error 17/15 Grub error 17 is one of the most common error messages that you’re likely to encounter using the Grub bootloader. The root cause behind it is a messed up partition table disk order.To fix this, grab a live cd and boot into your desktop.Execute the following: sudo fdisk –l You’re likely to get something like the following: Disk /dev/sdb: 750.1 GB, 750156374016 bytes255 heads, 63 sectors/track, 91201 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x000dc2a4 Device Boot Start End Blocks Id System/dev/sdb1 1 1275 10238976+ fd Linux raid autodetect/dev/sdb2 1275 91074 721306624 fd Linux raid autodetect/dev/sdb3 91074 91201 1022976 82 Linux swap / Solaris Partition table entries are not in disk orderIf the bolded line exists, you’ve just found your problem.Fixing this is ea
had it install Grub so I could boot between the two. After playing games on Vista, I rebooted to do some work in Ubuntu. The machine wouldn't boot due to Grub error 17, but after doing something stupid it booted just fine. The ProblemSo, I tell Vista to restart so I can load up Ubuntu. When I should get the Grub menu that lets me choose between Vista and Ubuntu, instead I got this error message: view plain copy to clipboard print about ColdFISH is developed by Jason Delmore. Source code and license information available at coldfish.riaforge.org GRUB Loading stage1.5GRUB loading, please wait . . .Error 17 1GRUB Loading stage1.523GRUB loading, please wait . . .4Error 17Possible SolutionsI hit up Google as usual and found this post on the Ubuntu forums that explains how to change some settings in the BIOS to fix the error. Then I found this post that explains how to reinstall Grub from a Live CD to fix the error.I booted up the Ubuntu Live CD, getting ready to reinstall Grub (2nd link). Something oddWhen the Live CD loaded, I noticed my external USB hard drive was mounted on the desktop. I remembered one this post from the 1st link:"In my case, I have three SATA hard disks.
My BIOS sees them as: HDD1 - 80 GB - Windows HDD2 - 80 GB - Linux HDD3 - 250 GB - MediaLinux sees them as: /dev/sda - 80 GB - Windows /dev/sdb - 250 GB - Media /dev/sdc - 80 GB - LinuxSo it generated device.map assuming that order was correct, i.e.: (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdcWhen the installer installed GRUB using that data, it tried to install the first part of GRUB on /dev/sda and told it to look for the OS on /dev/sdc. Unfortunately, this translated to "install on (hd0) then look for the OS on (hd2)", so it was looking for the OS on the wrong drive."So one cause of Grub error 17 is the order in which Linux mounts hard drives vs. the mount point where Grub expects to find Linux.The Stupid SolutionI unmounted the external hard drive, then turned it off. I rebooted the computer and a few seconds later BAM! there's the Grub Menu. Views: 64096 | Comments: 7 | Print | Comments (Comment Moderation is enabled. Your comment will not appear until approved.) [Add Comment] [Subscribe to Comments] #1 by Eric Knipp on 6/16/08 - 3:53 PM This reminds me of my difficulties installing Ubuntu off of a DVD+RW. Turns out CD-ROM drives are not able to read DVD's. #2 by Bill on 7/3/08 - 5:20 PM Although your comment doesn't have me up and running yet, it does give me a little deeper understanding of the problem I'm up against.Thanks #3