Search results

My workaround is to just run a @reboot crontab with the following cmdline: @reboot /sbin/ethtool -C ens7f0 rx-usecs 0 && /sbin/ethtool -C ens7f1 rx-usecs 0 Don't forget to replace ens7f0 and ens7f1 with your network interfaces

I ran it on the physical ones.

thanks, an enhancement request has been filed: https://bugzilla.proxmox.com/show_bug.cgi?id=2911

Hi, I was trying to set-up fail2ban for Proxmox Backup Server and I encountered the issue, that PBS does not log the rhost, instead it just logs "unknown". I have installed PBS directly on a PVE host. proxmox-backup-api[27055]: authentication failure; rhost=unknown user=root@pam msg=AUTH_ERR...

This issue is still present with the latest kernel version 5.4.41-1-pve.

My Desktop is running Ubuntu 20.04 and can connect to the target host using SMB 3.0 without any issues.

What would be the next debugging step? Creating a tcpdump and comparing the outputs?

Alright, so here are all the dmesg logs. They are completely unfiltered, the username has been anonymized.

Alright, so here is the usual mount.cifs output: mount.cifs --verbose //***.your-storagebox.de/backup /mnt/pve/storage-box -o user=***,pass=***,vers=3.0 mount.cifs kernel mount options: ip=195.201.107.44,unc=\\u205813.your-storagebox.de\backup,vers=3.0,user=***,pass=******** mount error(2): No...

Sorry, my fault. Here is the proper error log now.

I am experiencing the same issue with the same network card, as seen below. lspci -vv -t|grep 03.2 +-03.2-[07]--+-00.0 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection My syslog looks like this as well: [...] Apr 14 20:43:02 *** kernel: [2413144.982743] pcieport...

Yes, I did run this on the PVE Host and the mount failed according to dmesg with the following output: [174079.130370] CIFS: Attempting to mount //***.your-storagebox.de/backup [174084.520729] CIFS VFS: cifs_mount failed w/return code = -2

the ubuntu-vm is running Kernel Version 4.15.0-96-generic and cifs-utils (2:6.8-1) Your provided command threw the following error: -bash: syntax error near unexpected token `2' Therefore I have used the following command for strace: strace -f -o /tmp/mount.cifs.log mount.cifs ... I have...

Changing the position of the verbose parameter in the mount command did not affect the output in any way. It does not output more debugging information than previously. I have also checked dmesg for any useful information, but everything it says is [174079.130370] CIFS: Attempting to mount...

Here you go, Samba Version 1.0: mount.cifs //***.your-storagebox.de/backup /mnt -o user=***,pass=***,vers=1.0 --verbose mount.cifs kernel mount options: ip=195.201.***.***,unc=\\***.your-storagebox.de\backup,vers=1.0,user=***,pass=******** 2.0 mount.cifs //***.your-storagebox.de/backup /mnt -o...

I don't believe that is the case. I have also tried mounting the SMB Share from inside one of my Ubuntu 18.04 VMs, which works perfectly with any smb version. From what I have discovered, I am experiencing the same issues as @Razva who has started this thread.

They are all running on Proxmox VE 6.1

I wouldn't say so. I can mount the Hetzner storage box on one of my Hetzner Proxmox Hosts and on my homelab servers without any issues using the Proxmox GUI.

Hi, I can replicate the issue on my OVH host as well. With SMBv1 it mounts, with v2 or v3 it doesn't. I am running pve-kernel-5.3.18-2-pve. Here are the outpots of the cifs mount command with --verbose 1.0 mount.cifs //***.your-storagebox.de/backup /mnt/pve/storage-box -o...

I am currently using this server as a node without any issues for almost half a year now.