Grub error after restoring with fsarchiver

[jonathonp]

Steps taken so far on my notebook:

1. Made a backup of f12 with fsarchiver using Linux SystemRescueCd
2. Made new partition scheme with gparted
3. Restored fsarchive
4. Edited fstab and grub.conf to match new partition scheme
5. I installed grub with the fedora dvd. (I received a non critical error but it worked - I can't remember the details)
6. Booted fedora (selinux remapped on boot)
7. Updated fedora with yum

Everything seemed ok until i rebooted.

8. Rebooted - Grub is missing
9. When i tried to reinstall grub i received an error

[root@orange jonathon]# grub
Probing devices to guess BIOS drives. This may take a long time.


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> find /boot/grub/stage1
find /boot/grub/stage1
 (hd0,6)
grub> setup (hd0,6)
setup (hd0,6)

Error 12: Invalid device requested

10. I used the supergrub boot disc

(to boot !LINUX! (>=2) MANUAL option

Fedora booted with a non critical error. I'm can't see what is wrong with grub.

error
booting '7hda7 sda7 (hd0,6) hd0s7 ext2s 20GB Fedora Release 12

[root@orange jonathon]# cat /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 do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,8)
#          kernel /boot/vmlinuz-version ro root=/dev/sda9 rdblacklist=nouveau rdblacklist=nouveau
#          initrd /boot/initrd-[generic-]version.img
default=0
timeout=5
splashimage=(hd0,6)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.12-174.2.3.fc12.x86_64)
	root (hd0,6)
	kernel /boot/vmlinuz-2.6.31.12-174.2.3.fc12.x86_64 ro root=UUID=8cee91f2-d5a1-4073-b699-f145a0e2749a  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet rdblacklist=nouveau rdblacklist=nouveau
	initrd /boot/initramfs-2.6.31.12-174.2.3.fc12.x86_64.img
title Other
	rootnoverify (hd0,0)
	chainloader +1

[stoat]

Hello jonathonp,

Some things to consider or try...

For this...

Originally Posted by jonathonp

[root@orange jonathon]# grub
Probing devices to guess BIOS drives. This may take a long time.


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> find /boot/grub/stage1
find /boot/grub/stage1
 (hd0,6)
grub> setup (hd0,6)
setup (hd0,6)

Error 12: Invalid device requested

...Try this (if it's the master boot record that you're trying to re-install GRUB in)...

grub> root (hd0,6)
grub> setup (hd0)
grub> quit

And for this...

Originally Posted by jonathonp

I used the supergrub boot disc

(to boot !LINUX! (>=2) MANUAL option

Fedora booted with a non critical error.

...Did you remember to verify that UUID in the kernel command line of your grub.conf file? It's bound to be different now.

[jonathonp]

Hi stote. I received this error:

[root@orange jonathon]# grub
Probing devices to guess BIOS drives. This may take a long time.


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> root (hd0,6)
root (hd0,6)
 Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0,6)  
setup (hd0,6)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,6)"... failed (this is not fatal)
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,6)"... failed (this is not fatal)
 Running "install /boot/grub/stage1 (hd0,6) /boot/grub/stage2 p /boot/grub/grub.conf "... succeeded
Done.

Any ideas what it means? Grub is working again. I can't explain why it disappeared after the update. Maybe things got screwed up after restoring with fsarchiver. i always install grub on root partition and use http://gag.sourceforge.net/index.html to boot my systems. What' are the steps for removing grub and reinstalling it?

I noticed these package:
bootconf, x86_64 grubby.x86_64

but i have never used them before.

[stoat]

Originally Posted by jonathonp

i always install grub on root partition and use http://gag.sourceforge.net/index.html to boot my systems.

An important detail that was not mentioned before. Anyway, you knew how to modify the suggestion made by me.

Originally Posted by jonathonp

I received this error:

...

Any ideas what it means?

I gress you are referring to this...

Originally Posted by jonathonp

 Running "embed /boot/grub/e2fs_stage1_5 (hd0,6)"... failed (this is not fatal)
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,6)"... failed (this is not fatal)

That happened because you installed stage1 in a partition boot sector. Stage1.5 is only installed when GRUB is installed in a master boot record. It goes in the so-called DOS Compatibility Region which is the 62 normally unused sectors between the master boot record and the first partition of a legacy hard drive. When GRUB is installed in a partition boot sector, there is no such place in the partition to put stage1.5, so it is omitted.

Originally Posted by jonathonp

What' are the steps for removing grub and reinstalling it?

If by that you mean the grub package, then yum remove grub would uninstall it. And yum install grub would re-install it. But if you mean the GRUB boot loader, then you don't really uninstall it. Since most of it exists in the master boot record, DOS Compat Region, and partition boot sectors, you install something else in place of it. Or re-install it over itself.

Originally Posted by jonathonp

I noticed these package:
bootconf, x86_64 grubby.x86_64

but i have never used them before.

Originally Posted by rpmfind.net

The bootconf configuration utility is a convenient tool for setting GRUB kernel boot options.

Originally Posted by The grubby man page

grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), yaboot (powerpc) and zipl (s390) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment.

[jonathonp]

Thanks for the detailed information. Cheers