At 07:28 PM 1/5/2009, James A. Sack wrote:
Lief Hendrickson wrote:
> Carl Lowenstein wrote:
>> On Mon, Jan 5, 2009 at 5:20 PM, Lief Hendrickson <[email protected]>
>> 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
>> > 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?
>> > It still goes to the grub prompt when booting to hard drive.
>>
>> default=1 tells grub to boot the second thing that it finds in the
>> list. (Grub counts 0,1 not 1,2).
>> In the original grub menu, that would have been Windows. Now you
>> don't have a "second thing". So that line should now be default=0
>>
>> timeout=15 gives you 15 seconds to choose to do something else before
>> Grub proceeds automatically
>>
>> hiddenmenu hides all the options from you, for better or worse. If
>> you remove it or comment it out (# in first column) you will have a
>> somewhat more verbose text display from grub.
>>
>> carl
>> --
>> carl lowenstein marine physical lab u.c. san diego
>> [email protected]
>
>
> I changed the default line to "default = 0". It still only boots to
> grub prompt.
>
Did you have the spaces as shown? Maybe it needed to be "default=0" with
no spaces (or quotes).
negative on the spaces. the line reads
device=0
The next guess is that maybe the setup/install needs to be redone?
Carl, perhaps you can confirm that all that's necessary is to run (as root)
grub-install
although adding the recheck option might be useful
grub-install --recheck
Regards,
..jim
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
