Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 826781 - 'File Not Found' on startup
Summary: 'File Not Found' on startup
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 00:06 UTC by Ben Greear
Modified: 2012-06-03 23:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-31 00:26:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ben Greear 2012-05-31 00:06:49 UTC 
Description of problem:

When booting F17 with grub2, I see 3 'File Not Found' errors
but then it loads the kernel and works (when using the standard
linux kernels that come with F17).

I did a preupgrade from F16 in case that matters.


Version-Release number of selected component (if applicable):

Fedora 17.

How reproducible:

Always, at least in this install.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mads Kiilerich 2012-05-31 00:11:13 UTC 
preupgrade is apparently broken in several ways and will fail to configure the boot loader properly.

Please try
  grub2-install /dev/sdX
  grub2-mkconfig /boot/grub2/grub.cfg
and see if that makes the problem go away.

Remember to take a backup of /boot if you would like to have a backup.
Comment 2 Ben Greear 2012-05-31 00:20:06 UTC 
Yes, that makes the errors go away.  I still can't boot a custom kernel (hangs before the services start), but at least no grub2 error messages, and the standard F17 kernel boots fine.
Comment 3 Mads Kiilerich 2012-05-31 00:26:01 UTC 
That is a strong evidence that whatever it was, it wasn't a grub2 issue. You can try to check the open preupgrade bugs and see if you can add something there or find answers ... or if you should file a preupgrade issue.
Comment 4 Hin-Tak Leung 2012-06-01 01:57:12 UTC 
(In reply to comment #3)
> That is a strong evidence that whatever it was, it wasn't a grub2 issue. You
> can try to check the open preupgrade bugs and see if you can add something
> there or find answers ... or if you should file a preupgrade issue.

I have the same problem - I still would like to know what went wrong instead of just doing comment 1 to make the problem go away. What can I try before I proceed to get rid of the problem?
Comment 5 Mads Kiilerich 2012-06-01 09:27:33 UTC 
preupgrade did not install a new boot loader ... and patching the existing one with grubby also failed.
Comment 6 Hin-Tak Leung 2012-06-01 11:18:12 UTC 
(In reply to comment #5)
> preupgrade did not install a new boot loader ... and patching the existing
> one with grubby also failed.

But it still 'works' - the new kernel is operational, just with mysterious error messages during grub/dracut?
Comment 7 Hin-Tak Leung 2012-06-02 02:48:44 UTC 
I think this is a bug with preupgrade - it does not put the latest grub2 under /boot .
Comment 8 Hin-Tak Leung 2012-06-03 23:39:01 UTC 
Filed 
"Bug 827987 - preupgrade does not run grub2-install"
and attached my /boot before grub2-install to fix it, and it worked.

Encountered "Bug 817187 - GRUB2 error: file '/boot/grub2/locale/en.mo.gz' not found" after getting rid of the three no-name error lines. That is trivially worked around by copying one file over (https://bugzilla.redhat.com/show_bug.cgi?id=817187#c5).
Note You need to log in before you can comment on or make changes to this bug.