Search results

add log smbclient connection smbclient //uXXXXXX.your-storagebox.de/uXXXXX-sub1 --user uXXXXX-sub1 -d 5 cat /proc/fs/cifs/DebugData

HSB support ver=3.11 mount mount.cifs //uXXXXXXX.your-storagebox.de/uXXXXXX-sub1 /data/HSB -o credentials=/etc/HSB,nounix,vers=2.0 --verbose mount.cifs kernel mount options: ip=78.47.*4.**,unc=\\uXXXXXX.your-storagebox.de\uXXXXX-sub1,nounix,vers=2.0,user=uXXXXXX-sub1,pass=******** mount error...

After a long conversation with technical support Hetzner Storage Box (HSB) Team we found that my client (PVE) is trying to connect to HSB with smbclient to version SMB3_11 Using the smbclient directly negotiated SMB3_11 against the Storage Box. Please contact Proxmox Support for further...

This is a very interesting question, I already described that none of the versions that can be in the list - Does not work this pvesm add cifs hetzner --smbversion 3 --server uXXXXX.your-storagebox.de --share uXXXXXX-sub1 --username uXXXXXX-sub1 --password mypw --smbversion default --smbversion...

ok, where and what file can I change in proxmox itself so that the default smb versions is higher for connecting to CIFS?

Why do you think so? ~/.ssh# smbclient //uXXXXXX.your-storagebox.de/uXXXXXX-sub1 -d 0 -m smb3.0 -U uXXXXXX-sub1 -c 'l' WARNING: Ignoring invalid value 'smb3.0' for parameter 'client max protocol' Enter WORKGROUP\uXXXXXX-sub1's password: . D 0 Mon Aug...

Maybe 3.11 is too new. What about 3.0 or 2.1? root@pve:~/.ssh# pvesm add cifs hetzner --smbversion 3.0 --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...

# 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...

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 ...

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...

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...

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

@Dunuin Thanks for the explanation

Benchmarking_Storage

up

pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.128-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-6 pve-kernel-helper: 6.4-6 pve-kernel-5.4.140-1-pve: 5.4.140-1 pve-kernel-5.4.128-1-pve: 5.4.128-2 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 14.2.11-pve1...

why is it strange ? yes, /dev/sdd (typing mistake) raid6 using 2 tb disk 8 (12 TB Available space 4 TB Used for protection) all results on problems disk

Hi everyone! I have problem with my PVE 6.4-13/9f411e79 (running kernel: 5.4.128-1-pve) with Disk volume Disk model: PERC H730 Mini (raid6 2Gb*8) Disk /dev/sdd: 10.9 TiB create file system in parted: (parted) mklabel gpt mkpart primary 1 90% create file system ext4: mkfs.ext4 /dev/sdd1 done, I...

From my side, How i fixed that error Loaded Live CD Ubuntu 18.04 sudo fdisk -l Mount the filesystems # mount /dev/pve/root /mnt # mount --bind /dev /mnt/dev # mount --bind /proc /mnt/proc # mount --bind /sys /mnt/sys # chroot /mnt ls /lib/modules/ or ls /boot/*initrd* 5.4.34-1-pve...

Hi All, I have same problem but my Linux pve4 5.4.44-1 and can't load system Loading Linux 5.4.44-1-pve ... Loading initial ramdisk ... Tried load with 5.4.41-1, and 5.4.34-1 - same Loading Linux 5.4.34-1-pve ... Loading initial ramdisk ... Load 5.4.41-1 Please help, what i can do?