system fails to boot without ramdisk and incorrect / in fstab
Bug #509841 reported by
Scott Moser
This bug report is a duplicate of:
Bug #513919: Can't spawn jobs without /dev/null breaks mountall-dev which would create it; aka mountall: Event failed.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
Binary package hint: upstart
I'm trying to boot a system without a ramdisk. bug 503212 was fixed, so we no longer have mountall sigsegv, but we still fail to boot.
I'm attaching boot logs with '--debug', and then will give some comments on the differences.
ProblemType: Bug
Architecture: amd64
Date: Tue Jan 19 20:56:43 2010
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.3-11
ProcEnviron: SHELL=/bin/bash
ProcVersionSign
SourcePackage: upstart
Tags: lucid
Uname: Linux 2.6.32-10-server x86_64
To post a comment you must log in.
I filtered the 2 attached files above through a sed, sort, and uniq -u to find which lines were only in each log.
The output is attached here. Obviously, the boot with ramdisk has lots of messages as it gets further along.
The things that I thought were interesting in this attachment were:
a.) only the noramdisk boot has messages with: interface (eth0) interface (lo)
network-
and
network-
I don't know why these would not be present in the ramdisk log.
b.) The 'filesystem' and 'local-filesystem' boot event is not ever emitted from mountall in the noramdisk boot.
most of the other messages in successful boot depend on local-filesystem or filesystem