Ubuntu
mountall package

Karmic system fails to boot

Bug #433494 reported by Claudio Matsuoka on 2009-09-20

This bug report is a duplicate of: Bug #430542: lvm volumes fail to mount when specified as /dev/vg-name/volume. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	mountall (Ubuntu)	Incomplete	High	Scott James Remnant (Canonical)

Bug Description

Binary package hint: upstart

Karmic i386 system with up-to-date packages fails to boot after mountall (kernel 2.6.31-10) or presumably network start (kernel 2.6.30-2). In the latter case the system remains silent with no clear error indication when booting without splash, console input remains reponsive. With kernel 2.6.31-10 mountall complains about missing /proc/self/mountinfo and segfaults.

In both cases it's possible to boot with init=/bin/bash, and after performing some manual maintenance it's possible to bring up networking and upgrade to latest packages. Current versions are: upstart 0.6.3-3, initscripts 2.87dsf-4ubuntu5, mountall 0.1.6.

I tried to further diagnose utilities by running them by hand but couldn't do much because many of them require the upstart socket to be in place. A way to simulate system startup step by step could help to find what is breaking the boot process.

Revision history for this message

Claudio Matsuoka (cmatsuoka) wrote on 2009-09-20:

When booting with kernel 2.6.30-2, last message displayed before the system hangs is the NTP start message (possibly when eth0 goes up).

arno_b (arno.b) on 2009-09-20

tags:

added: ubuntu-boot

Revision history for this message

Claudio Matsuoka (cmatsuoka) wrote on 2009-09-20:

A few more pieces of information that might be useful:

By placing trace data in upstart scripts, it seems that the mountall job is correctly executed, but the rc-sysinit job isn't, even with the actual mounting command commented out (so it's not hanging inside the mounting process). Note that the mountall job emits the filesystem event and rc-sysinit is supposed to start on filesystem.

Revision history for this message

Frans van Berckel (fberckel) wrote on 2009-09-21:

Is bug #427356 related?

Rick Spencer (rick-rickspencer3) on 2009-09-21

Changed in upstart (Ubuntu):
importance:	Undecided → Critical
assignee:	nobody → Scott James Remnant (scott)

Robbie Williamson (robbiew) on 2009-09-21

Changed in upstart (Ubuntu):
importance:	Critical → High
tags:	removed: ubuntu-boot

Robbie Williamson (robbiew) on 2009-09-21

Changed in upstart (Ubuntu):
assignee:	Scott James Remnant (scott) → Canonical Foundations Team (canonical-foundations)

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2009-09-22:

Claudio: please provide your /etc/fstab

affects:	upstart (Ubuntu) → mountall (Ubuntu)
Changed in mountall (Ubuntu):
assignee:	Canonical Foundations Team (canonical-foundations) → Scott James Remnant (scott)
status:	New → Incomplete

Revision history for this message

Claudio Matsuoka (cmatsuoka) wrote on 2009-09-23:

fstab file Edit (693 bytes, text/plain)

fstab attached. It is a bit uncommon and has a few lvm devices. When tracing the system initialization I tried to stop the mountall job (via sulogin) and initialized and mounted all filesystems manually before continuing, and also tried commenting out all lvm devices in fstab. In both cases the rc-sysinit job was (apparently) not executed.

I was able to bring the system up to a usable state by dropping to a shell from the mountall job and then starting udev, mounting filesystem, starting dbus, hal, modprobing a few modules (evdev, agp-intel), mounting /dev/pts, going to runlevel 2 and starting the display manager.

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2009-09-23: Re: [Bug 433494] Re: Karmic system fails to boot

duplicate 430542

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message

Claudio Matsuoka (cmatsuoka) wrote on 2009-09-23:

Please note that the upstart bug with rc-sysinit not running happens even if all lvm volumes are removed from fstab.

Revision history for this message

Claudio Matsuoka (cmatsuoka) wrote on 2009-09-24:

Confirmed described symptoms still present with upstart 0.6.3-4, initscripts 2.87dsf-4ubuntu7 and all lvm volumes removed from fstab.

Revision history for this message

Cyril Jaquier (cyril-jaquier) wrote on 2009-10-24:

I have a similar issue (rc2.d scripts not being executed) since many weeks. I opened bug #453473.

I tried this after boot:

$ sudo start rc-sysinit
rc-sysinit stop/waiting

and also:

$ sudo initctl emit filesystem

but without success. No scripts in rc2.d is executed. I have no /etc/inittab and do not use LVM at all.

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda2
UUID=8077df6b-eb0e-40ff-9a4e-acbf5205d4a7 / ext4 noatime,errors=remount-ro 0 1
# /dev/sda1
UUID=805e5e3d-bc79-47c8-86b7-f81d91a08d49 /boot ext2 noatime 0 2
# /dev/sda3
UUID=478583d0-b995-4aaf-b416-4a47a283a52b none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0