Comment 79 for bug 525154

After Etienne and Clint said this problem is most easily reproduced by a slow fsck - I checked and I do appear to have filesystems unmounted uncleanly. So I'll investigate that as a separate issue (when I find out how to get my shutdown messages recorded to log). I'm certainly experiencing shutdowns that are very quick compared to my last install in Hardy Heron.

/var/log/boot.log:

fsck from util-linux-ng 2.17.2
...etc...
init: statd main process (920) terminated with status 1
init: statd main process ended, respawning
init: statd main process (930) terminated with status 1
...etc...
/dev/sda1: recovering journal
init: statd main process (987) terminated with status 1
init: statd main process ended, respawning
/dev/mapper/ubuntu01vg-homelv: recovering journal
init: statd main process (993) terminated with status 1
init: statd respawning too fast, stopped
/dev/mapper/ubuntu01vg-usermedialv: clean, 12/610800 files, 76473/2441216 blocks
/dev/mapper/ubuntu01vg-usrlv: recovering journal
/dev/mapper/ubuntu01vg-varlv: recovering journal
/dev/mapper/ubuntu01vg-rootlv: clean, 13556/183264 files, 148953/732160 blocks
/dev/mapper/ubuntu01vg-tmplv: recovering journal
/dev/mapper/ubuntu01vg-usrlocallv: clean, 43/60928 files, 8262/243712 blocks (check in 3 mounts)
init: ureadahead-other main process (1040) terminated with status 4
/dev/mapper/ubuntu01vg-tmplv: clean, 785/121920 files, 35321/487424 blocks
init: ureadahead-other main process (1061) terminated with status 4
init: mounted-tmp main process (1062) terminated with status 127
mountall: Event failed
...etc...