Partitions not unmounted correctly

If you are using Ubuntu, please file a bug in the Ubuntu bug tracker rather than on the upstream project.

I don't think there's an actual filesystem checking issue here, I think you're just being confused by the text being briefly visible as the X server is started.

(usplash bug should be the open one - since the text transition is the real issue)

How can I move this bug to this project? If I use "Also affects project" the name "ubuntu" isn't accepted, what name do I have to put in there?

Just forget about my previous post. I think it's a file system issue since the message says that it tries to recover the journal?!

I'm having what is probably the same problem as the original poster. I have two machines doing this after an upgrade to Lucid (10.04). There was no problem under karmic. On each I have around 6 file systems to mount. They are a mixture of non-raid normal partition ext3 file systems and RAID 1 ext3 file systems. On boot there will always be some "recovering journal" messages but it will happen on different combinations of file systems each boot.

To try and work out if it was a boot or previous shutdown problem, I shut down, booted from the live CD and ran dumpe2fs on all the filesystems. I then rebooted and stored the boot.log

In the output to dumpe2fs, some of the file systems had the following line:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file

A typical boot.log is attached.

Sorry, here's the attachment.

By the way, perhaps usplash is effected by this but it isn't the core of the problem. The problem appears to be file systems that are not umounted properly on the previous shutdown.

I suspect the fault lies in upstart somewhere.

For further information, the screen output on a "shutdown -H now" gives the following (srooy, I'm typing it out from a dead screen)

acpid: exiting

init: tty4 main process (1398) killed by TERM
... for tty5,2,3,6,1 and cron
 * Stopping MTA
 * Stopping MD monitoring service mdadm --monitor
nxsensor is disabled in '/usr/NX/etc/node.cfg'
init: avahi-daemon main process (1460) terminated with status 255
modem-manager: Caught signal 15, shutting down...
init: Disconnect from system bus
NX> ..... (a number of NX debug)
 * Stopping internet superserver inetd
Stopping Linux Video Disk Recorder: vdr - seems not to be running.
 * Will now halt
[ 144.272829] System halted.

Sorry, didn't mean to change this

Ok, I'll take some of my comments back. The problem lies in the init scripts and the sequence numbers / priorities on the link. On my upgraded systems, /etc/rc0.d looks like this:
lrwxrwxrwx 1 root root 26 2010-04-13 12:51 K01clamav-freshclam -> ../init.d/clamav-freshclam
lrwxrwxrwx 1 root root 16 2010-04-13 12:51 K01dhcdbd -> ../init.d/dhcdbd
lrwxrwxrwx 1 root root 16 2010-05-20 15:21 K01distcc -> ../init.d/distcc
lrwxrwxrwx 1 root root 14 2010-04-13 12:51 K01ferm -> ../init.d/ferm
lrwxrwxrwx 1 root root 17 2010-04-13 12:51 K01hddtemp -> ../init.d/hddtemp
lrwxrwxrwx 1 root root 20 2010-04-13 12:51 K01kerneloops -> ../init.d/kerneloops
lrwxrwxrwx 1 root root 21 2010-04-13 12:51 K01laptop-mode -> ../init.d/laptop-mode
lrwxrwxrwx 1 root root 15 2010-04-13 12:51 K01mdadm -> ../init.d/mdadm
lrwxrwxrwx 1 root root 27 2010-04-13 12:51 K01nfs-kernel-server -> ../init.d/nfs-kernel-server
lrwxrwxrwx 1 root root 18 2009-10-07 10:37 K01nxsensor -> ../init.d/nxsensor
lrwxrwxrwx 1 root root 18 2009-10-07 10:37 K01nxserver -> ../init.d/nxserver
lrwxrwxrwx 1 root root 23 2010-04-13 12:51 K01openbsd-inetd -> ../init.d/openbsd-inetd
lrwxrwxrwx 1 root root 17 2010-04-13 12:51 K01openvpn -> ../init.d/openvpn
lrwxrwxrwx 1 root root 17 2010-04-13 12:51 K01postfix -> ../init.d/postfix
lrwxrwxrwx 1 root root 14 2010-04-13 12:51 K01vtun -> ../init.d/vtun
lrwxrwxrwx 1 root root 17 2010-04-13 12:51 K01winbind -> ../init.d/winbind
lrwxrwxrwx 1 root root 13 2010-05-20 15:01 K01xdm -> ../init.d/xdm
lrwxrwxrwx 1 root root 15 2010-04-13 12:51 K02mysql -> ../init.d/mysql
lrwxrwxrwx 1 root root 19 2010-04-13 12:51 K03mysql-ndb -> ../init.d/mysql-ndb
lrwxrwxrwx 1 root root 23 2010-04-13 12:51 K04mysql-ndb-mgm -> ../init.d/mysql-ndb-mgm
lrwxrwxrwx 1 root root 17 2010-05-20 15:21 K08apache2 -> ../init.d/apache2
-rw-r--r-- 1 root root 353 2009-09-08 04:58 README
lrwxrwxrwx 1 root root 14 2010-04-13 12:51 S01halt -> ../init.d/halt
lrwxrwxrwx 1 root root 20 2010-05-20 15:01 S01networking -> ../init.d/networking
lrwxrwxrwx 1 root root 18 2010-04-13 12:51 S01sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 18 2010-04-13 12:51 S01umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 22 2010-04-13 12:51 S01umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 20 2010-04-13 12:51 S01umountroot -> ../init.d/umountroot
lrwxrwxrwx 1 root root 29 2010-04-13 12:51 S01unattended-upgrades -> ../init.d/unattended-upgrades
lrwxrwxrwx 1 root root 17 2010-05-20 15:01 S02urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 2010-04-13 12:51 S02wpa-ifupdown -> ../init.d/wpa-ifupdown
lrwxrwxrwx 1 root root 26 2010-05-20 15:01 S04cryptdisks-early -> ../init.d/cryptdisks-early
lrwxrwxrwx 1 root root 20 2010-05-20 15:01 S06cryptdisks -> ../init.d/cryptdisks

On a fresh install it looks like this:
lrwxrwxrwx 1 root root 24 2010-05-20 21:30 K08vmware-tools -> /etc/init.d/vmware-tools
lrwxrwxrwx 1 root root 19 2010-05-20 21:14 K74bluetooth -> ../init.d/bluetooth
-rw-r--r-- 1 root root 353 2009-09-07 11:58 README
lrwxrwxrwx 1 root root 29 2010-05-20 21:14 S10unattended-upgrades -> ../init.d/unattended-upgrades
lrwxrwxrwx 1 root root 22 2010-05-20 21:14 S...

My last update for the day.

After fixing the sequence numbers, the shutdown at least took longer and stopped some services. However it seems the rc scripts are run in parallel with upstart finishing other services. In particular the rc scripts shut down the network before autofs (/automount/autofs5) hung around which in turn blocked umount of most local file systems. Meanwhile the rc scripts executed the halt. I'm new to all this so perhaps I misunderstand. But it seems that the rc scripts are started when upstart is still cleaning up other services and there is a strong chance the machine will execute halt before everything is finished.

I'm hoping I'm wrong and someone can explain how this works.

I noticed that the installation of VMware-Tools (VMware-Tools-4.0.0-236512 for ESX 4.0 in my case) causes that the sequence numbers of rc0 and rc6 changes. Before the installation halt is linked with S90halt, after the installation it is S01halt.

This is the log when installing the VMware-Tools. There are several lines like this:

insserv: warning: current start runlevel(s) (0) of script `halt' overwrites defaults (empty).

OK - here is how you can reproduce this:

root@ubuntutpl:~# cat /etc/init.d/testinit
#!/bin/sh
### BEGIN INIT INFO
# Provides: test
# Required-Start: $local_fs
# Required-Stop: $local_fs
# X-Start-Before: $network
# X-Stop-After: $network
# Default-Start: 2 3 5
# Default-Stop: 0 6
### END INIT INFO

root@ubuntutpl:~# ls -l /etc/rc0.d/
total 1
-rw-r--r-- 1 root root 353 2009-09-07 20:58 README
lrwxrwxrwx 1 root root 22 2010-05-21 19:18 S15wpa-ifupdown -> ../init.d/wpa-ifupdown
lrwxrwxrwx 1 root root 18 2010-05-21 19:16 S20sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 17 2010-05-21 19:16 S30urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 2010-05-21 19:16 S31umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 20 2010-05-21 19:16 S35networking -> ../init.d/networking
lrwxrwxrwx 1 root root 18 2010-05-21 19:16 S40umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 20 2010-05-21 19:16 S60umountroot -> ../init.d/umountroot
lrwxrwxrwx 1 root root 14 2010-05-21 19:16 S90halt -> ../init.d/halt
root@ubuntutpl:~# insserv /etc/init.d/testinit

[ alot of insserv warnings ]

root@ubuntutpl:~# ls -l /etc/rc0.d/
total 1
-rw-r--r-- 1 root root 353 2009-09-07 20:58 README
lrwxrwxrwx 1 root root 14 2010-05-21 20:01 S01halt -> ../init.d/halt
lrwxrwxrwx 1 root root 20 2010-05-21 20:01 S01networking -> ../init.d/networking
lrwxrwxrwx 1 root root 18 2010-05-21 20:01 S01sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 18 2010-05-21 20:01 S01umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 22 2010-05-21 20:01 S01umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 20 2010-05-21 20:01 S01umountroot -> ../init.d/umountroot
lrwxrwxrwx 1 root root 17 2010-05-21 20:01 S02urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 2010-05-21 20:01 S02wpa-ifupdown -> ../init.d/wpa-ifupdown

I found a workaround. Before installing the VMware-Tools I rename /sbin/insserv to /sbin/insserv.bak - then the VMware-Tools installer uses update-rc.d as a fallback. After the installation I rename /sbin/insserv.bak back to /sbin/insserv .

The usplash package has been superseded by plymouth and has been removed from the Ubuntu archive. Closing all related bugs.