PDA

View Full Version : GRUB not booting after recent update



bAer`-
26th July 2007, 03:13 PM
Hey everyone!
I just updated fedora core 7 x64 this morning and after i rebooted GRUB wont boot. All i get is:
"GRUB _" the _ being a blinking cursor.

I downloaded the Super Grub CD, and i can get Linux to boot, but i can't figure how to fix GRUB.

OK so here's the situation:
/dev/sda has Windows XP running on it. I boot the windows boot loader normally and enter GRUB from there. But it won't boot.
Now here is the setup:


Disk /dev/sda: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track, 4866 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 2 1303 10458315 f W95 Ext'd (LBA)
/dev/sda2 * 1304 4866 28619766 b W95 FAT32
/dev/sda5 2 1303 10458283+ 7 HPFS/NTFS

Disk /dev/sdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 2 24792 199133707+ f W95 Ext'd (LBA)
/dev/sdb5 2 4646 37310931 7 HPFS/NTFS
/dev/sdb6 4647 9764 41110300 7 HPFS/NTFS
/dev/sdb7 9765 14802 40467701 7 HPFS/NTFS
/dev/sdb8 16761 20585 30724280 7 HPFS/NTFS
/dev/sdb9 20586 24792 33792695 7 HPFS/NTFS
/dev/sdb10 14803 14815 104391 83 Linux
/dev/sdb11 14816 16760 15623181 8e Linux LVM

Partition table entries are not in disk order

my fstab looks like this:

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0

I hope anyone has a clue on how to fix this. I'm pretty new to Linux/Fedora so don't eat me alive please :)

JN4OldSchool
26th July 2007, 03:42 PM
I was waiting to see if anyone else answered this as I know nothing about the Windows bootloader but what I suspect happened is your grub in /boot changed but the Windows bootloader didnt. The Windows bootloader is now "lost." You will probably have to change the grub entry there.

bAer`-
26th July 2007, 03:51 PM
I was waiting to see if anyone else answered this as I know nothing about the Windows bootloader but what I suspect happened is your grub in /boot changed but the Windows bootloader didnt. The Windows bootloader is now "lost." You will probably have to change the grub entry there.

Well i GRUB starts, judged by the name GRUB showing up and the blinking cursor.(GRUB is not named anywhere in the windows bootloader, it says Fedora Core 7 there) What i suspect is that GRUB can't get into the second Boot stage or something.

jonathonp
26th July 2007, 06:06 PM
Hi! the supergrub boot cd is a great tool. did you try fixing grub with it. i recommend installing grub on the boot partition. makes life easy and if anything goes wrong with your MBR such as not being able to point towards grub, it's easy to fix. at one stage i was booting vista, xp, fedora 6, 7 and ubuntu. eventually i came to the conclusion that the vista bootloader is an annoying thing but you can make it point to your linux boot partitions however from my experience the tools available to do it such as EasyBCD are unreliable. i think xp is handy to have if you need it there for something. Now i'm using the acronis disk director suite boot loader which is so easy and always works. all you do is install xp and your linux distributions on their own boot partitions and do a simple acronis install either with the boot cd or via xp. acronis does not overwrite (neither does your vista boot loader for that matter) your xp boot loader and can be easily disabled. i don't know if it works with vista though. anyway i'm done with vista and very rarely do i use xp anyway. you might want to reinstall fedora and do your setup differently.

bAer`-
27th July 2007, 08:23 PM
I reinstalled Fedora Core 7 now and installed GRUB on the MBR. Now Windows XP won't boot. This is my GRUB menu.lst:


# 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,9)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,9)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.21-1.3194.fc7)
root (hd1,9)
kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.21-1.3194.fc7.img
title Windows XP
rootnoverify (hd0,4)
makeactive
chainloader +1

I added the "makeaktiv" manually because i saw this in quite some pages i found with Google. But it still won't boot. Any help would be greatly appreciated!

Greetz bAer`-

EDIT:
I removed the makeactiv and changed the rootnoverify (hd0,4) to rootnoverify (hd0,1), because my windows boot partition is actually sda2 as seen in fdisk.
Works fine now, thanks for any help anyway :)

marcusB
27th July 2007, 09:54 PM
I updated to the 2.6.22.1-33.fc7 kernel today and encountered the same problem, no GRUB menu, just a blank screen except for "GRUB" in the top left corner.

Super Grub 0.9598 was able to find the linux boot partition and restore grub.

This particular x64 machine only has a single Fedora 7 linux install, and has never run any flavor of Windows. So I don't think this problem was caused by Windows.

dpatt
1st August 2007, 06:01 PM
I have exactly the same problem.
I have Fedora Core 7 x86_64.
Fedora is installed in VolGroup00 LogVol00.

Like a fool, I trusted that everything would work when updating the kernel. Now, when I reboot I get a "GRUB _" prompt.

I downloaded this "Super Grub boot CD" that I heard mention of above, but I can't get things to work out for me.

If I select, "GNU/Linux" from the Suber Grub boot CD menu, I see three choices (as they should be):
Fedora (2.6.22.1-41.fc7)
Fedora (2.6.22.1-27.fc7)
Other - Windows

I can boot into Windows just fine through this menu.
However, I cannot boot into Fedora!

If I select "Fedora (2.6.22.1-27.fc7)", for example, I end up with
Error 28: Selected item cannot fit into memory

This is preceded by the usual stuff:
root (hd1,0)
kernel /vmlinuz-2.6.22.1-27.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[ ]
initrd /initrd-2.6.22.1-27.fc7.img
[ Linux - initrd @ 0x9fb5e000 0x3b1d3a bytes ]

It does this for either kernel!
Tell me how I can get back to normalcy without having to reinstall Fedora (would be several days lost)

Thanks!

DP

marcusB
1st August 2007, 07:30 PM
Sorry, I do not remember the exact operations I told Super Grub to do, but I basically had it repair the MBR to use the LVM volume that Fedora was installed on. I did not actually try to boot the system with Super Grub, just had it repair the MBR.

I have not updated to the 2.6.22.1-41.fc7 kernel yet, it is also possible that this problem was somehow exacerbated by this new kernel build.

I don't have any more information on this, it might make sense to check for and/or file a bug on this.

If you do get more information, can you link this thread to whatever you find? Thanks!

dpatt
1st August 2007, 09:13 PM
I played around with supergrub to no avail. Somehow supergrub couldn't deal with that kernel. I couldn't get it to repair grub successfully, either - but that may reflect on my competence.

I ended up booting from the Fedora 7 install DVD, and selecting "upgrade". It wiped my old kernels, installed an older one, and replaced grub. Of course, all sorts of things were broken in the process everything compiled for the newer kernels).

However, I could boot FC7 again. I updated to the 41 kernel, and rebooted. I have started repairing recompiling a number of the broken things.

At least it boots. I wish I knew exactly what the problem was.

rileym3
2nd August 2007, 10:16 AM
Hello!
I have 2 identical x86_64 machines, and a P-III laptop which is i386.

The last known working kernel on the x86_64 machines was 2.6.21-1.3228.
The latest kernels seem to follow a different convention:
kernel-2.6.21-1.27
kernel-2.6.21-1.33
kernel-2.6.21-1.41

Something MUST be different in these newer kernels...perhaps someone can shed light on the recent changes? My 2 x86_64 machines, although identical in hardware and software, including kernel versions, react differently.

my morpheus server gives a kernel panic (how do I save a crashdump?)
my neo server simply reboots every time grub tries to boot a kernel
BOTH machines get the grub splash screen, which says the kernel will boot in <countdown> seconds...

My laptop which is NOT an x86, 64 (t9000), seems to boot just fine, although I do get a wierd message before the 'welcome to fedora' message. How can I save a copy of this to a textfile?
Smoothwall (www.smoothwall.org) has a web interface with a CGI that lets me see the kernel messages on boot. Perhaps it also saves this to a textfile? I might have to play with it and see...

It seems i386 machines may work fine, whereas the x86_64's may be the ones that fail to boot?
Are there any other people who have both arch's to test and confirm i386 vs x86_64 withany of these new kernels?

Hope this helps!
Regards,
Riley

jbkt23
12th August 2007, 01:50 PM
I am daul booting Fc6 & F7. On F7 the last update I installed was suffixed 1-33.fc7. Below are a list of steps I have to follow both in Fc6 and F7.
In Fc6 & F7:
Before booting to the new kernel I have to remake the initrd image for it because for some reason it is not made correctly during the yum install. If you watch while the kernel is installed you will see it hang and then some file locations with numbers like "P00.0000..." on the console. I think it has been noted as a bug in previous posts here.

mkinitrd initrd<kernel-version>.img <kernel-version>.fc6 or 7.

The odd thing that is new for my installation of F7 is that if I am in Fc6 and restart to boot into F7 it hangs with a kernel panic. If shutdown and then start up again F7 boots normally.

jbkt23