Bug 750449 - Could not load /lib/modules/`uname -r`/modules.dep
Summary: Could not load /lib/modules/`uname -r`/modules.dep
Keywords:
Status: CLOSED DUPLICATE of bug 1014954
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: x86_64
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 846704 972747
TreeView+ depends on / blocked
 
Reported: 2011-11-01 08:14 UTC by Petr Beňas
Modified: 2016-08-26 02:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-26 02:08:07 UTC
Target Upstream Version:


Attachments (Terms of Use)
Screenshot of the failed boot (32.73 KB, image/png)
2011-11-01 08:15 UTC, Petr Beňas
no flags Details

Description Petr Beňas 2011-11-01 08:14:49 UTC
Description of problem:
System cannot boot after fresh installation with following error:
FATAL: Could not load /lib/modules/2.6.32-214.el6.x86_64/modules.dep: No such file or directory

Version-Release number of selected component (if applicable):
RHEL6.2-20111026.2_nfs-Server-x86_64*
RHEL6.2-20111030.n.0_nfs-Server-x86_64*

How reproducible:
three times in a row in a kvm guest

Steps to Reproduce:
1. Install one of mentioned RHEL6.2 versions as a kvm guest, used PXE install
Tried basic server and minimal installation, tried using LVM or just simple one partition - reproducible in all cases.
3. Reboot the machine after successfull install 
  
Actual results:
Failure like on attached screenshot. 

Expected results:
System boots.

Additional info:
Probably initrd broken?

Comment 1 Petr Beňas 2011-11-01 08:15:39 UTC
Created attachment 531077 [details]
Screenshot of the failed boot

Comment 2 Petr Beňas 2011-11-01 08:20:41 UTC
One more additional info, qemu-kvm version used was qemu-kvm.x86_64 2:0.12.1.2-2.200.el6.

Comment 5 RHEL Program Management 2011-11-06 06:47:13 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-12-14 07:40:39 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 9 Pavel Holica 2013-10-03 08:24:19 UTC
I've just found that this may be caused by having two ramdisks in one boot entry: bug 1014954

Comment 10 RHEL Program Management 2013-10-14 05:10:31 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 12 Linda Wang 2016-08-26 02:08:07 UTC

*** This bug has been marked as a duplicate of bug 1014954 ***


Note You need to log in before you can comment on or make changes to this bug.