My Ubuntu HD-installation system just refuses to go further after all fstab entries are mounted.
The last several line on the boot up screen are:

Then nothing else, even after 10 more minutes. Booting into single mode stops at the same spot as well.

The system booted up just fine this morning, and I did a normal shut down. Only thing worth to mention is that I booted into WinXP once afterwards, and before this. Nothing else.

Detailed symptoms:

I use text boot (without 'quite splash'). Boot console has already switched to graphical framebuffer. Watching the text boot, it gets past fscking each of my linux-readable partitions and then stops at "ureadahead-other process (###) terminated with status 4".

I can ALT-F? to switch ttys and I can use CTL-ALT-DEL to reboot, so the machine isn't hard locked up... but that's it.

The symptom has nothing to do with fsck because I've booted into my livecd and fsck every partitions.

I can load the livecd, and mount the hard drive and chroot to it successfully.

Any help please?

What's the next step in normal boot after fscking partitions?

1. Check logs in /var/log.
2. Try CTRL+C and CTRL+D after that message.
3. Try removing ureadahead:

Thanks for the respond.

> 1. Check logs in /var/log.

No logs. not a single log is being written to the hard drive. The latest log entry was that of this morning.

> 2. Try CTRL+C and CTRL+D after that message.

That's interesting. I'll give it a try...
Nope, neither works.

> 3. Try removing ureadahead:

OK, will do that. But ureadahead is not the reason because

- I always get that, even during normal boot ups.
- I've disabled it via

mv /etc/init/ureadahead.conf /etc/init/ureadahead.conf.disable
mv /etc/init/ureadahead-other.conf /etc/init/ureadahead-other.conf.disable

Then the ureadahead-other never show up again, but the system still hung there.

Without logs it will be difficult to say something. It can be anything. Maybe paste here your /etc/fstab. If you don't see login prompt, so filesystems wasn't mounted.