Bug 488259
Summary: | grub does not want to boot after yum update. Shows "GRUB" in the top left corner. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rick Richardson <rickrich> |
Component: | grub | Assignee: | Peter Jones <pjones> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | bugs.michael, kyleki, pjones |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-29 15:31:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rick Richardson
2009-03-03 15:32:18 UTC
On Tuesday (03/03/2009 at 09:20AM -0600), Rick Richardson wrote: > On Tue, Mar 03, 2009 at 09:07:00AM -0600, Rick Richardson wrote: > > > > [rick@kathleen ~]$ root yum update > > {snip} > > kernel.i686 0:2.6.27.19-170.2.35.fc10 > > {snip} > > Complete! > > [rick@kathleen ~]$ root init 6 > > > > Did not come up; When I went to check on it, it says: > > > > GRUB > > > > In the top left corner... Thats it... > > Booted CD, selected Rescue Disk, then > > # chroot /mnt/sysimage > # grub-install /dev/sda > > Reboot. > Everything is normal again. I had to do the EXACT same thing on a laptop I updated on Sunday. But other platforms I have updated at the same time had no such issue. chris > On Tuesday (03/03/2009 at 11:01AM -0600), Rick Richardson wrote:
> > # yum update
> > # grub-install /dev/sda
> > # init 6
I did this on rick-laptop today. No problem and I didn't have to boot the rescue CD like for kathleen's desktop yesterday. Don't know why grub-install isn't getting called or is buggy on some desktops or laptops.
*** This bug has been marked as a duplicate of bug 450143 *** |