Milton's picture

The File Server applicance is a VMWare ESXi vm. 192.168.205.10 is Windows 2012R2 sharing a drive which is reachable from Windows clients. But the File Server appliance will not mount the b$ share nor any other share.

mount -t cifs //192.168.205.10/b$ -o username=user,password=pass,workgroup=dom /media/win-share

mount: block device //192.168.205.10/b$ is write-protected, mounting read-only

mount: cannot mount block device //192.168.205.10/b$ read-only

 

I tried adding sec=ntlm and sec=ntlmv2, but that just returned

mount: Operation not supported

Any suggestions appreciated.

Forum: 
Milton's picture

I stopped using the mount command instead using webmin

In webmin > System > Disk and Network Filesystems
Type: Common Internet Filesystem (cifs)
Add mount
Mounted as /media/win-share
Save and mount at boot
Mount now? Mount
Server Name 192.168.205.10 Share Name b$
Login Name backup Login Password password
-----------------------------------------------------
This webmin process creates an /etc/fstab entry which is right
-----------------------------------------------------
/etc/fstab


proc                    /proc   proc    nodev,noexec,nosuid     0       0
/dev/mapper/turnkey-root        /       ext4    errors=remount-ro       0       1
UUID=0aa6e5cf-76f0-408b-a9b2-c0a6600ca685       /boot   ext2    defaults        0       2
/dev/mapper/turnkey-swap_1      none    swap    sw      0       0
\\192.168.205.10\b$     /media/win-share        cifs    password=password,username=backup  0       0
-----------------------------------------------------
but upon reboot the mount fails, so
-----------------------------------------------------
http://lifeisabug.com/fix-debian-wheezy-mounting-cifs-smb-shares-boot-time/
Add the following to /etc/default/rcS:
ASYNCMOUNTNFS=no

-----------------------------------------------------

Now my Turnkey Linux File Server reliably sees the Windows file server share.

Next is to convince TKLBAM to backup that share to AWS.

Jeremy Davis's picture

Apologies on my delayed response. Glad to hear that you found a workaround and thanks for posting. I'm sure that will help others!

Add new comment