console errors about modules
Bug #525994 reported by
Dustin Kirkland
This bug report is a duplicate of:
Bug #525989: Eucalyptus runs images without ramdisk with a default ramdisk.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cloud-init
These appear benign, I think, as the image does boot, and I can ssh to it. I suspect this is due to our initramdisk-less running mode?
We could probably clean up our init a bit, to look a little less ominous.
Console log attached.
To post a comment you must log in.
The module errors you see in the log (copied below) there are evidence of my discovery in bug 525989 . The reason is you ended up booting with a karmic (or some other) ramdisk that did not have a /lib/modules/ 2.6.32- 14-server . Instead, it had a /lib/modules/ <kernel- version- that-it- was-built- for> .
WARNING: Couldn't open directory /lib/modules/ 2.6.32- 14-server: No such file or directory 2.6.32- 14-server/ modules. dep.temp for writing: No such file or directory 2.6.32- 14-server/ modules. dep: No such file or directory 2.6.32- 14-server/ modules. dep: No such file or directory 2.6.32- 14-server/ modules. dep: No such file or directory
FATAL: Could not open /lib/modules/
Couldn't get a file descriptor referring to the console
Begin: Loading essential drivers... ...
FATAL: Could not load /lib/modules/
FATAL: Could not load /lib/modules/
FATAL: Could not load /lib/modules/