Lief Hendrickson wrote: > At 07:07 PM 1/5/2009, James A. Sack wrote: >> Lief Hendrickson wrote: >> > At 02:19 PM 1/5/2009, James A. Sack wrote: >> >> Lief Hendrickson wrote: >> >> >.. >> >> > I was able to list the contents of the files using cat command. >> Here >> >> > they are: >> >> > >> >> > grub.conf as follows: >> >> > >> >> > # grub conf generated by anaconda >> >> > # >> >> > # Note that you do not have to rerun grub after making changes to >> >> this file >> >> > # NOTICE: You have a /boot partition. This means that >> >> > # all kernel and initrd paths are relative to >> >> /boot, eg. >> >> > # root (hd1,0) >> >> > # kernel /vmlinuz-version ro >> >> > root=/dev/VolGroup00.LogVol00 >> >> > # initrd /initrd-version.img >> >> > # boot=/dev/hda >> >> > default=1 >> >> > timeout=15 >> >> > splashimage=(hd1,0)/grub/splash.xpm.gz >> >> > hiddenmenu >> >> > title Fedore Core (2.6.9-1.1667) >> >> > root (hd1,0) >> >> > kernel /vmlinuz-2.6.9-1.667 ro >> >> root=/dev/VolGroup00/LogVol00 >> >> > rhgb quiet >> >> > initrd /initrd-2-6.9-1.667.img >> >> > title Windows >> >> > rootnoverify (hd0,0) >> >> > chainloader +1 >> >> > >> >> > ------------------------------------------------------------- >> >> > device.map as follows >> >> > >> >> > # this device map was generated by anaconda >> >> > (fd0) /dev/fd0 >> >> > (hd0) /dev/hda >> >> > (hd1) /dev/hdb >> >> > >> >> > ----------------------------------------------------------------- >> >> > (note the above files are typed so might have spelling errors) >> >> > Do you see anything that needs to be changed to fix the problem? >> >> >> >> >> >> I think this shows the problem is that the removed failed windows disk >> >> has resulted in a disk renaming/renumbering that is inconsistent with >> >> the conf file. >> >> >> >> The grub.conf file should be changed to replace the (hd1,0) in the >> root >> >> line to read >> >> root (hd0,0) >> >> Similarly change the splashimage line (optional). >> >> >> >> If you know how to get root in knoppix and remount the hda1 >> read-write, >> >> you can edit it within knoppix. >> >> >> >> Alternatively, you can boot hda to the 'grub>' prompt again and >> give the >> >> following commands ( write these down ;-) ). >> >> >> >> root (hd0,0) >> >> kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 >> >> initrd /initrd-2-6.9-1.667.img >> >> boot >> >> The 'rhgb quiet' part I omitted is ok -- that was optional. Note that >> >> grub is fussy! about these lines, don't miss the slashes or dashes, or >> >> put in any spaces except where shown. Note also the 'ell' (not >> 'one') in >> >> 'Vol', and the 'zero zero' (not 'OH OH'). Fussy! >> >> >> >> >> >> Presuming that boots your fedora ok, you can become root, and edit >> >> /boot/grub/grub.conf as above. You should also delete the three lines >> >> starting with. >> >> title Windows >> >> >> >> After that edit, booting should be back to working as it is >> supposed to >> >> (it says in fine print). >> >> >> >> Regards, >> >> ..jim >> > >> > >> > I was able to edit the grub.conf file in knoppix. I changed to root >> > (hd0,0) and splashimage. It still did not boot. >> > I next tried entering the commands from the grub prompt. The first >> time >> > I got an error 15 at the initrd command , then noticed you had a dash >> > after the 2 instead of a decimal point. Should be >> >> good eyes! >> >> > grub> initrd /initrd-2.6.9-1.667.img >> > I tried that and then the boot command. Result: successful boot >> > >> > Now problem remains of how to get it to work without having to use grub >> > prompt commands. >> > I took out the three lines starting with Windows. Do I need the >> > "default=1", the "timeout=15" and the "hiddenmenu" lines? >> >> No, another good observation on your part! The 'default=1' is probably >> the remaining obstacle (I'd wager) and you should either replace it with >> 'default=0' (no quotes) -- or equivalently delete/comment it out >> altogether. >> >> It's a matter of preferences, but I always comment-out the hiddenmenu >> line, In this case it would have been useful to see the menu without >> having to remember that you can ask for it with appropriate keypresses. >> >> The timeout value is in seconds. I like at least 10 even when there's >> only one choice(!), so I can see when to press a key to edit the parms, >> also kinda meaningful only if nohiddenmenu is disabled (commented out or >> deleted). Also, you can always press the enter key to end the countdown. >> >> > It still goes to the grub prompt when booting to hard drive. >> >> My guess: there's no menu shown because of the hidddenmenu, and after 15 >> seconds it tries to boot the second choice (counting from 0), but there >> is no second boot choice, so it falls-back to the boot-prompt (which is >> a nice fallback, actually). >> >> So, now you have to enter the manual commands one more time, then >> re-edit /boot/grub/grub.conf to change the default and hiddenmenu lines. >> >> Hey, you're almost there! :-) >> >> >> Regards, >> ..jim > > I changed to default = 12 and commented out the hiddenmenu line.
I assume you meant that you changed to timeout=12 (not default). Did a grub menu show on the screen during the boot process? If not, I suspect the install operation needs to be repeated (as in last email) -- as root grub-install --recheck > Result: still goes to grub prompt and does not boot. > > I wonder if the grub.conf file is being executed. I noticed there are > two grub folders as follows > > filesystem/boot/grub/ (this folder has a grub.conf file) > and > filesystem/boot/boot/grub (this folder does not have a grub.conf file) > > Why is there a boot folder under the main boot folder? This shouldn't be there and may be an indication of a prior install that had a wrong parm specified somewhere. > Anything else to try in the grub.conf file to see if it is executing? > You did see the comments about avoiding spaces in default=0 timeout=15 eh? If commenting out the hiddenmenu line did _not_ result in the grub menu being shown, I'd vote that the install operation needs repeating. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
