Search results

  1. C

    Correct procedure for zpool removal

    Great, You've done it through the gui. Perfect. If you can reboot it's fine. I usually can't do it so I use to delete the disk interface via /sys. You're welcome. Greetings, Chema.
  2. C

    Systemd-Logind: Fail to connect to DBus

    Good morning, I've located the problem. It has nothing to do with any bug or upgrade related errors. The issue, was that the mountpoint of some backups done via ZFS send/recv pointed to /. root@ve0:~# zfs get mountpoint | grep -P 'pve-1 ' Backups/rpool_dirty/ROOT/pve-1...
  3. C

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

    Hi, I'm linking this here. https://forum.proxmox.com/threads/systemd-logind-fail-to-connect-to-dbus.106174/ Last step may indicate that there's an issue with lxcfs. Considering that pve-kernel has fuse built in, I think that it would make sense. Does anyone have issues with LXC containers...
  4. C

    Correct procedure for zpool removal

    I'm not sure: do you want to import the pool on other machine or not ? One of these: Remove pool via gui. Correct me if im wrong: this just will remove entries from the file. Edit /etc/pve/storage.cfg, remove entries linked to your pool (consider that you may have subdirectories referenced...
  5. C

    Systemd-Logind: Fail to connect to DBus

    I've been checking configs on the other cluster member. As outlined on: https://forum.proxmox.com/threads/dirtypipe-cve-2022-0847-fix-for-proxmox-ve.106096/#post-456739 everything worked fine on this one. Errors arised when I've upgraded this node. As far as there are notable diffs between...
  6. C

    Systemd-Logind: Fail to connect to DBus

    I'll add some information here: I've tried both kernels 5.15 & 5.13 same bootconfig. The results are the same. Kernel Cmdline initrd=\EFI\proxmox\5.15.19-2-pve\initrd.img-5.15.19-2-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on acpi=on iommu.strict=0 mitigations=off elevator=deadline...
  7. C

    Systemd-Logind: Fail to connect to DBus

    Hi, After upgrading dirtypipe from pve-no-subscription. :~# pveversion --verbose proxmox-ve: 7.1-1 (running kernel: 5.13.19-5-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-12 pve-kernel-5.13: 7.1-8 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-5-pve...
  8. C

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

    Great! Both clusters with enterprise license are working fine: 2x Dell R720 - Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz - ZFS 4x HP DL385 G10+ - AMD EPYC 7452 32-Core Processor - HA, Ceph Not a single issue on Windows hosts. I've did not observed any of the issues you mentioned before on...
  9. C

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

    Hi guys, Thanks for both updates! I've just launched this on our test cluster. Everything good. Kind regards, Chema.
  10. C

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

    Good evening, I see the commit here for version: pve-manager/7.1-10/6ddebafe (running kernel: 5.13.19-3-pve) https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=95f0dbdf95bd74024ca6c266652448c08ad8e4b2 After apt update, pve-kernel-5.13 is not listed to be upgraded. At least, for this version...

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!