Recent updates caused Grub installation to be damaged?

Brian Morrison bdm at fenrir.org.uk
Sun Jun 15 07:58:23 UTC 2008


On Sun, 15 Jun 2008 09:46:14 +0200
Maurizio Marini <maumar at datalogica.com> wrote:

> i got the same issue; i was unable in any way to 
> chroot /mnt/sysimage
> after linux rescue
> 
> as fstab and grub.conf have been changed by upgrade; i fixed them mounting disk  on an external usb box.
> this was my changed fstab:
> 
> UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb /                       ext3    defaults        1 1
> UUID=22309ffe-0180-41bd-a868-9d5b15660781 /home                   ext3    defaults        1 2
> UUID=c46f0b8e-ea34-47f5-8c7f-57a7f3a5d531 /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
> UUID=817d341a-8daa-43dd-8c97-2eea4c1f418f swap                    swap    defaults        0 0
> 
> 
> i restored it to:
> [09:34:12 root at matanui /var/log ]# cat /etc/fstab
> /dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
> /dev/VolGroup00/LogVol02 /home                   ext3    defaults        1 2
> /dev/sda1               /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
> 
> 
> this was my grub.conf changed by upgrade:
> # 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/sda
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora (2.6.25.6-55.fc9.i686)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet
>         initrd /initrd-2.6.25.6-55.fc9.i686.img
> title Fedora (2.6.25.4-30.fc9.i686)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.25.4-30.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet
>         initrd /initrd-2.6.25.4-30.fc9.i686.img
> 
> 
> i restored it to:
> # 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/sda
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora (2.6.25.6-55.fc9.i686)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
>         initrd /initrd-2.6.25.6-55.fc9.i686.img
> title Fedora (2.6.25.6-55.fc9.i686)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet
>         initrd /initrd-2.6.25.6-55.fc9.i686.img
> title Fedora (2.6.25.4-30.fc9.i686)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.25.4-30.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet
>         initrd /initrd-2.6.25.4-30.fc9.i686.img
> 
> 
> at last i was able to chroot and then i issued:
> grub-install /dev/sda
> 
> then i was able to boot my fc9.
> 
> i investigated on /var/log/yum.log
> to find the *guilt*; 
> 
> 
> here it is the excerpt:
> 
> 
> 
> 
> 
> Jun 13 13:54:46 Updated: selinux-policy-3.3.1-64.fc9.noarch
> Jun 13 13:55:08 Updated: selinux-policy-targeted-3.3.1-64.fc9.noarch
> Jun 13 13:55:35 Updated: selinux-policy-devel-3.3.1-64.fc9.noarch
> Jun 13 13:55:40 Updated: logwatch-7.3.6-22.fc9.noarch
> Jun 13 13:55:47 Updated: kernel-headers-2.6.25.6-55.fc9.i386
> Jun 13 13:57:04 Updated: 1:java-1.6.0-openjdk-javadoc-1.6.0.0-0.15.b09.fc9.i386
> Jun 13 13:57:14 Installed: kernel-devel-2.6.25.6-55.fc9.i686
> Jun 13 13:57:23 Updated: nspr-4.7.1-0.9.1.fc9.i386
> Jun 13 13:57:28 Updated: nss-3.12.0.3-0.9.1.fc9.i386
> Jun 13 13:57:55 Updated: 1:java-1.6.0-openjdk-1.6.0.0-0.15.b09.fc9.i386
> Jun 13 13:57:57 Updated: postgresql-libs-8.3.3-1.fc9.i386
> Jun 13 13:57:58 Updated: kpartx-0.4.7-15.fc9.i386
> Jun 13 13:57:59 Updated: device-mapper-multipath-0.4.7-15.fc9.i386
> Jun 13 13:58:00 Updated: 1:java-1.6.0-openjdk-plugin-1.6.0.0-0.15.b09.fc9.i386
> Jun 13 13:58:02 Updated: nss-tools-3.12.0.3-0.9.1.fc9.i386
> Jun 13 13:58:31 Installed: kernel-2.6.25.6-55.fc9.i686
> Jun 13 13:58:32 Updated: gstreamer-plugins-farsight-0.12.7-2.fc9.i386
> Jun 13 13:58:34 Updated: gdb-6.8-10.fc9.i386
> Jun 13 13:58:35 Updated: nspr-devel-4.7.1-0.9.1.fc9.i386
> Jun 13 13:58:36 Updated: nss-devel-3.12.0.3-0.9.1.fc9.i386
> Jun 13 13:59:09 Installed: kernel-2.6.25.6-55.fc9.i686
> 
> 
> 
> 
> 
> my suspects are on 
> Jun 13 13:57:59 Updated: device-mapper-multipath-0.4.7-15.fc9.i386
> 
> reading 
> /usr/share/doc/device-mapper-multipath-0.4.7/FAQ
> 
> ++++++++++++++++++++++++++++++++++++++++
> * in /boot/grub/menu.lst, define the root= kernel parameter
>   Example : root=/dev/system1
> * modify /etc/fstab to reference /dev/system* partitions
> 
> At reboot, you should see some info like :
> 
> path /dev/sda : multipath system
> ++++++++++++++++++++++++++++++++++++++++
> 
> At reboot you can see a very unexpted christmas gift!
> 
> i think that device-mapper-multipath has changed 
> my /boot/grub/menu.lst and /etc/fstab, but some othr changes are missing;
> further, chkconfig multipathd --list is off off off off off
> then multipathd doesn't get started at boot and changes on grub.conf and fstab 
> are devasting
> 
> 	-m
> 

Ah, that's interesting, can you add the comments above to the bugzilla
entry here please:

https://bugzilla.redhat.com/show_bug.cgi?id=450143

I think it would help.

I'll have a look at the fstab situation on my F9 laptop and see if that
changed for me.

-- 

Brian Morrison

   "Arguing with an engineer is like wrestling with a pig in the mud;
    after a while you realize you are muddy and the pig is enjoying it."




More information about the fedora-list mailing list