Also affected by this on trusty! In my case somehow the message to skip
is showing up when mounting an LVM over LUKS over LVM partition however
the boot continues fine without any interaction... would be good to get
rid of that failure
--
You received this bug notification because you are a membe
** Tags removed: precise
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mountall ignores nofail mount option
To manage notifications about this bug go to:
https:/
This affects 14.04 too.
** Description changed:
Binary package hint: mountall
mountall ignores nofail mount option. Ubuntu can not be started if
external sas device is down, for example.
Description: Ubuntu 10.04.1 LTS
- Release: 10.04, 10.10, 12.10
+ Release: 10.04, 10.1
** Description changed:
Binary package hint: mountall
mountall ignores nofail mount option. Ubuntu can not be started if
external sas device is down, for example.
Description: Ubuntu 10.04.1 LTS
- Release: 10.04, 12.10
+ Release: 10.04, 10.10, 12.10
--
You received this
** Description changed:
Binary package hint: mountall
mountall ignores nofail mount option. Ubuntu can not be started if
external sas device is down, for example.
Description: Ubuntu 10.04.1 LTS
- Release: 10.04
+ Release: 10.04, 12.10
--
You received this bug notificati
s/system/file system/g
sorry about that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mountall ignores nofail mount option
To manage notifications about this bug go to:
https://bugs.l
Affected by this issue, and same as reporter I expected 'nofail' option
as the solution
My situation is I had my system on a ssd and while I want to automount
other system on my own computer I also want system to skip it if I boot
my ssd on another computer.
--
You received this bug notification
I agree with comment #21. This is an important feature, and it's strange that
it hasn't been implemented yet. The expected behaviour should be:
- If device can be mounted, mount it.
- If device can't be mounted, skip it (also possibly log the event somewhere).
- Optionally allow for specifying tim
So, this leaves the question of what needs to be done to allow for a
storage volume for which it is normal for it to be either present or not
present. If it is present, have it mounted as part of the normal
startup process. If it is not present, simply continue on with the
normal boot process wit
I don't think I've misunderstood anyone here, though I may have
misunderstood the code. Also, I don't think everyone commenting on this
bug report actually has the same goals.
There are three orthogonal aspects of boot behavior that users may wish to
configure here.
- whether to hold up the boo
@Steve Langasek
Looks like you misunderstood us.
> The 'nofail' option is documented as:
>do not report errors for this device if it does not exist.
> The problem you're describing is not one of reporting errors, but a
lack of timeout while waiting for a device to become available on boot.
'n
moving back to mountall as timeout option does not appear to work
** Package changed: util-linux (Ubuntu) => mountall (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mountall i
I'm looking to do the exact same thing as the original reporter. I have
some partitions on a secondary drive that is not always connected to my
system. If the secondary drive is present at boot I would like the
partitions mounted, if it is not, I would like the system to continue
without any noti
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: util-linux 2.20.1-1ubuntu3
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_U
The timeout option should be just a number of seconds to wait for the
device before giving up on it, e.g. timeout=60. What's the fstab line
that you tried and found didn't work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
>From reading the documentation, noauto option would mean that it will
not auto mount at boot up but will still automount if present/detected
(since cdroms and floppies use this and are automounted)? I tried the
timeout option, but that doesn't seem to work. Do you have a syntax
example?
--
You r
On Sat, May 19, 2012 at 08:46:03AM -, Ivan Frederiks wrote:
> Are you sure?
Yes.
> In this regard I think that documentation of 'timeout' option should be a
> separate bug.
There's only one bug here, which is the lack of documentation of 'timeout'.
The 'nofail' option is not defined to do w
Are you sure? I need 'nofail' option to use my external hdd with my laptop.
Sometimes hdd remains plugged in for a week and sometimes I take my laptop away
and I want it to continue booting normally.
In this regard I think that documentation of 'timeout' option should be a
separate bug.
--
You
The 'nofail' option is documented as:
do not report errors for this device if it does not exist.
The problem you're describing is not one of reporting errors, but a lack
of timeout while waiting for a device to become available on boot.
'nofail' is not a correct option to use for this.
m
Ubuntu 12.04 has been released, but nofail still doesn't work.
Please fix it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mountall ignores nofail mount option
To manage notificatio
Thanks for taking the time to submit a patch! I was able to get the
patch applied to the Precise (what will be 12.04) version of mountall.
However, the behavior is not what I had expected nor what I think you
intended. Instead of seeing a message regarding the skipping of the
filesystem marked no
The attachment "reel-mountall-nofail.diff" of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag '
"Yust wait long enough, someone will send a patch"
Ok, so after 1.5 years here is my solution for the problem. "nofail" wasn't
implemented at all, though it is
documented. Geee...
patch may have side effects but does what it should. Ah and it is against
mountall 2.15.3 from Ubuntu 10.04.
I don
Using "nobootwait" is not an option to me, because "nobootwait" also causes the
system not to wait for the filesystem to be checked.
In other words, the fsck is run in background while the boot process continues.
This causes other services that depend on that fs to fail.
Also "optional" (mentione
Ubuntu 10.11 Oneiric. The same fstab line that worked in 9.04 Jaunty
for an external usb hard drive would give disk checking errors at boot
in 10.11. "nofail" didn't change the behaviour, but "nobootwait" solved
the problem. Thanks for your posts.
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mo
Thanks Konstantin.
I was having the same problem and that solved it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610869
Title:
mountall ignores nofail mount option
--
ubuntu-bugs mailing list
u
Ubuntu 10.10 Maverick. The bug is still there.
possible workaround: using option "nobootwait"
--
mountall ignores nofail mount option
https://bugs.launchpad.net/bugs/610869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
28 matches
Mail list logo
