Deleted a partition; GRUB doesn't boot! (Answered)

[gonzalo76]

Hi to everyone,

I have 3 partitions , 1 Windows, 2 Fedora, 3 Documents.
In Windows, using Partition Magic, I deleted the 3rd partition, and in that place, I created two more partitions, one in NTFS and the other in FAT32. Now, in total, I have 4 partitions.

I use GRUB installed in the MBR to boot Windows XP and Fedora Core. Everything was just fine until I deleted that 3rd partition.

I think that I broke GRUB deleting that partition and making other partitions. Obviously, now, I can't boot any system and what appears to me is the GRUB minimal bash-like line screen.
I read a lot about how to fix this problem, but I couldn't resolve it.

Please, can someone help me...?

Thank you
gonzalo

[feenixx]

when you deleted one partition, boot table and drive numbers/letters got
re-organised. this happens when adding or deleting partitions.

since you did this using windows, grub doesn't know things have changed
and tries to look 'boot' (and fedora's root) partition from wrong places so
to speak.

no problem, you can enter in grub's own ugly shell, so do the following.

1. define root parititon first (this mean paths become relative to that
partition, and you don't have to write /boot everytime..). use tabulature
key to guess filenames and get partition lists too. depending on your setup
(do you got one or two harddrives)..

-> root (hd

*press tab key here to get list of harddisks , you prolly get list containing
entry hd0, (hd1 for 2nd harddisk, choose the one that contains the /boot
partition).

->root (hd0,

*press tab key here to get list of partitions. there is prolly two partitions
with type of 'ext3' (or other one is ext2), choose first one of these. let's
assume ext3 drives are numbers 6 and 7.

->root (hd0,6)

*press enter. now all filenames are relative to that partition. you know
that you defined correct partition if you can find contents of boot partition
using tabulature name guessing feature. try to write '/vm' and press
tablulature key. name should autocomplete to vmlinuz-x.x.x.x or show list
of multiple vmlinuz entries. if not, try defining root again, now for other
ext2, ext3 partition.

*then list your menu.lst file and write 'kernel' line it contains. grub shell
has 'cat' command that allows you to list files.

-> cat /grub/menu.lst

*remember that paths are relative to defined 'root' partition (which is
/boot)


*write menu.lst 'kernel' line. example :

-> kernel /vmlinuz-2.6.3 ro root=LABEL=/

*use tab to guess filenames. you probably have /vmlinuz-2.4.xx if you're
running 2.4 kernel

*next, define initrd line. almost same as above. use tab to guess
correct file name. example :

-> initrd /initrd-2.6.3.img

*all should be set now. give boot command

-> boot


if you are able to boot in linux box, log in as a root and run 'grub-install /dev/hda' to re-install grub back to MBR.

[gonzalo76]

YES !!!
Once again you save my life, I did exactly what you said and finally I could boot into Linux again !!!
Thank you so so so much for your answer, perfectly clear. I'll print your replie just in case I need it once again.

Greetings...
gonzalo

[Jman]

Marked as resolved.

[leigh123linux]

Thread closed


@ Zdun

I moved your post here

http://forums.fedoraforum.org/forum/...d.php?t=180719