Share via

Mount not working (-115) after detaching virtual machine

  • Article

Question

Friday, September 14, 2018 8:50 PM

I need to mount a network share on my Ubuntu virtual machine, which I wasn't able to do until now despite reading through quite some of your and the Linux documentation.

What I did so far:

I've set up a Ubuntu machine using the official image for Ubuntu 18.04.1 LTS and added a line to the "/etc/fstab" file, which now looks like following, whereby 10.0.0.4 is a machine which is online permanently holding a samba share on "share":

//10.0.0.4/share  /datadrive  cifs    guest,_netdev,iocharset=utf8,file_mode=0777,dir_mode=0777   00

When calling "mount -a" the system is able to find the shared folder and mount it, same if I restart the VM. But when deallocating it and then starting it, I get the following error message:

[   30.172043] CIFS VFS: Error connecting to socket. Aborting operation.
[   30.176740] CIFS VFS: cifs_mount failed w/return code = -115

What am I doing wrong? Out of your tutorial on https://docs.microsoft.com/en-us/azure/virtual-machines/linux/mount-azure-file-storage-on-linux-using-smb#persist-the-mount there should be no additional requirements, but also this one (taking a file-storage instead of a samba-share of another VM) gave the same result.

EDIT:

Here's some additional data I gathered when it today happened again:

systemctl status datadrive.mount returns:

● datadrive.mount - /datadrive
   Loaded: loaded (/etc/fstab; generated)
   Active: failed (Result: exit-code) since Mon 2018-09-17 17:09:52 UTC; 2min 59s ago
    Where: /datadrive
     What: //10.0.0.4/share
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 1040 ExecMount=/bin/mount //10.0.0.4/share /datadrive -t cifs -o x-systemd.requires=cloud-init.service,x-systemd.before=docker.service,guest,iocharset=utf8,file_mode=0777,dir_mode=0777 (code=exited, status=32)

Sep 17 17:09:41 stripes-master-s6 systemd[1]: Mounting /datadrive...
Sep 17 17:09:52 stripes-master-s6 mount[1040]: mount error(115): Operation now in progress
Sep 17 17:09:52 stripes-master-s6 mount[1040]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Sep 17 17:09:52 stripes-master-s6 systemd[1]: datadrive.mount: Mount process exited, code=exited status=32
Sep 17 17:09:52 stripes-master-s6 systemd[1]: datadrive.mount: Failed with result 'exit-code'.
Sep 17 17:09:52 stripes-master-s6 systemd[1]: Failed to mount /datadrive.

This time it only failed for 4 of the 5 machines who are supposed to mount this shared drive.

All replies (7)

Saturday, September 15, 2018 7:13 AM

You try the below troubleshooting steps:

  • First Make sure that you can ping the IP address
  • Telnet IP on Port 445
  • Has there be any IP changes lately? Please make sure that the firewall is properly set.
  • Check DNS issue
  • Check firewall (include local firewall or network firewall)
  • Check your Log files - /var/log/syslog or /var/log/messages

For more details, you may refer the suggestions outlined in the MSDN thread, which addresses similar issue.

If this answer was helpful, click “Mark as Answer” or “Up-Vote”. To provide additional feedback on your forum experience, click here

Monday, September 17, 2018 9:32 AM

As I wrote, it works after calling `mount -a` and even works after rebooting, so I can safely cross off the first four of your concerns.

I've now added a dependency on the service `cloud-init` which seems to help.

Tuesday, September 18, 2018 2:36 AM

Thank you for sharing your solution and experience here. It will be greatly beneficial for other community members who have similar questions.

Tuesday, September 18, 2018 5:45 AM

Couldn't get much out of the `/var/log/syslog` as of now. I booted up five machines simultaneously and it worked only for one of them. Comparing the `syslog` didn't give me a useful insight as it looked like the boot-order of the services wasn't any different. I've updated the question with some insights gained there.

Tuesday, September 18, 2018 6:48 AM

Nope, doesn't help. Just got this problem again ... Booting up five VMs simultaneously and only one of them got the mount right.

I've also looked at the logs on the samba server I manage, without any results ... I'm also thinking of switching to a network file mount managed by Azure. Investigation still ongoing ...

Wednesday, September 19, 2018 7:12 PM

We would like to get you in touch with a Linux Engineer to help better debug this. 

Do you have the ability to open a Technical Support Ticket? If not, you can email me at [email protected] and provide me with your SubscriptoinID and link to this thread. 

I can enable your subscription for a free support request. 

Monday, May 13, 2019 1:27 PM

Was there any resolution to this? I'm experiencing the same issues on Ubuntu 18.04 VMs (eastus) after starting them from a stopped/deallocated state. Was previously connected fine and restoring the mountpoint via fstab has been working without issue.

Attempting to run `mount -a` returns the "error(115): Operation now in progress" error.