PDA

View Full Version : FC9 / GRUB_ / nvidia



sdolgy
2nd July 2008, 09:53 AM
Hi there,

Normally I can sort out these problems, but it seems after a night of playing around, I'm a little bit at a loss.

Problem:

FC9 does not boot. It gets to a GRUB_ prompt and does not echo keyboard input

Hardware:

AMD64 chipset with a raid0 disk that has FC9 on it (upgraded from FC8 to FC9). I had been able to reboot no problem since the upgrade two weeks ago. It has only been in the last 24hrs when the computer was 'accidentally' switched off by the girlfriend that the problem has appeared. Normally it doesn't get a reboot.

I've seen another post that suggests the following:


1. Boot to the rescue environment
2. Mount the root / to /mnt/sysimage (I think Fedora rescue does it automatically)
3. chroot /mnt/sysimage
4. grub
5. device (hd0) /dev/sda
6. root (hd0,1)
7. setup (hd0)

I'm able to do steps 1, 2, 3 & 4.

When I do run 'fdisk -l | more' I can see that both /dev/sda and /dev/sdb have a * beside them. The output is similar but not exact to the following (can't cut and paste from console)

As they are mirrorred, which one should i be putting at step 5 to resolve this?

I tried grub-install with /dev/VolumeGroup00 ... and hoped this would work, but I get an error back such as:

/dev/VolumeGroup00 does not have any corresponding BIOS drive

I've also tried with /dev/sda and /dev/sdb with the same error message

/dev/sda does not have any corresponding BIOS drive
/dev/sdb does not have any corresponding BIOS drive

So..of course, any suggestions to be able to boot up normally would be most welcome.

Thanks in advance

sdolgy
2nd July 2008, 10:06 AM
Could it be i need to use /dev/md0 ? hmmm! I hope. Something to try when I get home. Any other suggestions would be most welcome.

glennzo
2nd July 2008, 10:34 AM
Since you can't copy and paste this will be a pain in the butt, but could you post the complete output of fdisk -l ??

sdolgy
2nd July 2008, 02:42 PM
fdisk -l:

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

Device Boot Start End Blocks Id System
/dev/sda1 * 1 25 200781 83 Linux
/dev/sda2 26 24792 198940927+ 8e Linux LVM

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

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 25 200781 83 Linux
/dev/sdb2 26 24792 198940927+ 8e Linux LVM

Disk /dev/dm-0: 203.9 GB, 203928108032 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xffffffff

Device Boot Start End Blocks Id System
/dev/dm-0p1 * 1 25 200781 83 Linux
/dev/dm-0p2 26 24792 198940927+ 8e Linux LVM

Disk /dev/dm-1: 205 MB, 205599744 bytes
255 heads, 63 sectors/track, 24 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000


Disk /dev/dm-2: 203.7 GB, 203715509760 bytes
255 heads, 63 sectors/track, 24767 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000


Disk /dev/dm-3: 201.5 GB, 201595027456 bytes
255 heads, 63 sectors/track, 24509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000


Disk /dev/dm-4: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x30307800

here's the /boot/grub/grub.conf:

# 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 (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/mapper/nvidia_gigfbbbe
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.25.6-55.fc9.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.25.6-55.fc9.x86_64 ro root=UUID=9edac39c-eb88-4728-96ce-06682eee0627 rhgb quiet
initrd /initrd-2.6.25.6-55.fc9.x86_64.img
title Fedora (2.6.25-14.fc9.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=9edac39c-eb88-4728-96ce-06682eee0627 rhgb quiet
initrd /initrd-2.6.25-14.fc9.x86_64.img

I haven't touched grub ever.

JEO
2nd July 2008, 06:59 PM
You said in your first post that you had raid 0 which is striped. It sure looks like you have a raid 1 mirror. It looks like you have lvm on top of dmraid. Can you verify that you are using mirroring or striping?

Also what is the output of:
ls /dev/mapper
?

sdolgy
3rd July 2008, 09:33 AM
sorry about that. it's raid1, mirorred. its a hardware raid.

JEO
3rd July 2008, 09:43 AM
You did not provide the output of ls /dev/mapper but if it matches below, from the rescue environment try:

grub --device-map=/dev/null

device (hd0) /dev/mapper/nvidia_gigfbbbe
root (hd0,0)
setup (hd0)

JEO
3rd July 2008, 09:56 AM
Oh, by the way, I tested grub-install and that method does not work right for dmraids. I think it has to do with the extra p that gets appended to the /dev/mapper partition name before the partition number. So that's why grub-install won't work in this case.

sdolgy
3rd July 2008, 12:32 PM
hi jeo, thanks for the replies. it's my machine at home and i can't connect to it remotely to do an ls /dev/mapper ... when i get home tonight i'll post it. i'll also try your other suggestion.

thanks again

sdolgy
3rd July 2008, 06:37 PM
hi jeo,

that fixed it. cheers. wonder if that grub-install bug is posted in bugzilla.

JEO
3rd July 2008, 10:12 PM
Glad to hear that it worked. :)

I noticed that grub-install isn't even included in the rescue environment (when you tell it to skip mounting your system) only the grub shell is.