Solved Unable to mount /backups folder (Cifs)
@girish I did a google research before and I saw linked document but it seems that is not my situation.
The only difference that I've between a standard installation is that I disabled SSH login with password and also disabled root login.
Which logs should i see?
make sure you can do the mount manually on the command line first, then add it to fstab
The same syntax I used on other Cloudron installations and it worked very fine.
I tried to mount manually but I got a syntax error.
Eg. I used:
mount -t cifs //<server>/<remote_folder> /backups uid=yellowtent,gid=yellowtent,user=<user>,pass=<pass>,iocharset=utf8 0 0
and I got:
mount: bad usage
@p44 could be 2 things.. compare
mountversions, which may have a different syntax.
make sure cifs is available on the new system, for ex if mount.cifs isn't available, it won't recognize the
cifsparameter and error out.
if there are other cifs mounts available (any windows box) try making sure that works to validate cifs at least.
alternative might be smbfs.
Thank's @robi !
I've this situation:
/sbin$ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.8-1ubuntu1.1 Candidate: 2:6.8-1ubuntu1.1 Version table: *** 2:6.8-1ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.8-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Also mount.cifs is available.
If there are other cifs mounts available (any windows box) try making sure that works to validate cifs at least.
This step is not totally clear how to perform...
@p44 you can follow here:
@robi Thank's Robi, I'll go deeper inside the problem fixing.
Just to check, is this a Hetzner storage box? If so be sure to have turned samba shares on at the Hetzner end (I had a similar issue and this resolved it for me)
I had the same problem. I use the following entry in fstab:
//XXX/XXX /media/backups_cifs cifs uid=yellowtent,gid=yellowtent,username=XXX,password=XXX,vers=3.0,noperm 0 0
The target directory must be created first.
@jdaviescoates Yes is Hetzner box. Works perfectly on two other Cloudron istances. Enabled "Samba shares" and "External Reachability".
On two works fine, another one no...
@danigl Thank's a lot, the targeted directory is created first. Just a question: why you add the "vers=3.0" parameter?
Yes is Hetzner box.
It may just be an issue with Hetzner. As you've seen, recently my backup hetzner storage box somehow unmounted itself during a backup and I needed to restart for it to mount again.
Assume you've tried restarting your server already?
@jdaviescoates Maybe is Hetzner side problem. I had a similar event few weeks ago and I opened a ticket to Cloudron support desk. I restarted server.
Also one week ago and also yesterday I had a similar problem.
For this case "Unable to mount /backups folder (Cifs)" I'm still investigating and I don't think is Hetzner side.
About unmounting problem, I was thinking to move to other storage service. Did you find any workarounds?
@p44 Given Cloudron is just app on ubuntu, maybe you can try to mount it in a separate ubuntu server on Hetzner? At that point, Hetzner support should be able to help you out hopefully.
@girish Totally agree with your suggestion. About the topic issue, the server where I running this specific Cloudron instance is not Hetzner.
But I just created a demo account to Wasabi to move forward and assure a backup.
where I running this specific Cloudron instance is not Hetzner
Oh, that gave me an idea. Could it be that there is too much latency for the CIFS mount to work? Or maybe there is some configurable latency delay setting for mounting. Usually, CIFS/NFS etc works well only in same data center.
@girish Thank's a lot Girish. Latency between two data centers is around 40ms... maximum 60ms... What's your idea?
Usually, CIFS/NFS etc works well only in same data center.
Interesting. Got a reference for this?
I think I purposely chose a different location for my Hetzner Storage Box from my Hetzner VPS just for a bit more redundancy (in case the VPS location get destroyed somehow).
@jdaviescoates Totally agree with this strategy. It could be interesting to chose a total different provider to achieve this goal.
I configured for Wasabi seems to be fast and resilient. But I have to well understand user policy and permissions.
When I use services like this, I'm always a little bit scared that folder can go public due permission problems.
I was only guessing about latency, I don't have any special expertise here. I found this article https://www.redhat.com/sysadmin/using-nfsstat-nfsiostat that might help debug further.
It could be interesting to chose a total different provider to achieve this goal.
Agreed. I'm going to investigate https://teuto.net/teutostack-openstack-public-cloud/?lang=en who apparently do S3 style object storage, who I came across here https://social.coop/@aligyie/105385317039616213
@robi thanks but the added context not mentioned is affordable storage space that is also powered by 100% renewable energy.
@jdaviescoates that is very specific
@p44 Did you get the issue sorted with the Hetzner Storage Box? I am facing the same problem and cannot work out why it is not mounting. "Samba Shares" and "External Reachability" are enabled but I keep getting the error 'mount: bad usage'.
@ccfu Which Storage Box datacenter are you using? Source data is hosted on Hetzner, or on a different provider?
@p44 The Storage Box is in Falkenstein. The Cloudrons I am attempting to set this up with are also both with Hetzner, one in Falkenstein, the other in Nuremberg.
First of all, let's try to reproduce my working configuration:
- Create a subfolder in root Hetzner Box Folder
- Create a Hetzner Box Sub User (eg. sub1)
- Assign Sub User to created subfolder
- Enable Samba to Sub1 user
On Cloudron instance:
- create /backups_cifs dir
Then, add this row in etc/fstab:
//u123456-sub1.your-storagebox.de/u123456-sub1 /backups_cifs cifs uid=yellowtent,gid=yellowtent,user=u123456-sub1,pass=PASSWORD,iocharset=utf8,x-systemd.automount 0 0
u123456 is the Hetzner Box ID
sub1 is the sub user name
PASSWORD is Hetzner Box given password
@p44 I'd recommend trying the instructions and mount code provided by Hetzner:
That's what I did and it's been working fine.
@jdaviescoates Thank's, I pasted my current working configuration
@ccfu Let us know