Note that you can get around the recovery shell by using the
nobootwait option it /etc/fstab for /home.
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
Inconsistent error message: Filesystem could not be mounted
https://bugs.launchpad.net/bugs/504224
You received this bug
** Description changed:
Binary package hint: mountall
karmic: mountall 1.0
- When mounting NFS shares at boot, there is always an error for each mount
point:
- mountall: Filesystem could not be mounted:
- These errors appear, even when the filesystem will be mounted.
- They also
** Tags added: ubuntu-boot-experience
** Tags added: boot-experience
** Tags removed: ubuntu-boot-experience
** Tags added: ubuntu-boot-experience
** Tags removed: boot-experience
--
Inconsistent error message: Filesystem could not be mounted
https://bugs.launchpad.net/bugs/504224
You received
For clarification, if this is the same thing I'm having it's preventing
my machine from booting.
I have about 10 NFS mounts, and my machine hangs on boot with the above
printouts.
To work around this, and boot into X so I can log in, I can enter the
recovery shell, do mount -a, and exit the
On Thursday 07 January 2010 14:47:33 Johan Walles wrote:
For clarification, if this is the same thing I'm having it's preventing
my machine from booting.
This bug is only about the error messages. They are the same and that makes it
difficult to know what is going on. (However, I do have a lot
I'm probably suffering from bug 470776, thanks for the reference! It
has been fixed for Lucid, but I filed bug 504271 about getting it fixed
for Karmic as well. Unattended boots would be nice.
My text consoles work fine, they just don't have any login prompts.
So it's probably not video driver
