Fedora 17 Grub Error File Not Found
Contents |
"error 15: file not found" live-usb asked 2012-07-11 12:01:05 +0000 Hutt 11 ●1 ●1 ●2 hello there, I am desperately trying to boot fedora 17 from a usb stick created from the gnome-live-cd. when I try to boot from error file '/grub/i386-pc/normal.mod' not found grub rescue the stick, I get "error 15 - file not found" in the boot loader. I error file /boot/grub/i386-pc/normal.mod not found entering rescue mode tried to create the live-usb with two different tools (linuxliveusb + liveusb creator) and I get the same error with both tools.I /boot/grub/i386-pc/boot.mod not found am creating the bootable stick from windows. The machine I am trying to get fedora installed is a netbook with an Intel Atom N2800 and 4GB RAM. burning a cd is unfortunately not an option because the lenovo grub rescue insmod normal file not found has no optical drive and I do not have an external optical drive. also, I do not have any linux machine at my hands. any suggestions on how to get it to work? edit retag flag offensive close merge delete Commentstry unetbootin and if that does not work then download the new isoAkshay( 2012-07-11 20:16:25 +0000 )edit 8 answers Sort by ยป oldest newest most voted 1 answered 2012-10-13 08:05:02 +0000 din 27 ●2 Here is
Grub Rescue Reboot
the solved Thread http://forums.fedoraforum.org/showthread.php?t=283055 edit flag offensive delete link more 1 answered 2012-10-12 10:34:42 +0000 winzter143 11 ●1 I encounter this problem just because I install the ISO to the partition as is /dev/sdb1 and not on the device /dev/sdb. ISO must install to device /dev/sdb try also to find here http://winzter143.blogspot.com/2012/10/how-to-create-live-fedora-on-usb-in.html edit flag offensive delete link more 0 answered 2012-09-06 15:58:12 +0000 Killswitch 1 Hello, yes I had this same problem last night while creating my live usb stick with fedora 17 and for me the solution was fairly more simple then some of these other solutions. I also used the fedora liveusb creator tool. My boot order was wrong in my bios. I had two options one being: USB KEY: {name of your usb drive} so for me: USB KEY: PATRIOT MEMORY and the other option was: UEFI: PATRIOT MEMORY I had accidentally set it to the UEFI (wrong) option rather than the USB KEY: (right) option that is the correct one to boot to. That stopped the error 15: file not found another small thing im not 100% sure about is my friend who did this same thing told me to create my bootable usb stick on usb 2.0 rather than 3.0. Not sure if that would make a difference. We both created our usb drives inside of windows 7 using liv
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
/boot/grub/i386-pc/normal.mod Not Found Windows
hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask /boot/grub/i386-pc/normal.mod not found mint Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join /boot/grub/x86_64-efi/normal.mod not found them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Grub error: file '/grub/i386-pc/normal.mod' not found? up vote 4 https://ask.fedoraproject.org/en/question/8129/fedora-17-live-usb-boot-error-error-15-file-not-found/ down vote favorite 2 I recently install arch (hopefully successfully) on my machine. When I went to reboot however I had a problem. I got a black screen with text saying Grub loading. Welcome to GRUB! error: file '/grub/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> I have since googled looking for an answer. I almost found one here on the Ubuntu forums yet then I saw one of the comments saying it was untrue. There is also another answer http://unix.stackexchange.com/questions/70538/grub-error-file-grub-i386-pc-normal-mod-not-found but I'm not sure if I want to install from the live CD for fear of messing things up. You would understand my fear if you too spent 7 hours setting this up after constantly running into partitioning, command, tutorial, and system problems. What a joy. Anyone know of an easy solution to getting grub working? grub2 share|improve this question edited Dec 26 '13 at 20:57 hildred 3,68811233 asked Mar 29 '13 at 17:59 Griffin 1981413 The second suggestion (with the liveCD and chroot) is probably worth trying. Or a variation on it: I'm not an arch user but have installed it before, and from what I remember, you might want to contemplate that suggestion in relation to the various stages of installing arch, some of which involve a chroot. If you can backtrack to a previous step booting the arch CD and then mounting and chrooting into your installation, you should be able to try grub-install. You don't have to repeat any of the steps, just use them as a guide to get chrooted in from a liveCD. –goldilocks Mar 29 '13 at 19:26 While I'm not at the computer right now I do believe I tried the grub install and it didn't work.- –Griffin Mar 29 '13 at 19:34 @Griffin It didn't work as in "grub-install" failed, or it didn't fix the problem? –derobert Mar 29 '13 at 20:09
years ago Last modified 23 months ago F18 - file not found -/isolinux/vmlinuz0 Reported by: jantman Owned by: lmacken Priority: major Milestone: __unclassified__ Component: fixed_in_git Version: Keywords: https://fedorahosted.org/liveusb-creator/ticket/810 Cc: Blocked By: Blocking: Description I've created a USB flash drive of Fedora 18 KDE using liveusb-creator 3.11.7 on Fedora 17. My intended target is a https://wiki.gentoo.org/wiki/GRUB_Error_Reference mid-2010 MacBook? Pro 6,2, booting via EFI with the rEFInd boot manager. I can boot to grub 2.0, but once I select "Fedora-18-x86_64-Live-KDE.iso", I get not found the following error message: error: file `/isolinux/vmlinuz0` not found. error: you need to load the kernel first. Press any key to continue... if I mount the created image, I can verify that there is, in fact, no /isolinux directory on disk. There is, however, a /syslinux directory. Making the following /boot/grub/i386-pc/normal.mod not found change to /EFI/BOOT/grub.cfg (after first chmod u+w'ing it) allows the Fedora installer to boot: --- grub.cfg.orig 2013-01-17 10:57:41.267566185 -0500 +++ grub.cfg.new 2013-01-17 11:00:15.716646259 -0500 @@ -22,10 +22,10 @@ ### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora-18-x86_64-Live-KDE.iso' --class fedora --class gnu-linux --class gnu --class os { - linuxefi /isolinux/vmlinuz0 root=live:LABEL=Fedora-18-x86_64-Live-KDE.iso ro rd.live.image quiet rhgb - initrdefi /isolinux/initrd0.img + linuxefi /syslinux/vmlinuz0 root=live:LABEL=Fedora-18-x86_64-Live-KDE.iso ro rd.live.image quiet rhgb + initrdefi /syslinux/initrd0.img } menuentry 'Verify and Boot Fedora-18-x86_64-Live-KDE.iso' --class fedora --class gnu-linux --class gnu --class os { - linuxefi /isolinux/vmlinuz0 root=live:LABEL=Fedora-18-x86_64-Live-KDE.iso ro rd.live.image quiet rhgb rd.live.check - initrdefi /isolinux/initrd0.img + linuxefi /syslinux/vmlinuz0 root=live:LABEL=Fedora-18-x86_64-Live-KDE.iso ro rd.live.image quiet rhgb rd.live.check + initrdefi /syslinux/initrd0.img } Change History comment:1 Changed 4 years ago by jantman There's also an issue with the disk label being changed to LIVE. Updated diff for grub.conf: --- grub.cfg.orig 2013-01-17 10:57:41.267566185 -0500 +++ grub.cfg.newest 2013-01-17 11:37:58.561167111 -0500 @@ -22,10 +22,10 @@ ### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora-18-x86_64-Live-KDE.is
systemHardwareSoftwareDesktopServer & SecurityProject & Community Tools What links hereRelated changesSpecial pagesPrintable versionPermanent linkPage informationBrowse properties User Create accountLog in Toggle navigation PageDiscussion View source more History GRUB Error Reference From Gentoo Wiki Jump to: navigation, search The objective of this article is to list problems and errors that may occur in certain situations when using the GRUB Legacy bootloader. All these solutions have been acquired through the cooperation of users on the Gentoo Forums. Contents 1 Starting notes 1.1 Acknowledgements 1.2 Disclaimer warning 2 GRUB loading, please wait... 2.1 Situation 2.2 Solution 3 GRUB Error 12 3.1 Situation 3.2 Solution 4 GRUB error 15 4.1 Situation 4.2 Solution - Initial configuration 4.3 Solution - Booting an entry 5 GRUB error 17 5.1 Situation 5.2 Solution 6 GRUB error 18 6.1 Situation 6.2 Solution 7 GRUB GRUB GRUB GRUB GRUB ... 7.1 Situation 7.2 Solution 8 Probing devices to guess BIOS drives. This may take a long time 8.1 Situation 8.2 Solution 9 When installing GRUB, it just hangs 9.1 Situation 9.2 Solution 10 Uncompressing Linux... Ok, booting the kernel 10.1 Situation 10.2 Solution 11 GRUB just shows a GRUB prompt 11.1 Situation 11.2 Solution 12 Could not find device for /boot/boot: not found or not a block device 12.1 Situation 12.2 Solution 13 The system reboots after hitting return at the GRUB menu 13.1 Situation 13.2 Solution 14 After hitting the Enter (Return) key at the GRUB menu, the screen blanks out 14.1 Situation 14.2 Solution 15 Missing GRUB image 15.1 Situation 15.2 Solution 16 Failing To boot Windows from a second hard drive 16.1 Situation 16.2 Solution 17 GRUB segfaults when trying to install 17.1 Situation 17.2 Solution Starting notes Acknowledgements Many thanks to Earthwings, penetrode, loyaltonone, pilla, airhead, nephros, yamakawa and all the others for the suggestions on the original thread. Disclaimer warning The examples provided are just examples. Be sure to change partition numbers and the like according to the specific systems specs. Follow the solutions provided by this document at the readers own risk. GRUB loading, please wait... Situation GRUB loading stage 1.5 GRUB loading, please