Recent content by iBug

  1. I

    TCP RST Packets dropped by pve-firewall

    A follow-up 4 years later: See my new thread #134423 and my bug report #4983.
  2. I

    TCP RST packets dropped by PVE Firewall

    After an hour's debugging, I draw the conclusion that it's a bug in PVE Firewall. I've submitted it as #4983. To whoever stumbling upon this issue, go add nf_conntrack_allow_invalid: 1 to your host firewall config. This is the best workaround available at the moment. The reason why the RST...
  3. I

    TCP RST packets dropped by PVE Firewall

    Worked out the ACK number issue: By default tcpdump prints sequence numbers relative to previous packets. Adding -S to tcpdump options shows the correct numbers. Nothing wrong on this side. Still wondering what's wrong with conntrack INVALID state.
  4. I

    TCP RST packets dropped by PVE Firewall

    I'm running into exactly the same issue as #56300. The previous thread was old and I have more details on that, so I thought I'd just open a new thread. PVE version is almost up-to-date: proxmox-ve: 8.0.2 (running kernel: 6.2.16-6-pve) VM → Firewall → Options → Firewall = No: No effect VM →...
  5. I

    Unable to get device for partition 1 on device /dev/mmcblk0

    Unfortunately no. Since Proxmox VE is Debian under the hood, some level of familiarity with Linux CLI is required. Basic tasks like text editing shouldn't be too hard if you follow some tutorials online. Good luck on your learning.
  6. I

    Migrating zfs pool from non-proxmox to proxmox

    Correct. Normally you just create another dataset for your VM/CT, like z-media/ampache2. If you really need the exact name, there's zfs rename to the rescue. In the zfs list output, if the mountpoint is a single dash, it's a ZVOL (obviously cannot be mounted by ZFS). If it's anything else...
  7. I

    Migrating zfs pool from non-proxmox to proxmox

    TASK ERROR: unable to parse zfs volume name 'ampache' Your ZFS volume z-media/ampache is a dataset, not a ZVOL volume that PVE is expecting. You should give it a ZVOL to work with, like zfs create -s -V 64G z-media/ampache. For the extra disk, it's because PVE scans the given storage source...
  8. I

    Migrating zfs pool from non-proxmox to proxmox

    1. ZFS keeps a record of which host OS last imported an array. If the array imports properly on the host but not the VM, try exporting it from the host first. You may also try zfs import -f in case of emergency but otherwise not recommended. 2. If the ZFS pool imports well, you can edit...
  9. I

    Unable to get device for partition 1 on device /dev/mmcblk0

    @namyounsu Thank you for the information. I've updated my blog article on https://ibug.io/p/49.
  10. I

    Will Proxmox provide Rsync access for the public repository (download.proxmox.com)?

    Trying to give this idea a bump. Given that Proxmox Offline Mirror tool is out, Rsync seems the best choice for it.
  11. I

    Will Proxmox provide Rsync access for the public repository (download.proxmox.com)?

    First, thanks to Proxmox GmbH for developing this wonderful open-source virtualization solution. I know of multiple universities and non-profits providing mirror for Proxmox repositories, and we're currently using lftp(1) to sync content via HTTP, which frequently causes de-sync. If Proxmox...
  12. I

    DirtyPipe (CVE-2022-0847) fix for Proxmox VE

    I can confirm pve-kernel-5.13.19-5-pve version 5.13.19-13 is having a good term with Windows KVM, including PCI passthrough (vfio-pci). Host is HP DL380 Gen 10 with Intel Xeon Scalable processors (Skylake). Thank you for the quick response.
  13. I

    vzdump causes iSCSI connection lost on one server model with PVE 7, but not on another model

    @avladulescu For the time being we did put pve-qemu-kvm on hold. When we found that 9 KB MTU solved the issue for us, we released the hold and followed the latest versions. We've been running fine since. @benh7 Glad that I could help.
  14. I

    vzdump causes iSCSI connection lost on one server model with PVE 7, but not on another model

    @avladulescu @benh7 Strangely enough, our issues were gone after enabling jumbo frame (9000 bytes MTU) on the management network where the problematic NIC is connected. You might want to give this a try unless you have incompatible devices. We were able to bisect the cause to QEMU 6.0 adding...
  15. I

    Boot failed after upgrading to 7.0-11

    At grub screen, you can press e to edit grub configuration before booting. At that point, you can remove quiet from the kernel command line and then boot. There should be more output available, usually enough for you to locate the issue, like missing files or initramfs modules. Alternatively...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!