Comment 8 for bug 483359

Thanks for the sudo touch /forcefsck tip.
Doing that didn't cause the problem, it ran fsck normally and then booted up normally, which i don't really understand why.
I can't really tell if its related to any other bugs, googling ureadahead status 4 just gives me the impression that it is just a warning...