Re: Recent updates caused Grub installation to be damaged?
On Sun, 15 Jun 2008 09:55:06 +0200 Maurizio Marini <[EMAIL PROTECTED]> wrote: > On Sunday 15 June 2008, Brian Morrison wrote: > > > > It's also the first time I've had this problem since starting with RH7. > yes. it is > maybe the first time for every distro > > > > Sounds like someone needs to bugzilla it then, this really shouldn't > > happen. Had I been on the road without an F9 DVD to hand it would have > > been a lot more difficult to fix. > > we should advise every other fc9 user on this issue, but i dunno how... > posting on a widely read mlist, like bugtraq, maybe Adding your observations to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=450143 would help, no one else seems to have noticed the device-mapper-multipath connection. -- 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." -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
On Sun, 15 Jun 2008 09:46:14 +0200 Maurizio Marini <[EMAIL PROTECTED]> 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 > defaults1 1 > UUID=22309ffe-0180-41bd-a868-9d5b15660781 /home ext3 > defaults1 2 > UUID=c46f0b8e-ea34-47f5-8c7f-57a7f3a5d531 /boot ext3 > defaults1 2 > tmpfs /dev/shmtmpfs defaults0 0 > devpts /dev/ptsdevpts gid=5,mode=620 0 0 > sysfs /syssysfs defaults0 0 > proc/proc procdefaults0 0 > UUID=817d341a-8daa-43dd-8c97-2eea4c1f418f swapswap > defaults0 0 > > > i restored it to: > [09:34:12 [EMAIL PROTECTED] /var/log ]# cat /etc/fstab > /dev/VolGroup00/LogVol00 / ext3defaults1 1 > /dev/VolGroup00/LogVol02 /home ext3defaults1 2 > /dev/sda1 /boot ext3defaults1 2 > tmpfs /dev/shmtmpfs defaults0 0 > devpts /dev/ptsdevpts gid=5,mode=620 0 0 > sysfs /syssysfs defaults0 0 > proc/proc procdefaults0 0 > /dev/VolGroup00/LogVol01 swapswapdefaults0 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
Re: Recent updates caused Grub installation to be damaged?
On Sunday 15 June 2008, Brian Morrison wrote: > > It's also the first time I've had this problem since starting with RH7. yes. it is maybe the first time for every distro > > Sounds like someone needs to bugzilla it then, this really shouldn't > happen. Had I been on the road without an F9 DVD to hand it would have > been a lot more difficult to fix. we should advise every other fc9 user on this issue, but i dunno how... posting on a widely read mlist, like bugtraq, maybe -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
On Sun, 15 Jun 2008 08:45:56 +0100 Brian Morrison <[EMAIL PROTECTED]> wrote: > On Sun, 15 Jun 2008 11:52:31 +0800 > Tony Frame <[EMAIL PROTECTED]> wrote: > > > I had the same problem on 2 out of 3 F9 machines recently updated. Fixed > > it by booting from Live CD / USB and running grub and doing the > > following : > > > > >root (hd0,0) > > >setup (hd0) > > >quit > > > > then re-booting (guess you should check hd0 is your boot device first). > > > > It's also the first time I've had this problem since starting with RH7. > > Sounds like someone needs to bugzilla it then, this really shouldn't > happen. Had I been on the road without an F9 DVD to hand it would have > been a lot more difficult to fix. > Seems there is already a bug open about this sort of behaviour: https://bugzilla.redhat.com/show_bug.cgi?id=450143 -- 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." -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
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 defaults1 1 UUID=22309ffe-0180-41bd-a868-9d5b15660781 /home ext3 defaults1 2 UUID=c46f0b8e-ea34-47f5-8c7f-57a7f3a5d531 /boot ext3 defaults1 2 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 UUID=817d341a-8daa-43dd-8c97-2eea4c1f418f swapswap defaults0 0 i restored it to: [09:34:12 [EMAIL PROTECTED] /var/log ]# cat /etc/fstab /dev/VolGroup00/LogVol00 / ext3defaults1 1 /dev/VolGroup00/LogVol02 /home ext3defaults1 2 /dev/sda1 /boot ext3defaults1 2 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 /dev/VolGroup00/LogVol01 swapswapdefaults0 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
Re: Recent updates caused Grub installation to be damaged?
On Sun, 15 Jun 2008 11:52:31 +0800 Tony Frame <[EMAIL PROTECTED]> wrote: > I had the same problem on 2 out of 3 F9 machines recently updated. Fixed > it by booting from Live CD / USB and running grub and doing the > following : > > >root (hd0,0) > >setup (hd0) > >quit > > then re-booting (guess you should check hd0 is your boot device first). > > It's also the first time I've had this problem since starting with RH7. Sounds like someone needs to bugzilla it then, this really shouldn't happen. Had I been on the road without an F9 DVD to hand it would have been a lot more difficult to fix. -- 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." -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
On Sat, 2008-06-14 at 18:31 -0400, Sam Varshavchik wrote: > Brian Morrison writes: > > > I updated this morning for the new kernel plus another 30 or so updates. > > > > After rebooting, I got a screen that read just GRUB, then nothing. > > > > Initially I thought that the device.map file might have been the > > problem, it had an entry for fd0 in it as the first device, then hd0 > > as /dev/sda. I edited the file to remove the fd0 entry and tried again, > > but still the same result. In the end I re-installed grub again and got > > the correct stage 1.5 message before the Grub screen came up. > > Generally, editing device.map is not enough. /sbin/grub-install must be > invoked to reinitialize the bootloader using the updated device.map file. > So, your changes to device.map didn't take effect until you reinstalled > grub. > > > Has anyone else had problems of this nature on updates recently? I > > suppose this could have been a glitch but I've never had a boot sector > > damaged before in this way in all the time I've been using Redhat and > > Fedora, > > Not with the most recent set of updates, but both of my servers that use > softraid ended up getting a busted grub configuration installed by F9's > anaconda, when I upgraded from F8. > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list I had the same problem on 2 out of 3 F9 machines recently updated. Fixed it by booting from Live CD / USB and running grub and doing the following : >root (hd0,0) >setup (hd0) >quit then re-booting (guess you should check hd0 is your boot device first). It's also the first time I've had this problem since starting with RH7. Apart from updating the kernel to 2.6.25.4-30.fc9.i686, the only other thing I can recall changing was to install Google Earth (only on the 2 machines that had problems) ... but seems unlikely that would upset the boot loader. Tony -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
Brian Morrison writes: I updated this morning for the new kernel plus another 30 or so updates. After rebooting, I got a screen that read just GRUB, then nothing. Initially I thought that the device.map file might have been the problem, it had an entry for fd0 in it as the first device, then hd0 as /dev/sda. I edited the file to remove the fd0 entry and tried again, but still the same result. In the end I re-installed grub again and got the correct stage 1.5 message before the Grub screen came up. Generally, editing device.map is not enough. /sbin/grub-install must be invoked to reinitialize the bootloader using the updated device.map file. So, your changes to device.map didn't take effect until you reinstalled grub. Has anyone else had problems of this nature on updates recently? I suppose this could have been a glitch but I've never had a boot sector damaged before in this way in all the time I've been using Redhat and Fedora, Not with the most recent set of updates, but both of my servers that use softraid ended up getting a busted grub configuration installed by F9's anaconda, when I upgraded from F8. pgpmM2RUvbtXj.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
