Puppy Linux Grub Error 18
Contents |
times are UTC - 4 Forum index »House Training »Beginners Help ( Start Here) GRUB Error 18 Moderators:Flash, Ian, JohnMurga View previous topic :: View next topic Page 1 of 1[3 Posts] Author Message r_e_h Joined: 16 Dec 2010Posts: 18Location: Muville error 15 file not found grub Posted: Sun 19 Dec 2010, 23:21 Post subject: GRUB Error 18Subject description: a thread of
How To Install Puppy Linux To Hard Drive From Usb
solutions Now I'm not being a control freak here and I'm not your mother. But I have an idea for a signal-only
Error 15 File Not Found Linux Redhat
thread with no noise. If you have had Grub Error 18 on boot AND fixed it, then -- IF YOUR FIX IS DIFFERENT FROM THOSE ALREADY HERE -- add it. If you only have a comment and it's on-topic,
Error 15 File Not Found Centos
do a Quote on the solution you are talking about and add your bit. If it's off-topic noise you want to make, go shout it down a hole. ;-) This would leave us with a list of annotated solutions, non? I'm not going to worry about whether ya'll go along with this idea. But if it flies, this would be a good resource for fixing that problem and a new kind of thread that could be used from error 15 file not found windows 7 time to time in the forum. just an idea. I'll follow this post with my own recent solution. Last edited by r_e_h on Sun 19 Dec 2010, 23:23; edited 1 time in total Back to top r_e_h Joined: 16 Dec 2010Posts: 18Location: Muville Posted: Sun 19 Dec 2010, 23:23 Post subject: Fixed error with grub4dosSubject description: This is on a linux-only box My goal was to have a Linux only box. I was hoping for Puppy-only but that didn't work out. But this is a solution for Linux only and not a Windows box that also has linux I tried installing Puppy 511 with the Universal Installer, both frugal and full installs. Both gave Grub Error 18 when booted, saying the cylinder was too big for the BIOS. So I found a dist that would install from a Live CD and boot from Grub. The one that worked for me was Debris Linux. This way I knew the box was OK and Grub was OK. So I just needed to get Puppy to work. The solution I found, with help from Puppy's forum, was this: 1. I downloaded and unpacked grub4dos from sourceforge.net 2. I su'd to root and copied grub4dos.exe to / 3. In the same terminal I soft-linked menu.lst in / -- ln -s /boot/grub/menu.lst 4. I opened menu.lst in an editor and made the following entries
GRUB (Grand Unified Bootloader) GRUB is a BootLoader. Within Puppy Linux GRUB may be installed onto any partition using: Menu > System > Grub /boot/grub/menu.lst This file should contain entries similar to these: # grub error 15 For booting GNU/Linux on /dev/sda1 (H.D.D. primary partition) title Puppy Linux rootnotify (hd0,0) kernel error 15 file not found grub windows 7 (hd0,0)/vmlinuz pmedia=idehd initrd (hd0,0)/initrd.gz # For booting GNU/Linux on /dev/sda1 (U.S.B. flash drive partition) title Puppy Linux rootnotify (hd0,0) kernel (hd0,0)/vmlinuz error 15 file not found press any key to continue pmedia=usbflash initrd (hd0,0)/initrd.gz Error 2: Bad file or directory type thread References Can I install Puppy on HDD but boot from USB thumbdrive? Appendix When the GRUB menu comes up, press 'c' to go to http://www.murga-linux.com/puppy/viewtopic.php?t=63172&sid=6ed84aa25535b3051ad860ac8dbdd20e a command line. Type 'find /vmlinuz' and 'find /initrd.gz' This will tell you where GRUB thinks the files are. GRUB GRand Unified Bootloader, a multiboot bootloader that is easy to install and configure. It can boot from the Master Boot Record on a hard drive or from a CD. Especially easy to set up for Puppy. http://wiki.linuxquestions.org/wiki/GRUB To learn about the GNU GRUB project, please see: http://www.gnu.org/software/grub/ The manual for "legacy" http://puppylinux.org/wikka/GRUB GRUB, including 0.96 installable from Puppy installer, please see: http://www.gnu.org/software/grub/manual/ GRUB (short for GRand Unified Boot Loader) is a boot loader, similar in overall function to LILO. It is the standard way to boot into an operating system (or several) used by most recent Linux distributions, but capable of being loaded on any Linux distro. Go here for a comparison of Lilo & Grub, written by Laurence Bonney (IBM). From TheBabbs - I run Puppy Linux 1.0.6 (soon to be 1.0.7) and Fedora Core 3 on the same desktop machine. Each has its own partition on different drives. When I first added Puppy Linux to this system, I had the hardest time configuring the GRUB install which Fedora had previously installed. It was not until someone provided me a sample configuration that I was able to hack "/boot/grub/grub.conf" to add an option to choose which Linux I wanted to use. In light of that, here is what I presently have in my grub.conf file: # grub.conf # default=0 fallback=1 timeout=5 splashimage=(hd1,0)/grub/splash.xpm.gz hiddenmenu password --md5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx title Puppy Linux (1.0.6) rootnoverify (hd0,0) kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 title Fedora Core (2.6.11-1.35_FC3) root (hd1,0) kernel /vmlinuz-2.6.11-1.35_FC3 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.11-1.35_FC3.img MBR Solving problems with if grub is more or less working, you sho
wrote in message news:49954849$0$2514$... > > > rootnoverify (hd0,9) gives me error 18. > I did of course mean: rootnoverify (hd1,9) Dave davesurrey, Feb 13, 2009 #21 Advertisements davesurrey Guest "Daniel James" <> wrote in http://www.techiehq.net/threads/grub-error-18.23256/page-2 message news:... > In article news:<49942035$0$16176$>, Davesurrey > wrote: >> I did post the result of fdisk which may help a lot. > > Yes, I've just seen it. > >> Think you mean sdb4 here rather than sdb5. >> Or have I mis-understood. > > My fault. I actually meant to type sdb2 (sdb5 was a thinko on my part) > because I thought the EXTEND partition would be the second partition in > the MBR, but I see now error 15 that you actually have three primary data > partitions in there and that the EXTEND partition is sdb4 (as you say). > > Sorry for any confusion there. > >> Understand but I have since added an sdb13 and it worked just fine. >> So doubt any limit is causing this. > > There's clearly no /physical/ limit, or you wouldn't be able to create > the partitions in the first place. > > The error message you're getting, though: error 15 file > > "Error 18: Selected cylinder exceeds maximum supported by BIOS." > > is one that suggests that something (presumably grub) is trying to read > the disk using CHS addressing (that is: telling the BIOS a head number, > cylinder number, and sector number to read, rather than just a logical > block number from the start of the disk -- that's the only way that > "selected cylinder" makes any sense). > > The problem with CHS is that the way the head number, cylinder number, > and sector number are passed to the BIOS limits the values that are > passed. The sector number must be 1..63, the head number must be > 0..255, and the cylinder number must be 0..1023 -- which is where the > 8GB limit comes from. Back in the dawn of time when hard drives were > only around 10MB or 20MB in size those CHS numbers represented the > actual position of a sector on the disk ... a disk with 4 heads and 16 > sectors per track gave 32k bytes per track, so 20MB used 640 tracks. > > Modern disks lie about the number of heads (fdisk thinks your disk has > 255 -- the maximum that can be addressed using CHS -- but it probably > only has 2 or 4) and the number of sectors per track (fdisk thinks > yours has 63 -- again, t