On Tue, 2010-10-26 at 20:31 +0000, Ainsley Harewood wrote: > After I tried to > reboot and got unreadahead main process (336) terminated with status 5 > and after that it just doesnt complete the booting process.
Right. This is a known and common problem. It's not caused by ureadahead though. Yes, ureadahead does complain when /var is on a separate filesystem but it doesn't prevent booting anyway. What is preventing your booting is just not displaying any messages about it. But again, it's not ureadahead. ureadahead's message just happens to be the last thing printed before whatever else is preventing your boot from completing breaks. > I am pretty sure that its /var because I installed it like half hour > before and didnt put var on a separate partition and it worked > perfectly. You are misunderstanding me. I am not saying your /var is NOT on a separate filesystem. I'm just saying that ureadahead is not preventing your system from booting. -- ureadahead requires /var on root filesystem https://bugs.launchpad.net/bugs/523484 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
