From forum thread http://forums.gentoo.org/viewtopic.php?t=122656 Due to request I've started passing to XML the above error collection, expect to have something in a week's time. Hope Sven is not away for holidays! ;) Reproducible: Always Steps to Reproduce:
I'm not :) If you are going to copy/paste a huge amount of a certain posting (not only bits and bytes here and there), you should contact the author for permission on using this in a document. If you however going to interprete already-public-domain information, then there is no problem at all.
And? Any progress on this? The thread gets larger and larger :)
Sorry, I won't be able to accomplish any requests on existing bugs (that goes for Mr. Bones too) until 28 January. I'm currently under exams period.
So, how where your finals? :)
Exams fine... Tomorrow morning all get on it ok? Expect it ;)
Created attachment 50556 [details] The Grub Error Collection This is the Gentoo GRUB Error Collection. Enjoy :)
Please, replace the reviewer 'idoneus' with 'Hartwig Brandl'. Hartwig Brandl asked his email address to not be publicly displayed.
Ioannis, I notice that the license you use isn't the CC-BY-SA license. At Gentoo, only new documentation using that particular license is accepted. We don't want to start with a pool of several licenses, it makes juridical consequences harder. What is the reason you choose PDL 1.0? Is it your own choice or is it due to a third party?
Doh, sorry Sven, I thought PDL was ok. Change license to CC-BY-SA. Auth granted :) [I do not care much about the license of the doc, to be said.]
Hartwig Brandl, is it ok for you?
Sure, CC-BY-SA is alright.
Comment on attachment 50556 [details] The Grub Error Collection ><?xml version='1.0' encoding="UTF-8"?> ><!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> > ><guide link="/doc/en/grub-error-collection.xml"> ><title>Gentoo Grub Error Collection</title> > ><author title="Thread Reviewer"> > <mail>Hartwig Brandl</mail> ></author> > ><author title="Editor"> > <mail link="deathwing00@forums.gentoo.org">Ioannis Aslanidis</mail> ></author> > ><abstract> >The objective of this error collection is to solve the most frequent (and >also less frequent) problems and errors that could show up when using and >configuring the GRUB bootloader. All these solutions have been achieved >through the cooperation of many users of Gentoo Forums. The original thread >of this document can be found ><uri link="http://forums.gentoo.org/viewtopic.php?t=122656">here</uri>. ></abstract> > ><license>CC-BY-SA</license> > ><version>1.3</version> ><date>2005-02-06</date> > ><chapter> ><title>Starting notes</title> > ><section> ><title>Acknowledgements</title> ><body> ><p> >Many thanks to Earthwings, penetrode, loyaltonone, pilla, airhead, nephros, >yamakawa and all the others for the suggestions on the ><uri link="http://forums.gentoo.org/viewtopic.php?t=122656">thread</uri>. ></p> ></body> ></section> > ><section> ><title>Disclaimer warning</title> ><body> > ><p> >The examples provided are just examples. Be sure to change partition numbers >and the like according to your systems specs. Follow the solutions provided >by this document at your own risk. ></p> > ></body> ></section> ></chapter> > ><chapter> ><title>The Grub Error Collection</title> > ><section> ><title>Grub loading, please wait...</title> ><body> ><p> >When rebooting you get this message and then grub hangs? But booting of your >grub floppy works fine? ></p> ><pre> >GRUB loading stage 1.5 >GRUB loading, please wait... ></pre> ><p> >According to <c>the_bell</c> you should change the boot order in your BIOS. >Tell your BIOS to not boot first your floppy. ><c>penetrode</c> wrote that this may also be due to bad CFLAGS settings. >Although the current grub ebuild filters out -fstack-protector it can't hurt >to recompile grub without CFALGS if nothing else helps. ></p> ><pre> ># CFALGS="" emerge grub ></pre> ></body> ></section> > ><section> ><title>Grub error 12</title> ><body> ><pre> >12 : Invalid device requested This error is returned if a device string is >recognizable but does not fall under the other device errors. ></pre> ><p> >Did you execute the two lines below in the grub prompt? ></p> ><pre> >grub> root (hd0,0) >grub> setup (hd0) ></pre> ><comment> >(hd0,0) must be replaced with your boot partition and (hd0) with the HDD >you have chosen. Remember that (hd0) will install the bootloader in the >Master Boot Record of the HDD 0, aka Primary Master. ></comment> ></body> ></section> > ><section> ><title>Grub error 15</title> ><body> ><p> >After hitting return in the grub prompt you get something similar to this >one? ></p> ><pre> >Booting 'gentoo Linux' > >root (hd0,0) >Filesystem type is ext2fs, partition type 0x83 >kernel (hd0,0)/boot/kernel-2.4.20 root=/dev/hda3 vga=792 > >Error 15: File not found >Press any key to continue... ></pre> ><pre> >15 : File not found >This error is returned if the specified file name cannot be found, but >everything else (like the disk/partition info) is OK. ></pre> ><p> >If it's the kernel that it's missing (bzImage, kernel...):make sure that >the file it is referring to exists on your boot partition. >To find out what the exact name of your kernel is, first boot from the >live-cd or into your existing linux installation. Then mount /boot if >you've got a seperate partition, or mount / if you don't. Then do the >following: ></p> ><pre> ># cd /boot ># ls ></pre> ><p> >This will list all the kernels that you've got on your boot partition. >If your kernel is missing make sure that you compiled a kernel either >with genkernel or make menuconfig: ></p> ><pre> ># cd /usr/src/linux/ ># make menuconfig ></pre> ><p> >And that you copied it to your boot partition: ></p> ><pre> ># cp /usr/src/linux/arch/[your architecture, e.g. i386]/boot/bzImage >/boot/ ></pre> ><p> >However if this error is caused while trying to install grub. And is >similar to this one: ></p> ><pre> >grub> root (hd0,0) > Filesystem type is xfs, partition type 0x83 > >grub> setup (hd0) > Checking if "/boot/grub/stage1" exists... no > Checking if "/grub/stage1" exists... no > >Error 15: File not found ></pre> ><p> >First of all make sure that you changed root(hd0,0) and setup (hd0) >according to your systems specifications. >If you've typed in everything correctly, then you should compare this >thread. It seems that one ebuild version of grub is flawed. >(0.93.20031222) The best solution is most likely to try another ebuild >of grub. One possibility is to mask this version of grub: ></p> ><pre> ># echo "=sys-boot/grub-0.93.20031222" >> /etc/portage/package.mask ># emerge grub -p ></pre> ><p> >Or else give this line a try provided by <c>dirtboy</c> ></p> ><pre> ># grub-install /dev/bootdevice ></pre> ><comment> >Notice that bootdevice has to be something like hda or hda1, depending >whether you want to install it or not in the MBR. The major and minor >numbers must suit your configuration. ></comment> ><p> >If all else fails make sure that your partition is not somehow corrupt. >Be sure that you are able to great symbolic links. ></p> ></body> ></section> > ><section> ><title>Grub error 17</title> ><body> ><pre> >17 : Cannot mount selected partition >This error is returned if the partition requested exists, but the >filesystem type cannot be recognized by GRUB. ></pre> ><p> >Be sure to check your root(x,y) settings in your grub.conf. ></p> ></body> ></section> > ><section> ><title>Grub error 18</title> ><body> ><pre> >18 : Selected cylinder exceeds maximum supported by BIOS. This error >is returned when a read is attempted at a linear block address beyond >the end of the BIOS translated area. 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). ></pre> ><p> >Try an update for your BIOS and/or move your boot partition to the >front (or at least into the appropriate range). ></p> ></body> ></section> > ><section> ><title>"GRUB GRUB GRUB GRUB..."</title> ><body> ><p> >According to <c>airhead</c> this can be caused by having your bios >detect your disks automatically. Try to set your bios entry to >User Type HDD. ></p> ></body> ></section> > ><section> ><title>Probing devices to guess BIOS drives. >This may take a long time. </title> ><body> ><p> >When trying to install grub, grub hangs at this line. >One possible solution could be that you have some weird configuration >of your devices, like ultra/non-ultra DMA disks on one cable. ></p> ></body> ></section> > ><section> ><title>When installing grub it just hangs</title> ><body> ><p> >If you haven't got a floppy drive, have you used the --no-floppy switch? ></p> ></body> ></section> > ><section> ><title>Uncompressing Linux... Ok, booting the kernel.</title> ><body> ><p> >One possible solution is that ACPI is not working correctly. Try to >disable it in your bios or in your kernel. ></p> ></body> ></section> > ><section> ><title>Where is my grub.conf?</title> ><body> ><p> >Try the following lines provided by <c>madtomkidd</c>: ></p> ><pre> ># mount /dev/hda1 /boot ># nano -w /boot/grub/grub.conf ></pre> ><p> >Be sure to note that this implies that you've got a separate boot >partition, which is /dev/hda1. Otherwise you'll have to change the >first line accordingly. ></p> ></body> ></section> > ><section> ><title>Could not find device for /boot/boot: >Not found of not a block device</title> ><body> ><p> >When trying to run grub-install you receive this error message? >Check that you didn't forget the following: ></p> ><pre> ># cp /proc/mounts /etc/mtab ></pre> ></body> ></section> > ><section> ><title>After hitting enter at the grub menu the system >reboots</title> ><body> ><p> >Try disabling framebuffer support in your kernel. >If this does not help, disable APM/APCI/ACP. ></p> ></body> ></section> > ><section> ><title>After hitting enter at the grub menu the screen >goes black</title> ><body> ><p> >Turn off framebuffer (typically remove vga=XYZ from your >grub.conf) and check the processor architecture in your >kernel config. ></p> ></body> ></section> > ><section> ><title>After upgrading grub you only get a grub prompt?</title> ><body> ><p> >Make sure that your menu.lst link exists: ></p> ><pre> ># cd /boot/grub ># ln -s grub.conf menu.lst ></pre> ><p> >And that you executed the following in grub: ></p> ><pre> >root (hd0,0) >setup (hd0) ></pre> ><p> >Check out ><uri link="http://bugs.gentoo.org/show_bug.cgi?id=39392"> >bug 39392</uri>. ></p> ><p> >You may also want to try this tip provided by <c>ibis</c>: ></p> ><pre> ># cd /boot ># ln -s ./ boot ># grub-install --root-directory=/boot /dev/hda ></pre> ></body> ></section> > ><section> ><title>After upgrading your grub image is gone?</title> ><body> ><p> >First of all check if the file you are referring to really >exists. If that is the case, go and check the ebuild. Maybe the >patch for the splash image is commented out in the version that >you are using. ></p> ></body> ></section> > ><section> ><title>Cannnot open root device "hdaX"</title> ><body> ><p> >Are you getting something like the following error? ></p> ><pre> >VFS: Cannot open root device "hda7" or 03:07 >Please append a correct "root=" boot option >Kernel Panic: VFS: Unable to mount root fs on 03:07 ></pre> ><p> >Make sure your grub.conf reads two times the same (hd0,X) entry: ></p> ><pre> >root(hd0,1) >kernel (hd0,1) ></pre> ><p> ><c>nephros</c> said this is 80% of the time caused by an incorrectly >configured kernel, specificly either: ></p> ><pre> >[+]IDE chipset (or SCSI controller) support not compiled or compiled >as a module (and no initrd). >[+]filesystem support used on root partition not compiled or compiled >as a module (and no initrd). >[+]support for MSDOS partition tables not compiled >(CONFIG_PARTITION_ADVANCED -> CONFIG_MSDOS_PARTITION)(it happened!) ></pre> ><p> >On fresh installs it's often caused by not having edited /etc/fstab >during the install process, and it still contains lines like "/dev/ROOT >/ ext2 defaults,noatime 0 0". Solution for both kinds is obviously rebooting >the LiveCD or, in the former case, just a sane kernel and fix the configs. ></p> ></body> ></section> > ><section> ><title>Cannot find [insert any filesystem] on ide0(3,5)</title> ><body> ><pre> >sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,5) >XFS: bad magic number >XFS: SB validate failed >Kernel Panic: VFS: Unable to mount root fs on 03:05 ></pre> ><p> >Make sure you've set your root partition in your grub.conf correctly. ></p> ></body> ></section> > ><section> ><title>Using genkernel but forgot to note that kernel >version?</title> ><body> ><p> >Boot your system using your LiveCD, mount your boot partition and >run the following commands: ></p> ><pre> ># cd /boot ># ls ></pre> ><p> >This will list various files that can be found on your boot partitions. >One should start with kernel- while anouther one starts with initrd-. >The number/text behind it is your kernel version. Now follow the handbooks >instructions and exchange the sample kernel version with the one you installed. ></p> ></body> ></section> > ><section> ><title>Unable to boot into Windows</title> ><body> ><pre> >Booting 'Win2k' >root (hd1,0) >Filesystem type unknown, partition type 0x7 >chainloader +1 ></pre> ><p> >Make sure your boot entry reads something similar to one of these: ></p> ><pre> >title=%$@@#$* >root (hd0,0) >chainloader (hd0,0)+1 ></pre> ><pre> >title=%$@@#$* >rootnoverify (hd0,0) >chainloader (hd0,0)+1 ></pre> ><p> >Have special care with the chainloader option. ></p> ></body> ></section> > ><section> ><title>Boot Windows from your second harddrive</title> ><body> ><p> >If you've got problems doing so, try the following tip from ><c>cyrillic</c>, by changing your windows boot entry: ></p> ><pre> >title Win2k >map (hd0) (hd1) >map (hd1) (hd0) >chainloader (hd1,0)+1 ></pre> ></body> ></section> > ></chapter> > ></guide>
Created attachment 51772 [details] The Grub Error Collection version 1.3 Sorry for the above comment. This version corrects the author name for Hartwig Brandl and establishes Creative Commons license.
I see a "tip by cyrrilic", we normally use <mail link="foo@bar">cyrrilic</mail> for that or, if it's a forum user, <uri link="forum-path-to-profile">cyrrilic</uri>.
Created attachment 52189 [details] The Grub Error Collection version 1.4 Profile links corrected. Hartwig: There is movement in the thread, please revise when you have some time... :)
Sven, what's the current status of this??
I've updated the guide a bit and committed it to CVS. It'll be available at http://www.gentoo.org/doc/en/grub-error-guide.xml. I have removed one or two sections that were completely not grub related, one of them because the problem is a bit more complex (probably deserves a guide on its own). The guide is revamped so that each issue is its own chapter (easier for the user to find, since there is a drop-down menu for the chapters) and each chapter has a "Situation" and "Solution" section. It's not linked yet (this bug is marked as a showstopper), please verify the guide and tell me if you like it, stuff needs to be added/changed etc. Also state if it's good for publication :)
Hey, you really improved this dramatically :) Just one notice: link should be changed from 'grub-error-collection.xml' to 'grub-error-guide.xml' (you changed the filename) The rest looks cool! About the thread: new, yet unresolved, errors have 'appeared'. After they get solved I'll attach a patch or something.
Fixing link, thanks for reporting it.
Created attachment 54125 [details, diff] grub-segfault.patch This patch is proposed to be applied into the current CVS grub-error-guide.xml as an update. It contains just a new chapter of low relevance.
The addition is added. I'm closing this bug now. Thanks for the contribution!
