Comment 25 for bug 439604

1. It would be nice to get a list of which things do get blocked for -is there a way of asking mountall itself? I am still trying to understand all of this

2. The root cause was the laptop crashing on resume (unrelated), meaning that an fsck was needed; I think this was delaying stuff. It was exhibiting sometimes as the splash screen bringing up a message under the alert saying "could not mount /home and its UUID", then later on as X not coming up, no /home. All you get is the console. Would the fsck be locking the disck causing X to fall over?

I'm wondering if referencing disks by UUID is causing trouble; on the other machine I couldn't boot with root=UUID=something, editing menu.lst to have root=/sda1 fixed that -again, it shouldn't happen, but it was needed. And no, I don't have quotes around UUID in fstab.