16.04. /etc/fstab contains
UUID=9bb5096d-7c9b-4a53-b298-7974b9cd6a74 /mnt/WD4 ext4
noauto,nofail,errors=remount-ro 0 0
Upon plugging the disk, following gets logged:
[190158.370855] sdd: sdd1
[190158.371844] sd 7:0:0:0: [sdd] Attached SCSI disk
[190158.649144] EXT4-fs (sdd1): warning:
@Jean, it's 2016, 16.04, and this bug is still present...
Tried `noauto` + a lot of different combinations, it is always ignored and
mounted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1208
We are in 2015 and this bug seams to be still present in the 15.10
ubuntu version. I want to do a backup of my NAS on a internal hard
drive, so just mount this hard drive during the backup and then unmount
it. The issue is that it is auto mounted at boot even with the noauto
option in the fstab.
The bug is still present in Ubuntu 10.10 and it seems I can confirm what
Ubfan has mentioned, namely that the cause is the /media/ directory, as
all my drives that mount elsewhere haven't been auto-mounted. Also this
bug is only triggered sporadically, most the time it works fine and
doesn't automo
I've been dancing around this problem for the last few releases too. My
workaround is to use /mnt instead of /media in fstab and then Gnome will obey
the noauto. Ideally, I would still get these noauto partitions listed in
Places/Other Removable Media menu so I could choose to mount them with
I'm using Karmic and the bug seems to be still here. I mean, I have an
external hdd, but I want gnome-volume-manager to automount only one
partition, so I put in my fstab something like this:
/dev/disk/by-id/usb-SAMSUNG_HD103SI_1f00bfdf194b13025100-0:0-part3
/media/Monolith hfsplus force,user
> status:New → Incomplete
are you joking??
This bug was reported for Feisty more then 2 years ago. Feisty is no longer
maintained, so it should be marked
-> OUTDATED!
And now asking to check with Karmic just demonstrates the main
deficiency of this bug reporting system:
A bug is repor
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? May you please try the same with Karmic? Thanks in advance.
** Changed in: gnom
What's happening here is that the drives are defined to not be
automatically mounted on boot ("noauto") but are defined to permit users
to mount them.
When a user logs in, it looks like it's mounting them.
Gnome-volume-manager or whatever does that bit these days should respect
the noauto flag?
** This bug is no longer flagged as a security issue
--
/dev/sda3 is mounted despite the 'noauto' option in fstab
https://bugs.launchpad.net/bugs/120829
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Pleasingly, disabling the option [system>preferences>removable drives
and media>storage>mount removable media when inserted] still allows usb
devices to be mounted automatically.
--
/dev/sda3 is mounted despite the 'noauto' option in fstab
https://bugs.launchpad.net/bugs/120829
You received this
Well, I have finally found the problem... It very simply involves the
single setting [system>preferences>removable drives and
media>storage>mount removable media when inserted]. Deselecting this
makes noauto work as usual. I also managed to remove the desktop drive
icons; open terminal and type "gc
I just installed Gusty Beta and checked for that issue:
it has been fixed, 'noauto,user' no longer mounts the partitition, and users
are allowed to mount manually.
Thanks to the maintainers!
It would now be great to have that important fix also backported to
Feisty.
Best regards, Ingo
--
/dev/
I also have the problem of noauto being ignored. It worked fine in
Dapper, but in Feisty, if the "user" option is used it ignores "noauto",
and if "user" is removed it doesn't automount but then doubleclicking on
the drives icon results in the message "You are not privileged to mount
the volume". I
Meanwhile I gathered some more information:
1. if the only option in /etc/fstab is 'noauto' all is fine, it gets not
mounted
2. if the option 'user' is also added (noauto,user) it gets mounted
Conclusion: some process/application performs the mounting in user space.
However I am unable to fi
Arnold,
in fact you are right - depending on conditions this can be a big security hole.
It also is contradicting to the Linux-philosophy 'do not touch foreign data
unless the user tells you to do so'.
Moreover there seems to be no reaction on this issue.
Therefore I did change the description fl
My Machine : MSI-16332 - Notebook
OS: Ubuntu 7.04 - AMD64
Fresh Install
I also have this same problem.
I use noauto in fstab but feisty ignores this mount option.
I have 3 other os's w/multi partitions, and feisty insists on mounting
everything in sight ( like a blabber-mouth ) : O
Just ignore
> thus placed a '#' in front of the line in fstab, now Ubuntu complains
about 'error mounting local filesystems' on every boot.
This issue has been resolved meanwhile, it was my fault: a typo in /etc/fstab.
It is not related to the obove described bug which still persists (noauto
option is ignore
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8105530/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/8105531/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/8105532/ProcStatus.txt
--
/dev/sda3
19 matches
Mail list logo
