Auto mount CIFS

I know that there are many post and solutions regarding how to auto mount CIFS shares.... but for some reason I cannot get any of them to work.
Here is what I know.
1) I used to use fstab. But not fstab requires root access to mount CIFS Shares
2) I have tried smbnetfs as described here: [url= https://wiki.archlinux.org/index.php/sa … c_mounting ] Samba . This results in extremely slow browsing to the network share and my credentials being denied. It is possible that I have not set up the ~/.smb/smbnetfs.auth file correctly. I also get the message:
WARNING: Unkown libsmbclient version: 4.1.6
SMBNetFS may not work as expected.
3) I have tried autofs Autofs with no luck.
4) I would be willing to mount from the terminal or a script file. However, when I mount with
sudo mount -t cifs //networkstorage/01_media /home/user/Network/01_media -o username=xxxx,password=xxxxx
I do not get rear/write privileges.
5) I know the CIFS share is set up correctly. Because if I brows to the share using thunar I can mount the location (with password and username) and get full read write access.
Can anyone suggest what is the best method for mounting. So that I can begin trying to fiqure out how to make it work for my system. Or if I could get some advice on what I am doing wrong in the terminal so that I could get R/W privileges.
Thanks!

You tried the fstab, but you didn't specify what youactually put in the fstab. There is an option which should enable you to mount the cifs filesystem as a normal user... it is the same option as any other filesystem. Have a look at the mount man page, as it has the information you are looking for.
I don't know what smbnetfs is or how one would use that, but from a quick gander at the package info it appears to be a fuse filesystem. You also didn't give even a hint of what happened when you tried autofs, or in what way you failed.
I think what you might really be looking for is an automounting daemon though. I'm not sure how they work with network shares that require a password, but you might want to have a look. This would be how the DEs handle automounting. In particular, there is udev{,2} that seems to be the most common solution.

Similar Messages

Auto Mount fails on CIFS share

I have setup auto_master with the following line:
/- auto_direct
I also have tested a client smb share connection with the following successfully since this node is a member of the cih-ettm windows domain;
I have also setup smbadm add-key with this users name and password so that when I mount here with the following command a password is not required.
mount -F smbfs //chaos.cih-ettm.com/InboundImages /export/home/ttp/images
This works and I get a mount point and I can copy files to the directory and the windows box sees and can access the files.
If I try to set this up as an automount by adding the following line to /etc/auto_direct and execute the command automount I receive the error 'not owner'
/export/home/ttp/images -fstype=smbfs,dirperms=0755,uid=ttp //chaos.cih-ettm.com/InboundImages
Error returned:
automount: mount /export/home/ttp/outboundimages/images: Not owner
I also have the following lines in the /etc/security/exec_attr
Basic Solaris User:solaris:cmd:::/usr/lib/fs/smbfs/mount:privs=sys_mount
Basic Solaris User:solaris:cmd:::/usr/lib/fs/smbfs/umount:privs=sys_mount
In all cases the 'ttp' user is the owner of the /export/home/ttp/images
Any help would be appreciated.
Thanks,
Dave

Found out this same thing this morning. Was getting constant invalid argument errors and indeed removing "noatime" from the fstab entries fixes it. Looking at mount.cifs man page there is not only no reference to noatime but neither to relatime or anything like that.
Guess that functionality has been removed in cifs-utils? Not sure but the Wiki will need updating regardless.
Last edited by ElderSnake (2012-06-16 02:59:36)

Trying to resolve ntlmv errros mounting CIFS network shares via fstab

Kernel: 3.4.2-2
WM: Openbox
About 6 months or so ago, which was after about a year on my current install with no issue, I began getting an ntlmv error when auto mounting samba shares at
boot. Everything still worked but I continued getting an error message.
My fstab entry at that time looked like this:
//<LAN_IP>/<share name>/ /mnt/Serverbox cifs credential=/path/to/file,file_mode=0777,dir_mode=0777 0 0
The error I recieved looked like this:
CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
So I did what research I could on the error, found the "sec" option and discovered that adding the "sec=ntlmv2" option to my above noted fstab entry got
rid of the error message and everything still worked perfectly; that is until this weekend.
After upgrading both machines this weekend I noticed a new boot time error message and saw that my shares were no longer being mounted.
relevant boot log:
Mounting Network Filesystems [BUSY] mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
relevant everything log:
CIFS VFS: bad security option: ntlmv2
/var/log/pacman from the the weekend's upgrade:
[2012-06-16 13:03] Running 'pacman -Syu'
[2012-06-16 13:03] synchronizing package lists
[2012-06-16 13:03] starting full system upgrade
[2012-06-16 13:10] removed dbus-python (1.0.0-1)
[2012-06-16 13:10] upgraded linux-api-headers (3.3.2-1 -> 3.3.8-1)
[2012-06-16 13:10] Generating locales...
[2012-06-16 13:10] en_US.UTF-8... done
[2012-06-16 13:10] en_US.ISO-8859-1... done
[2012-06-16 13:10] Generation complete.
[2012-06-16 13:10] upgraded glibc (2.15-10 -> 2.15-11)
[2012-06-16 13:10] upgraded bison (2.5-3 -> 2.5.1-1)
[2012-06-16 13:10] upgraded libpng (1.5.10-1 -> 1.5.11-1)
[2012-06-16 13:10] upgraded cairo (1.12.2-1 -> 1.12.2-2)
[2012-06-16 13:10] upgraded libwbclient (3.6.5-2 -> 3.6.5-3)
[2012-06-16 13:10] upgraded cifs-utils (5.4-1 -> 5.5-1)
[2012-06-16 13:10] upgraded sqlite (3.7.12.1-1 -> 3.7.13-1)
[2012-06-16 13:10] upgraded colord (0.1.21-1 -> 0.1.21-2)
[2012-06-16 13:10] installed pambase (20120602-1)
[2012-06-16 13:10] upgraded pam (1.1.5-3 -> 1.1.5-4)
[2012-06-16 13:10] upgraded libcups (1.5.3-4 -> 1.5.3-5)
[2012-06-16 13:10] upgraded cups (1.5.3-4 -> 1.5.3-5)
[2012-06-16 13:10] installed python-dbus-common (1.1.0-2)
[2012-06-16 13:10] installed python2-dbus (1.1.0-2)
[2012-06-16 13:10] upgraded dconf (0.12.1-1 -> 0.12.1-2)
[2012-06-16 13:10] upgraded desktop-file-utils (0.19-1 -> 0.20-1)
[2012-06-16 13:10] upgraded firefox (13.0-2 -> 13.0.1-1)
[2012-06-16 13:10] upgraded freetype2 (2.4.9-2 -> 2.4.10-1)
[2012-06-16 13:10] upgraded initscripts (2012.05.1-3 -> 2012.06.1-1)
[2012-06-16 13:10] upgraded jre7-openjdk-headless (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded jre7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded jdk7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
[2012-06-16 13:10] upgraded kdelibs (4.8.4-1 -> 4.8.4-2)
[2012-06-16 13:10] upgraded libdrm (2.4.33-1 -> 2.4.35-1)
[2012-06-16 13:10] upgraded libglapi (8.0.3-2 -> 8.0.3-3)
[2012-06-16 13:10] upgraded liblrdf (0.4.0-9 -> 0.5.0-1)
[2012-06-16 13:10] upgraded libmysqlclient (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:10] installed khrplatform-devel (8.0.3-3)
[2012-06-16 13:10] installed libegl (8.0.3-3)
[2012-06-16 13:10] upgraded nvidia-utils (295.53-1 -> 295.59-1)
[2012-06-16 13:10] upgraded libva (1.0.15-1 -> 1.1.0-1)
[2012-06-16 13:10] upgraded mkinitcpio (0.9.1-1 -> 0.9.2-2)
[2012-06-16 13:10] >>> Updating module dependencies. Please wait ...
[2012-06-16 13:10] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-06-16 13:10] ==> Building image from preset: 'default'
[2012-06-16 13:10] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-06-16 13:10] ==> Starting build: 3.4.2-2-ARCH
[2012-06-16 13:10] -> Running build hook: [base]
[2012-06-16 13:10] -> Running build hook: [udev]
[2012-06-16 13:10] -> Running build hook: [autodetect]
[2012-06-16 13:10] -> Running build hook: [pata]
[2012-06-16 13:10] -> Running build hook: [scsi]
[2012-06-16 13:10] -> Running build hook: [sata]
[2012-06-16 13:10] -> Running build hook: [filesystems]
[2012-06-16 13:10] -> Running build hook: [usbinput]
[2012-06-16 13:10] -> Running build hook: [fsck]
[2012-06-16 13:10] ==> Generating module dependencies
[2012-06-16 13:10] ==> Creating xz initcpio image: /boot/initramfs-linux.img
[2012-06-16 13:10] ==> Image generation successful
[2012-06-16 13:10] ==> Building image from preset: 'fallback'
[2012-06-16 13:10] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-06-16 13:10] ==> Starting build: 3.4.2-2-ARCH
[2012-06-16 13:10] -> Running build hook: [base]
[2012-06-16 13:10] -> Running build hook: [udev]
[2012-06-16 13:10] -> Running build hook: [pata]
[2012-06-16 13:10] -> Running build hook: [scsi]
[2012-06-16 13:10] -> Running build hook: [sata]
[2012-06-16 13:10] -> Running build hook: [filesystems]
[2012-06-16 13:10] -> Running build hook: [usbinput]
[2012-06-16 13:10] -> Running build hook: [fsck]
[2012-06-16 13:10] ==> Generating module dependencies
[2012-06-16 13:10] ==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
[2012-06-16 13:11] ==> Image generation successful
[2012-06-16 13:11] upgraded linux (3.3.8-1 -> 3.4.2-2)
[2012-06-16 13:11] upgraded lirc-utils (1:0.9.0-16 -> 1:0.9.0-18)
[2012-06-16 13:11] upgraded mesa (8.0.3-2 -> 8.0.3-3)
[2012-06-16 13:11] upgraded mysql-clients (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:11] upgraded mysql (5.5.24-1 -> 5.5.25-1)
[2012-06-16 13:11] upgraded nvidia (295.53-1 -> 295.59-1)
[2012-06-16 13:11] upgraded opencl-nvidia (295.53-1 -> 295.59-1)
[2012-06-16 13:11] upgraded pango (1.30.0-1 -> 1.30.1-1)
[2012-06-16 13:11] upgraded pcmanfm (0.9.10-1 -> 0.9.10-2)
[2012-06-16 13:11] upgraded psmisc (22.16-1 -> 22.17-1)
[2012-06-16 13:11] upgraded smbclient (3.6.5-2 -> 3.6.5-3)
[2012-06-16 13:11] upgraded thunderbird (13.0-1 -> 13.0.1-1)
[2012-06-16 13:11] upgraded udisks2 (1.94.0-1 -> 1.94.0-2)
[2012-06-16 13:11] upgraded unrar (4.2.3-1 -> 4.2.4-1)
[2012-06-16 13:11] upgraded virtualbox-archlinux-modules (4.1.16-1 -> 4.1.16-2)
[2012-06-16 13:11] In order to use the new version, reload all virtualbox modules manually.
[2012-06-16 13:11] upgraded virtualbox-modules (4.1.16-1 -> 4.1.16-2)
[2012-06-16 13:11] upgraded xine-ui (0.99.6-5 -> 0.99.7-1)
[2012-06-16 13:11] Running 'pacman -Syy'
[2012-06-16 13:11] synchronizing package lists
[2012-06-16 13:12] Running 'pacman -Syu'
[2012-06-16 13:12] synchronizing package lists
[2012-06-16 13:12] starting full system upgrade
[2012-06-16 13:13] upgraded lib32-freetype2 (2.4.9-1 -> 2.4.10-1)
[2012-06-16 13:13] upgraded lib32-gnutls (3.0.19-1 -> 3.0.20-1)
[2012-06-16 13:13] upgraded lib32-krb5 (1.10.1-2 -> 1.10.2-1)
[2012-06-16 13:13] upgraded lib32-libpng (1.5.10-2 -> 1.5.11-1)
[2012-06-16 13:13] upgraded lib32-libx11 (1.4.99.902-1 -> 1.5.0-1)
[2012-06-16 13:13] upgraded lib32-nvidia-utils (295.53-1 -> 295.59-1)
[2012-06-16 13:13] upgraded lib32-sqlite3 (3.7.11-1 -> 3.7.13-1)
[2012-06-16 13:13] upgraded lib32-util-linux (2.21.1-1 -> 2.21.2-1)
[2012-06-16 13:13] upgraded lib32-xcb-util (0.3.8-1 -> 0.3.9-1)
[2012-06-16 13:13] upgraded wine (1.5.5-1 -> 1.5.6-1)
Currently returning to the old fstab entry once again gives the initial error code about the security mechanism being upgraded in kernal release x.x (it always seemed to change with each kernel change) though the shares seem to mount just fine. I've looked through the wiki, man pages on die.net and googled everything I can think of and I find a lot pages mentioning ntlmv errors with no solutions, many telling me that ntlmv and ntlmv2 are mount options, but nothing that gives me any indication on why I might be getting this error or how to go about looking for a solution.
I've looked through the pacman logs on both my desktop and my file server that I'm connecting to in an effort to determine what might have changed and I found that:
the smbclient had been upgraded on both machines so I tried downgrading back to version 3.6.5-2 but there was no change when rebooting.
I also found cifs-utils had been upgraded on the file server. So I downgraded that as well to the previous version (5.4-1), rebooted both machines and I'm still getting the same invalid arguement error.
I've now gone back and upgraded to the most recent versions of the downgraded packages on each machine but I'm at a loss as to what my next steps should be. Where do I go from here to track this down and determine if this is a bug or configuration error. Is there a cleaner way of mounting these shares that I should be using instead of fstab?
Thank you.

I had the same issue. After upgrading kernel to 3.4.5 today the cifs share mounted with original fstab settings. I believe it was caused by this bug:
kernel changelog wrote: The double delimiter check that allows a comma in the password parsing code is
unconditional. We set "tmp_end" to the end of the string and we continue to
check for double delimiter. In the case where the password doesn't contain a
comma we end up setting tmp_end to NULL and eventually setting "options" to
"end". This results in the premature termination of the options string and hence
the values of UNCip and UNC are being set to NULL. This results in mount failure
with "Connecting to DFS root not implemented yet" error.

Mount error: ...not superuser and mount.cifs not installed SUID

I'm trying to automount Samba shares but get this everytime I try to mount the partition:
mount error: permission denied or not superuser and mount.cifs not installed SUID
I have this entry in the fstab:
//192.168.2.1/Capsule /media/capsule cifs auto,noserverino,username=xxx,password=xxx,workgroup=WORKGROUP,iocharset=utf8,file_mode=0777,dir_mode=0777,suid,users 0 0
I tried different options (suid,users or without them) same results.
I also tried to chown like this:
chmod u+s mount.cifs
But still no luck
Need help please.

It seems that mount.cifs will only let you mount at directory that you are the owner of. I think this may be changeable with the UID option but I have not figured it out.

How to turn off auto mounting of server on boot?

I've got an old MacPro that is running Mavericks but is having an issue where the finder constantly crashes and restarts. I think it may have to do with a an old server (an external Mac mini) that would mount when the MacPro booted up because I now get an error message telling me that the Mac Pro can no longer find that server (which makes sense as it is no longer there). If I leave the error window open and don't click 'ok', the Finder remains intact and the crash loop does not begin. If I click 'ok' in the server connection error window, the problems begin.
…So, where do I "turn off" this auto mounting of the old mac mini on boot? I've looked in my Login items in the system prefs and no such task is there, and I can no longer recall how i even set up this automount function.
Thanks for any help you can offer.
Mark

Repair Disk.
Choose Apple menu > Restart. Hold down the Command (⌘) and R keys as your computer restarts.
When you see a white screen with an Apple logo in the middle, you can release the keys.
Click Disk Utility, and then click Continue.
In the list at the left, select the item you want to repair.Macintosh HD.
Click First Aid.
Click Repair Disk.
If Disk Utility reports that the disk appears to be OK or has been repaired, you’re done.
Click Restart.

How Do I find out what app is auto-mounting a network share and stop it?

I have a new laptop, the 13" rMBP. I installed Steam and wanted to use the network share on my server to store the game files. Everything went OK. I closed Steam, disconnected the share and shutdown my laptop. When I opened my laptop later on at work, it started to try and mount the network share.It keeps on going it. I removed the Steam app and all files related to Steam that I could find. I've looked at fstab, auto_home, auto_master and a large list of other files and directories and I *still* cannot find the offending file that's auto-mounting the share. It's really frustrating.
The share auto-mounts when I am home but not on the desktop or in finder. I find it by looking at /Volumes/ in terminal. If I mount the share manually under /Volumes/ it shows as Games-1 and mounts on the desktop under Games.
Does anyone have any ideas on where I should be looking to find the offending process/file/daemon?
Thank you!
Trevor

thanks for the reply but are you sure about this? What difference would it make? Why 5 apps?
Even if it does work, which I doubt, at some point, I will have to resync ALL my apps again and surely the same thing will happen again, and I will be none the wiser. I still won't know which app it is. There must be a way of finding this out.
Any ideas?
What is really freaking me out is how it is connecting to my carrier (who is charging me) with Cellular data switched off.......?
Thanks again.

Hello. I have a problem with OEL 6.5 and ocfs2. When I mount ocfs2 with mount -a command all ocfs2 partitions mount and work, but when I reboot no ocfs2 partitions auto mount. No error messages in log. I use DAS FC and iSCSI FC.

Hello.
I have a problem with OEL 6.5 and ocfs2.
When I mount ocfs2 with mount -a command all ocfs2 partitions mount and work, but when I reboot no ocfs2 partitions auto mount. No error messages in log. I use DAS FC and iSCSI FC.
fstab:
UUID=32130a0b-2e15-4067-9e65-62b7b3e53c72 /some/4 ocfs2 _netdev,defaults 0 0
#UUID=af522894-c51e-45d6-bce8-c0206322d7ab /some/9 ocfs2 _netdev,defaults 0 0
UUID=1126b3d2-09aa-4be0-8826-0b2a590ab995 /some/3 ocfs2 _netdev,defaults 0 0
#UUID=9ea9113d-edcf-47ca-9c64-c0d4e18149c1 /some/8 ocfs2 _netdev,defaults 0 0
UUID=a368f830-0808-4832-b294-d2d1bf909813 /some/5 ocfs2 _netdev,defaults 0 0
UUID=ee816860-5a95-493c-8559-9d528e557a6d /some/6 ocfs2 _netdev,defaults 0 0
UUID=3f87634f-7dbf-46ba-a84c-e8606b40acfe /some/7 ocfs2 _netdev,defaults 0 0
UUID=5def16d7-1f58-4691-9d46-f3fa72b74890 /some/1 ocfs2 _netdev,defaults 0 0
UUID=0e682b5a-8d75-40d1-8983-fa39dd5a0e54 /some/2 ocfs2 _netdev,defaults 0 0

What is the output of:
# chkconfig --list o2cb
# chkconfig --list ocfs2
# cat /etc/ocfs2/cluster.conf

External Hard Drive connected to AEBS does not auto mount

Just upgraded from Tiger 10.4.11 to Leopard 10.5.5. I have a AEBS running 5.3.2 airport utility with a LaCie HD connected to it.
In Tiger, my external hard drive would auto mount onto the desktop every time the computer turned on or woke up from sleeping etc.
In Leopard, my external drive will not auto mount. It does not show up in the sidebar under devices. It does not show up in the disk utility. To access it, I have to go the the finder sidebar, select my AEBS under shared, then select my HD. Also, I did check show connected servers and external disk on the desktop in the finder preferences. Also, not sure if this matters but the icon on my external drive on my desktop is the blue drive with three people holding hands and not the brighter blue one with the wireless signal logo.
In tiger my external HD basically acted like any other folder that was always there and not like a networked drive that I had to go and connect to. I want to go back to that. I heard this has to do with leopord no longer having the airdisk utility??
thanks

Try making an alias of one of the top-level folders in your external (AEBS-connected) drive, drag it to the desktop, and then put it in your Login Items.
--> System Preferences/Accounts/Login Items
You can simply drag the folder alias into the Login Items window.
When you next log in, the folder will be automatically opened. Alas, it doesn't give you instant access to the entire external drive, but you can back out a level to see the entire drive. It isn't quite what you had with Tiger, but perhaps it will suffice.
If you leave the aliased folder on your desktop, you have a skinny approximation to the mounted volume that you had with Tiger.

External hard drive and SD card won't auto mount

I am using MBP with retina on Yosemite. MacBook Pro (Retina, 15-inch, Late 2013).
On Maverick, all my external drives used to auto mount. The same was true just after Yosemite was installed. Lately, only my Time Machine hard drive auto mounts and others don't, e.g. my backup drive that I use with Super Duper! and my camera SD card. I have to go to disk utility and mount them manually. I did not see any option for auto mount in disk utility.
Could you please guide me on how to get auto mount back?
Thanks in advance

I have been dealing with this same issue for the past several months. Running a Macbook Pro (Mid 2010) with OS X Yosemite 10.10.1. This problem occurs when I plug in Firewire, USB, or SD card. The external hardware appear to be working fine, it has to be either a setting, or a quirk that needs corrected with Yosemite. I have run all OS systems since Snow Leopard. Never had this problem. Anyone have any ideas?

How do I stop a CCC partition auto mounting in Lion

I have an external USB drive with 2 partitions. The first partition has a CCC Clone of my drive before Lion. The second is used for Time Machine. This drive auto mounts on boot which is fine but the CCC partition causes problems with the App Store as it sees Apps that I installed in the Clone backup as installed on Lion. The easy way for me to fix this is just to eject the CCC partition but I have to do this every time I boot. Is there a way of just stopping this drive from auto mounting on boot and manually mounting if need be. Any help would be appreciated. Many Thanks in advance.

I just upgraded to the latest version of Lion--I don't know why it didn't change the info. under my Apple icon. And I know I can uncheck the box while signing off, but you have to do it each time--I'm looking for a way to uncheck it and recheck whenever I want, the way the dock options are supposed to work (although it doesn't for me anymore with Lion).
Checked the Users and Groups--the only login items listed are basically 4 apps that I had back when I had my PC and I no longer have them--I may have had Growl for awhile but I deleted it. There are yellow triangles by them. No other apps listed there.
I guess I'll have to uncheck the box each time I sign off. Tedious, but that's the way it is. Wish I had Snow Leopard back!
Thanks for your suggestions though--just wish they worked.

Auto Mount in SAP LVM 2.0

Hi All,
We have installed SAP LVM 2.0 SP3 in our landscape and we are working on manage system configuration to utilize cloning futer in SAP LVM.
During the configuration, we are not able to select auto mounter option in Instance configuration.
I request you to kindly suggest me on this.
Thansk and Regards,
Prasad

Hello Dieter,
Thank you, I have created a support ticket with SAP.
Thanks and Regards,
Prasad

[solved] USB drives won't auto mount

When I plug in a drive, I get this error message:
Rejected send message, 1 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=4499 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3069 comm="/usr/sbin/hald)).
2nd harddrive:
Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=3537 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3058 comm="/usr/sbin/hald)).
There are fixes in other forums, but they are all radically differnet, and the one's I tried aren't working.
I have an eee pc with xfce and slim.
I know this is a perimssion problems since auto mount works fine for root. Could anyone tell me the (probably simple) fix for this? Thanks.
Last edited by Meskarune (2010-04-15 04:21:08)

HAL:
http://wiki.archlinux.org/index.php/HAL#Troubleshooting
Also check your .xinitrc and make sure your lines matches this:
exec ck-launch-session startxfce4
Lastly, you can also use udev to automount your drives:
http://wiki.archlinux.org/index.php/Ude … SB_devices

Disable Gnome auto mount for one specific UUID

I am using Gnome 3 (gnome disk utility,udisks,udev stack i think).
I have a device (Garmin Edge 800) that I am only going to use in Virtualbox so I want to prevent it from automatically mounting in Gnome. However I want other devices to auto mount as normal so disabling auto mount entirely isn't an option.
The device got two UUIDs and previously I could write a HAL fdi policy to ignore devices with those UUIDs, but now that HAL is deprecated I am not able to figure out how to do this.
Last edited by lessthanjake (2011-06-29 09:56:30)

There's probably a udev config file somewhere (udev wiki perhaps) but you can do it with fstab "noauto" that's what I do for partitions I don't want to auto mount.

Working auto-mount?

Hi all,
I have a xfce4 desktop installed. I want an automount service. I tried autoFS, with the following settings:
auto.master
/media /etc/autofs/auto.custom --timeout=15
auto.custom
disc -fstype=auto,ro,nodev,nosuid :/dev/cdrom
Backup -fstype=auto,user,rw,async,umask=000,gid=users,noatime,nodiratime :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
## Backup -fstype=ext4,user,rw,async,umask=000,gid=users,noatime,nodiratime :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
Shared -fstype=ntfs-3g,user,rw,async,umask=000,gid=users,noatime,nodiratime :/d ev/disk/by-uuid/565AF3085AF2E421
ReaderCard -fstype=vfat,flush,user,rw,async,umask=000,gid=users,noatime,nodirat
ime :/dev/disk/by-uuid/0102-0304
##ReaderInt -fstype=auto,async,nodev,nosuid,umask=000,gid=users :
## Other medium here
# floppy -fstype=auto,async,nodev,nosuid,umask=000 :/dev/fl
The files are formatted following the instructions. The partition Backup, however, does not come up ("no such file or directory", even when root).
Backup is ext4 and it's kept on an external hard drive, the same of Shared. Mounting it manually works. I have tried with simpler options (as simple as
Backup -fstype=auto :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
with no results. Autofs won't do.
As an alternative I have tried xfce volume manager, but that doesn't work with ANY external device.
Please help. Thank you.

That would be a solution - if it worked. I tried that too. The Arch wiki just glances on the setup, solving the whole question with a one liner "Thunar-volman's automount doesn't work currently because of the hal to udev switch, Sept 2010"
The section on udev is obscure, mentioning to check policykit to "properly start your session".
However the policykit page is also obscure, containing no mention about starting X session properly or even improperly for what matters.
The default setting produces no result at all.
Nowhere I was able to find a five-lines working example of set up. I have used Linux daily since 2000 (and I know it should not take more than 5 line explanation to setup an auto-mount).
I am really embittered by this interpretation of "the arch way". The documentation on certain core tools such as policykit is completely insufficient and the defaults do not solve basic problems (hours to set up a basic auto-mount? incomplete wiki pages referring each other?).
Arch could be a perfect desktop distribution with just a pinch of attention to put the obvious features, when correctly disabled by default, at easy reach through complete examples. (Shutdown buttons? Same story: one line reference to policykit, dbus and other 10 tools with not the barest explanation about how to use them in synergy for the purpose. Result? Manual shutdown for the moment).
If you could provide a working setup for thunar volume manager I'll be happy to use and add it to the wiki.
Thank you.

USB Auto-mounting Woes [SOLVED]

Hi,
I've been trying to get my USB sticks to auto-mount and grant all users permission to mount/unmount them.
To achieve that I initially added the following to my sudoers using visudo:
%wheel ALL=NOPASSWD: /bin/mount
%wheel ALL=NOPASSWD: /bin/umount
That however didn't solve my inability to (un)mount drives in PCMan FM.. so I headed towards the wiki. The wiki stated the following:
You can easily automount and eject removable devices with the combination of pmount, udisks2 and spacefm. Note you have to run spacefm in daemon mode with spacefm -d & in your startup scripts, ~/.xinitrc or ~/.xsession, to get automounting.
I wasn't too fussed about having to use spacefm and everything seemed to work just fine.. until I tried format a USB stick using gparted. Gparted fails because because seemingly half way through the formatting procedure the drive is mounted (my suspicion is that it's spacefm).
mkdosfs: /dev/sdb1 contains a mounted file system.
If i unmount and format manually using the CLI it works just fine.. but I quite like gparted
I tried removing
spacefm -d
from my .xinitrc and that actually stops openbox from starting up. Uninstalling (and later re-installing when it didn't help) pmount didn't help either, spacefm just auto-mounts in a strange 'run' way..
So now I'm stuck, anyone experienced similar issues with gparted and spacefm?
Last edited by omgitsaheadcrab (2012-06-22 13:27:07)

ck-list-sessions shows an active consokekit session, so that should be fine?
Session1:
unix-user = '1000'
seat = 'Seat1'
session-type = 'x11'
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2012-06-22T12:24:47.734505Z'
login-session-id = '3'
The gparted error log is as follows:
GParted 0.12.1
Libparted 3.1
Delete /dev/sdb1 (fat32, 7.37 GiB) from /dev/sdb 00:00:01 ( SUCCESS )
calibrate /dev/sdb1 00:00:00 ( SUCCESS )
path: /dev/sdb1
start: 2048
end: 15466495
size: 15464448 (7.37 GiB)
delete partition 00:00:01 ( SUCCESS )
========================================
Create Primary Partition #1 (fat32, 7.37 GiB) on /dev/sdb 00:00:01 ( ERROR )
create empty partition 00:00:00 ( SUCCESS )
path: /dev/sdb1
start: 2048
end: 15466495
size: 15464448 (7.37 GiB)
set partition type on /dev/sdb1 00:00:01 ( SUCCESS )
new partition type: fat32
create new fat32 file system 00:00:00 ( ERROR )
mkdosfs -F32 -v -n "PATRIOT" /dev/sdb1
mkdosfs 3.0.12 (29 Oct 2011)
mkdosfs: /dev/sdb1 contains a mounted file system.
========================================
I still can't help but feel it's spacefm doing something funny (automounting when it shouldn't)
Last edited by omgitsaheadcrab (2012-06-22 12:31:36)

Auto mount CIFS

Similar Messages

Maybe you are looking for