For those wondering heres the perms on my smbcredential files - again this worked crorrectly under both Ubuntu and Fedora:

I see the same thing:

Edited by th3blad3runn3r at 2016-11-11 18:44

Could you please give a try with thoses credentials:

I had some isssues with

preventing cifs to mount correctly.

I know it sounds crazy, as .smbcredentials should be only read while fstab is processed....

the problem with that is that 'poweruser' or at least the user account that I connect under does not exist on this machine.

And in my case, 'poweruser' exists both on my machine and the remote one (my NAS)...
I can't figure out why this doesn't work anyway, as long as the correct remote user is declared into the .smbcredentials.
Local rights shouldn't interfere.
My understanding so far :

Let's name LUSER the local user on the machine you're trying to mount your cifs partition into
Lets name RUSER the remote account for your NAS or your distant machine

.smbcredentials should contain


Are you sure (if you're using a NAS), that the share options on the remote node are OK ?

I have three shares, one on a Linux development machine and the other two on a Windows fileserver.

As previously noted all three used to auto-mount fine under Fedora and xUbunbtu.
The only change here is moving to Deepin.

Mounting works as expected when using 'sudo mount -a' which tells me my fstab entries and smbcredential files are fine.

I have another way to solve this problem：
Edit this file with root permission——

And then add codes before "exit 0"——

so this mount codes will be executed when you login ..

That's honestly a terrible idea from a security standpoint.

Your password should never be stored in plaintext anywhere on your machine.

It is not mounting cifs here at all. I need access to windows share with username and without password.

Add x-gvfs-show and users to the options, so that they will show up in file manager. This will still not mount them automatically, but you will be able to mount them by clicking on them in nautilus or in whatever file manager you use (faster then sudo mount -a).
Do you see these messages during boot:
CIFS VFS: Error connecting to socket. Aborting operation.
CIFS VFS: cifs_mount failed w/return code = -101
Since auto mounting is not working for me either and i think it's somehow related to these, but i didn't find anything useful about them by now.

Had a similar issue when trying to properly auto-mount my NAS which uses SMB, with fstab (I couldn't automatically load my music library in a media player, unless I first accessed the share via nautilus).

After trying out all the tricks with FSTAB, I decided to go about this in a bit different way, and since I would anyways forget how I did it, I made some instructions that I can share here:

To automount an SMB Share with systemctl / systemd:

systemctl enable NetworkManager-wait-online.service
(I needed to enable this to indicate when the mounting should happen)

create a new SystemCTL Unit with .mount file extension to /etc/systemd/system/
Name for the Unit = Path to mount directory (e.g. "home-username-NAS.mount") with this content:

[Unit]
Description=Mount NAS at boot
Wants=network-online.target
After=network-online.target

[Mount]
What=//192.168.1.3/NAS  
Where=/home/yourusername/NAS
Options=credentials=/home/yourusername/.smbcredentials,iocharset=utf8,rw,uid=1000,gid=1000 (basically the same stuff you would use in fstab)
Type=cifs
TimeoutSec=30

[Install]
WantedBy=multi-user.target


Testing if the mount works:
systemctl start home-yourusername-NAS.mount

Finally to enable the mount on Startup:
systemctl enable home-yourusername-NAS.mount


Hope this helps, or at least gives some clues on how you could proceed

Edited by th3blad3runn3r at 2016-11-1 13:56

Here's how I succeed with cifs mount :
Below an excerpt of my fstab

The trick relies upon the use of a credential file:
This one must contain the following entries

and its access rights have to be :

Hth