On further investigation, it appears that no *actual* fsck is being
performed when I get this error.
When I use /forcefsck, it returns 0.1% non-contiguous after a short
delay, and boots normally.
When my boot stalls with a fsck message, no vterms, but sshd active, on
the connected display it retu
I'm getting the same issue on Server 10.04 LTS.
Installing mountall 2.15 appeared to fix the issue, but it has returned.
touch /forcefsck does not cause the issue - it only appears without
interference (seemingly). I also noticed it started occuring again when
the fsck on boot reports 'clean' as
