I went through one more install/upgrade cycle and found that a) there appears to be no significant configuration changes in /etc that would be likely to cause this problem, and b) reformatting /var doesn't appear to be necessary during a reinstall to clear up the Waiting for /var hang. That seems to indicate that the problem is in one of the 570+ packages that get upgraded with an apt-get dist-upgrade applied to alpha2. Since the only visible major changes between the working pre-update boot sequence and the broken post-update changes are the uvcvideo error (unlikely) and the missing fsck startup, the problem seems likely to be either with fsck or the process which invokes it during init fs mounting.
I'm not sure how to figure out how upstart is starting up file system mounting. The only reference to fsck that I've seen is in /etc/init/mountall.conf. At first glance it would seem mountall shouldn't be trying to run fsck before mounting file systems since mountall has a parameter to force that action, but maybe that's for forcing a full check and it's calling fsck to increment a mount count by default. That would seem to make mountall and e2fsck the most likely suspected culprits for my woes. So I'll try to see if I can grab a copy of the Alpha2 versions of those packages and try to roll back to them after the dist-upgrade. I'm just wondering if I need to rebuild them after the new kernel and headers are installed by dist-upgrade but before rebooting. If anybody knowledgeable would be willing to give me some pointers, or even encouragement that I'm looking in the right direction if that's finally the case, I'd really appreciate it. -- system hangs on reboots after upgrading lucid alpha 2 hal packages https://bugs.launchpad.net/bugs/524135 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
