Sigh, this still happens after all. It just doesn't seem to always happen right away after an update. Sometimes it needs a few reboots, but once it happens I can't seem to clear it up without reinstalling Alpha 2 (also appear to need to wipe at least my root partition). I've lost count of how many reinstalls I've had to do, but it's over 5. After my first re-install of 10.4 Alpha 2, it's been /var that's been hanging, not /tmp. I just get the ubuntu logo and "Waiting for /var [SM]" underneath. Before that logo I see an error about uvcvideo, followed by the results of e2fscks for root, /boot. /home, /tmp, but not /var. I'm also seeing the ureadahead errors indicated in bug #484677 but those go away after applying the "start on local-filesystems" change indicated in bug #432360. None of those changes appear to fix the issue with the wait for /var. If I boot from the Alpha 2 Alternative CD (running RAID and LVM) and use the rescue mode, I can run fsck on /var with no problems.
That said, if the init startup order did change, as is implied in 484677, then could it be that there is now something starting up earlier which is placing a lock on /var and preventing the fsck from running somehow? What is running those fscks anyways? It doesn't look like mountall should be doing it by default but something is. I no longer think this is hal -related since it seems to happen before hald ever starts, but I'm not sure what it is related to. init scripts? Can anybody help me out to figure out what's breaking here? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
