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 -- KPLUG-Newbie@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie