I'm just giving ideas, I like simplicity too and certainly not demand
additional ways to do one thing. For me your fix is just not ultimate
option - not running fsck at all or mounting drive manually does add
burden on end user that probably doesn't want to know what fsck is or
use any special tric
I gave a solution. In my first reply:
If a particular filesystem is not always present, then you should
configure the disk so that the fsck pass number is 0, and that mount
option "noauto" is present so that the filesystem is not mounted at boot
time. Then it will not interrupt the boot process,
This is still present in 8.04 and there seems no good way to fix this
now in ubuntu - you don't like the ignore approach, but you don't
provide any other means to fix it properly. Disabling fsck completely is
bad, giving user power to mount file systems is not bad, but it requires
additional action
Nothing Upstart-related in this bug report
** Changed in: upstart (Ubuntu)
Status: Unconfirmed => Rejected
--
Failed file system check, weird behaviour
https://bugs.launchpad.net/bugs/68589
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Well, the problem is that we need to distinguish between a critical
filesystem (like /usr) being not present, and something completely
optional, like /media/disk. More of a concern is where a filesystem is
critical for an application-level server, and if it's missing it causes
the server to reall
I would like to mention that from an end users perspective, they way you tell
me I should edit fstab is not good.
Ubuntu should be able to handle futile things like this, it should detect the
partition is not present and continue booting. "Fail with grace, not fall down
on it's face"
--
Failed
It was Edgy at the time of posting, now It's Feisty. But the rack is gone.
We might as well close this. Nothing will happen to it.
In any case, the mount all file system spec should have solved this.
(but didn't).
--
Failed file system check, weird behaviour
https://bugs.launchpad.net/bugs/68589
What version of Ubuntu is this?
If a particular filesystem is not always present, then you should
configure the disk so that the fsck pass number is 0, and that mount
option "noauto" is present so that the filesystem is not mounted at boot
time. Then it will not interrupt the boot process, and t
** Changed in: Ubuntu
Sourcepackagename: None => e2fsprogs
--
Failed file system check, weird behaviour
https://launchpad.net/bugs/68589
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
