Comment 0 for bug 504224
Revision history for this message
| Alvin (alvind) wrote Inconsistent error message: Filesystem could not be mounted | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
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 appear when they can't be mounted. (due to another bug)
Example:
mount.nfs4: DNS resolution failed for leto: Name or service not known
mountall: mount /home [901] terminated with status 32
mountall: Filesystem could not be mounted: /home
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home: waiting for leto:/home
* Setting preliminary keymap
.... and so on
In this example, /home is mounted during the boot process, even though mountall says it could not be mounted. If it doesn't work, the same errors appear, but only the recovery shell is available.