Ubuntu
cloud-init package

console errors about modules

Bug #525994 reported by Dustin Kirkland  on 2010-02-22

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.

Revision history for this message

Dustin Kirkland  (kirkland) wrote on 2010-02-22:

console.log Edit (58.9 KiB, text/plain)

Revision history for this message

Scott Moser (smoser) wrote on 2010-02-23:

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
FATAL: Could not open /lib/modules/2.6.32-14-server/modules.dep.temp for writing: No such file or directory
Couldn't get a file descriptor referring to the console
Begin: Loading essential drivers... ...
FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory

Revision history for this message

Scott Moser (smoser) wrote on 2010-02-24:

I marked this as a duplicate of bug 525989. The reason is that the module errors listed above come from mis-matched kernel/ramdisk as a result of the "default ramdisk"