From the bug description, this sounds like an issue with the karmic
mountall where it would continue when it shouldn't - this has been fixed
in Lucid
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
Startup in Karmic with unclean filesystems leaves system in a wrong state
Is this behavior really by design? If so, it is a very bad one. By
default, the system should wait until all file systems are available
before letting the user log in. Otherwise, the user can suffer data loss
as follows:
1) Boot with unmounted file systems. The mount points will look like empty
If I drop to the shell I can let the fsck finish and start the X environment
manually (just as a work around).
If I don't do anything I can login via the GUI, but since my home directory is
not ready by then I just get an empty desktop and a warning dialog like
cannot access home directory,
Why is dropping to a shell a good solution? Doesn't the fsck eventually
finish and then you can access your separate partition? It seems much
better to give the user a fast boot and most of their desktop (sans
corrupted home directory) than to just give them a shell with no home
directory.
**
