"Storage <name> not online" error when try to add Hetzner Storage Box using CIFS to Proxmox VE (6.4-13)

[ijonjic11]

Hello,

i'am having trouble with adding Hetzner Storage Box to Proxmox using CIFS method. I tried to add it in both ways, via WebUi and CLI. Both ways shows message:

create storage failed: storage 'zeusbackup' is not online (500)

I created folder on storage box (/zeusbackup, zeus is the name of Proxmox host),but i cannot see that folder when i scan available share folder (on WebUi and using cifs scan command).

Hetzner Storage is online,can ping it from host and login to it using sftp CLI command.

Proxmox (Debian 10 based) is also installed on Hetzner's server.

Does anyone have the same problem and is it solvable?

 

[fiona]

Hi,
could you share the output of

time smbclient //<host>/zeusbackup -d 0 -U <user>%<password> -c 'echo 1 0'

and the output of pveversion -v?

 

[ijonjic11]

Hi, no need for that, i manage to mount it. If someone need help in future i will share my way how i did it.

I first used CLI.

nano /etc/fstab

PASTE THIS (This line will mount storage automatically if server reboot):
//u279209.your-storagebox.de/backup /zeusbackup cifs iocharset=utf8,rw,credentials=/etc/backup credentials.txt,file_mode=0660,dir_mode=0770 0 0

On proxmox host i created /zeusbackup (mkdir /zeusbackup) folder (this is mount folder for CIFS mount).

credentials=/etc/backup-credentials.txt - create the same file (touch etc/backup-credentials.txt) on the same path and give it 0600 rights (chmod 0600 /etc/backup-credentials.txt). In this file paste username and password of Hetzner Storage, like this:

username=<username> (for me it is u279209)
password=<password>

CTRL-O -CTRL-X (Save and Quit)

Run following command:
mount /zeusbackup

df -H (to check if storage is mounted):
You should see smth like this:
//u279209.your-storagebox.de/backup 108G 1.7G 106G 2% /zeusbackup

After this, go to Proxmox WebUi and create directory storage.
WebUi-->Datacenter-->Storage-->Add-->Directory:
For ID enter name of the storage (per your choice)
Directory: /zeusbackup
Choose what type of data you want to store on this storage.

And that's it. You can now work with your remote storage like it is on your local server.

 

[fiona]

Hi, no need for that, i manage to mount it. If someone need help in future i will share my way how i did it.

I first used CLI.

nano /etc/fstab

PASTE THIS (This line will mount storage automatically if server reboot):
//u279209.your-storagebox.de/backup /zeusbackup cifs iocharset=utf8,rw,credentials=/etc/backup credentials.txt,file_mode=0660,dir_mode=0770 0 0

On proxmox host i created /zeusbackup (mkdir /zeusbackup) folder (this is mount folder for CIFS mount).

credentials=/etc/backup-credentials.txt - create the same file (touch etc/backup-credentials.txt) on the same path and give it 0600 rights (chmod 0600 /etc/backup-credentials.txt). In this file paste username and password of Hetzner Storage, like this:

username=<username> (for me it is u279209)
password=<password>

CTRL-O -CTRL-X (Save and Quit)

Run following command:
mount /zeusbackup

df -H (to check if storage is mounted):
You should see smth like this:
//u279209.your-storagebox.de/backup 108G 1.7G 106G 2% /zeusbackup

After this, go to Proxmox WebUi and create directory storage.
WebUi-->Datacenter-->Storage-->Add-->Directory:
For ID enter name of the storage (per your choice)
Directory: /zeusbackup
Choose what type of data you want to store on this storage.

And that's it. You can now work with your remote storage like it is on your local server.

Could you still run the command from my first reply? If there is a problem that can be fixed in Promxox VE, I'd like to do that, so that fewer people need such a workaround, which has downsides:

• Proxmox VE won't be aware that this is a network storage. You can use pvesm set <storeid> --is_mountpoint 1 so that it will at least recognize when the storage wasn't mounted for some reason.
• You need to set up the mount on each node individually.

Stupid question: in your first screenshot the share is called zeusbackup but in the mount command it's called backup?

 

[ijonjic11]

Hi,
could you share the output of

time smbclient //<host>/zeusbackup -d 0 -U <user>%<password> -c 'echo 1 0'

and the output of pveversion -v?

Output of time smbclient //u279209.your-storagebox.de/backup -d 0 -U u279209%<password> -c 'echo 1 0'

real 0m0.275s
user 0m0.031s
sys 0m0.004s

Output of pvevesrion -v

proxmox-ve: 6.4-1 (running kernel: 5.4.143-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-helper: 6.4-8
pve-kernel-5.4: 6.4-7
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.140-1-pve: 5.4.140-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve1~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.6-pve1~bpo10+1

Stupid question: in your first screenshot the share is called zeusbackup but in the mount command it's called backup?

/zeusbackup is folder on proxmox host (created to be mount point for storage). //u279209.your-storagebox.de/backup is provided by Hetzner's control panel (screenshot in the attachment).

 

[fiona]

/zeusbackup is folder on proxmox host (created to be mount point for storage). //u279209.your-storagebox.de/backup is provided by Hetzner's control panel (screenshot in the attachment).

So when you tried to add the storage via GUI the share had the wrong name?

 

[ijonjic11]

So when you tried to add the storage via GUI the share had the wrong name?

Entered all the information needed and on the bottom there is "Share" drop-down menu which is actually cifs scan (i think) command in back-end. When i click on it, it start "Scanning" process and find 0 share folders ( just blank drop-down list). Then i manually entered share folder that i previously created on storage. After that i clicked on Add, and create storage failed: storage 'zeusbackup' is not online (500) message appears.

 

[negative_creep]

Hi. i was have same problem, when my node used Ipv6. i've tried to ping my storage box from node, find that node resolve host to ipv6 add, then disabled ipv6 at node(i'm not use it) and after it resolves as ipv4 address -than all wass added completly

 

[SpiderQubit]

Hello, did anyone manage to fix this using pvesm? Or is the solution to mount it using fstab and then link the directory to proxmox? I have the same problem using the same storage provider (hetzner storage box).

 

[Minimy]

Here is my workaround

1. logon with the main account into the StorageBox via sftp with e.g. FileZilla and create a new folder, e.g. PMX backup

2.
Create a new sub-account (uXXXXXX-subX) under Hetzner Robot - Storage Box and assign it to the PMX-Backup folder

3.
logon @ Proxmox Terminal and create a folder

mkdir /mnt/HZ-BX

4.
create new directory in Proxmox->Rechenzentrum->Storage
ID: Hetzner-BX
folder: /mnt/HZ-BX
contents: Backup

5.
nano /etc/fstab

//uXXXXXX-subX.your-storagebox.de/uXXXXXX-subX /mnt/HZ-BX cifs iocharset=utf8,rw,credentials=/etc/HZ-BX-credentials.txt,file_mode=0660,dir_mode=0770 0 0

6.
nano /etc/HZ-BX-credentials.txt

user=uXXXXXX-subX
password=xxxxxxxxxxxxxx

exit

chmod 0600 /etc/HZ-BX-credentials.txt


7.
reboot Proxmox

8.
@ Proxmox Terminal df -H indicates the successful connection to the storage box

//uXXXXXX-subX.your-storagebox.de/uXXXXXX-subX 11T 4.3G 11T 1% /mnt/HZ-BX

 

[joge]

Of course you can add the Hetzner Storage Box via GUI and don't need any fstab workaround. The only thing you need to remember is that if you not use the Storage Box Admin Account but a Sub-Account the share is the username of the sub account not the folder (https://docs.hetzner.com/robot/storage-box/access/access-samba-cifs)

Steps

1. Create a sub account in the Hetzner Storage Box Settings pointing to the folder you want to use; enable Samba. Example User: u301XXX-sub1

2. In the Proxmox GUI, create a new Storage with the following config:

ID: Name of your Storage
Server: u301XXX.your-storagebox.de
Username: u301XXX-sub1
Password: XXX
Share: u301XXX-sub1

With this config I added the storage successfully and also created the first backup of my VMs. Even if you enter the username as Share, the content is stored in the folder you assigned to the user in the Hetzner Storage Box Settings.

Cheers

 

[cvhideki]

Hi joge

Of course you can add the Hetzner Storage Box via GUI and don't need any fstab workaround. The only thing you need to remember is that if you not use the Storage Box Admin Account but a Sub-Account the share is the username of the sub account not the folder (https://docs.hetzner.com/robot/storage-box/access/access-samba-cifs)

Steps

1. Create a sub account in the Hetzner Storage Box Settings pointing to the folder you want to use; enable Samba. Example User: u301XXX-sub1

2. In the Proxmox GUI, create a new Storage with the following config:

ID: Name of your Storage
Server: u301XXX.your-storagebox.de
Username: u301XXX-sub1
Password: XXX
Share: u301XXX-sub1

With this config I added the storage successfully and also created the first backup of my VMs. Even if you enter the username as Share, the content is stored in the folder you assigned to the user in the Hetzner Storage Box Settings.

Cheers

Hi I have the same problem with add Hetzner Storage Box via GUI

create storage failed: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) (500)

dmesg

CIFS: VFS: cifs_mount failed w/return code = -112

 

[fiona]

Hi,

Hi joge

Hi I have the same problem with add Hetzner Storage Box via GUI

create storage failed: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) (500)

dmesg

CIFS: VFS: cifs_mount failed w/return code = -112

error code 112 usually means host is down. Can you ping the host via name? Via IP?

 

[cvhideki]

Hi,

error code 112 usually means host is down. Can you ping the host via name? Via IP?

I was try insert IP address, and domain name, same situation
ping icmp_seq=3 ttl=58 time=28.8 ms
When I add that line:

mount.cifs //uXXXXXX.your-storagebox.de/uXXXXXX-sub1 /data/HSB -o user=uXXXXXX-sub1,pass=mypassword,vers=1.0 --verbose

mount in folder /data/HSB
like that post

pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-2-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-7
pve-kernel-helper: 7.2-7
pve-kernel-5.15.39-2-pve: 5.15.39-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

 

[fiona]

I was try insert IP address, and domain name, same situation
ping icmp_seq=3 ttl=58 time=28.8 ms
When I add that line:

mount.cifs //uXXXXXX.your-storagebox.de/uXXXXXX-sub1 /data/HSB -o user=uXXXXXX-sub1,pass=mypassword,vers=1.0 --verbose

mount in folder /data/HSB
like that post

Hmm, can you also manually mount it, if you use vers=default (which is what Proxmox VE will try to use)?

 

[cvhideki]

Hmm, can you also manually mount it, if you use vers=default (which is what Proxmox VE will try to use)?

previously unmount:

umount -f -a -t cifs -l

Yes, but have an errors:

mount.cifs //uXXXXXX.your-storagebox.de/uXXXXXX-sub1 /data/HSB -o user=uXXXXXX-sub1,pass=mypassword --verbose
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

#dmesg
CIFS: VFS: cifs_mount failed w/return code = -112

 

[fiona]

Ok, so that's the problem. Proxmox VE doesn't support mounting with vers=1.0, because there are security issues with that. Does mounting with vers=2.0 work? If yes, you can add the storage via pvesm, specifying --smbversion 2.0. Otherwise, I'd strongly suggest using a server with a newer version.

 

[cvhideki]

Ok, so that's the problem. Proxmox VE doesn't support mounting with vers=1.0, because there are security issues with that. Does mounting with vers=2.0 work? If yes, you can add the storage via pvesm, specifying --smbversion 2.0. Otherwise, I'd strongly suggest using a server with a newer version.

when I checked smb versions to hetzner storage box, i use the command:

smb3

# smbclient //uXXXXX.your-storagebox.de/uXXXXX-sub1 -d 0 -m smb3 -U uXXXXX-sub1 -c 'l'
Enter WORKGROUP\uXXXXX-sub1's password:
  .                                   D        0  Mon Aug  1 12:50:36 2022
  ..                                  D        0  Mon Aug  1 12:50:36 2022

                5368709120 blocks of size 1024. 4416901816 blocks available

smb1

WARNING: Ignoring invalid value 'smb1' for parameter 'client max protocol'
Enter WORKGROUP\uXXXXX-sub1's password:
  .                                   D        0  Mon Aug  1 12:50:36 2022
  ..                                  D        0  Mon Aug  1 12:50:36 2022

                5368709120 blocks of size 1024. 4399381340 blocks available

when use pvesm scan:

root@pve:/#pvesm scan cifs uXXXXX.your-storagebox.de --username=uXXXXXX-sub1 --password=mypassword
root@pve:/#

maybe you need to change some settings in the config on Proxmox?

 

[fiona]

when I checked smb versions to hetzner storage box, i use the command:

smb3

# smbclient //uXXXXX.your-storagebox.de/uXXXXX-sub1 -d 0 -m smb3 -U uXXXXX-sub1 -c 'l'
Enter WORKGROUP\uXXXXX-sub1's password:
  .                                   D        0  Mon Aug  1 12:50:36 2022
  ..                                  D        0  Mon Aug  1 12:50:36 2022

                5368709120 blocks of size 1024. 4416901816 blocks available

smb1

WARNING: Ignoring invalid value 'smb1' for parameter 'client max protocol'
Enter WORKGROUP\uXXXXX-sub1's password:
  .                                   D        0  Mon Aug  1 12:50:36 2022
  ..                                  D        0  Mon Aug  1 12:50:36 2022

                5368709120 blocks of size 1024. 4399381340 blocks available

when use pvesm scan:

root@pve:/#pvesm scan cifs uXXXXX.your-storagebox.de --username=uXXXXXX-sub1 --password=mypassword
root@pve:/#

maybe you need to change some settings in the config on Proxmox?

With pvesm scan it's not currently possible to pass the version, but it actually uses -m smb3, see here. In fact, the command should be pretty much the same as yours above. Can you do

export USER=uXXXXX-sub1
export PASSWD=<your password>
smbclient -m smb3 -d 0 -L uXXXXX.your-storagebox.de

and post the output?

And Proxmox VE will use vers=default when adding the storage (if not overriden) and man mount.cifs states:

 • default - Tries to negotiate the highest SMB2+ version supported by both the client and server.

So it's strange that auto-negotiation doesn't seem to work.
You can use

pvesm add cifs <storage ID> --smbversion 3.11 --server uXXXXX.your-storagebox.de --share uXXXXX-sub1 --username uXXXXX-sub1 --password <password>

to explicitly set the version.

 

[cvhideki]

With pvesm scan it's not currently possible to pass the version, but it actually uses -m smb3, see here. In fact, the command should be pretty much the same as yours above. Can you do

export USER=uXXXXX-sub1
export PASSWD=<your password>
smbclient -m smb3 -d 0 -L uXXXXX.your-storagebox.de

and post the output?

# smbclient -m smb3 -d 0 -L uXXXXXX.your-storagebox.de
Enter WORKGROUP\root's password:
Anonymous login successful
tree connect failed: NT_STATUS_ACCESS_DENIED
_________________________________________
# smbclient //uXXXXXX.your-storagebox.de/uXXXXXX-sub1  -m smb3 -d 0 '-L'
Enter WORKGROUP\root's password:
Anonymous login successful
tree connect failed: NT_STATUS_CONNECTION_DISCONNECTED

So it's strange that auto-negotiation doesn't seem to work.
You can use

pvesm add cifs <storage ID> --smbversion 3.11 --server uXXXXX.your-storagebox.de --share uXXXXX-sub1 --username uXXXXX-sub1 --password <password>

to explicitly set the version.

# pvesm add cifs hetzner --smbversion 3.11 --server uXXXXXX.your-storagebox.de --share uXXXXXX-sub1 --username uXXXXXX-sub1 --password mypw
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
create storage failed: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

#dmesg
CIFS: Attempting to mount \\uXXXXXX.your-storagebox.de\uXXXXXX-sub1
CIFS: VFS: cifs_mount failed w/return code = -112