Search results

thanks, that worked as well. But unluckily, it seems impossible to rescue that server from remote, as it gets stuck on that prompt: Cannot import 'rpool': pool was previously in use from another system. The pool can be imported, use 'zpool import -f' to import the pool. I can only hardly...

Thanks, that worked. I was just rbindmounting /run directly: $ zpool import -f rpool $ zfs set mountpoint=/mnt rpool/ROOT/pve-1 $ mount -t proc /proc /mnt/proc $ mount --rbind /dev /mnt/dev $ mount --rbind /sys /mnt/sys $ mount --rbind /run /mnt/run $ chroot /mnt /bin/bash init then worked...

Hi Stoiko. I have now tried to proxmox-boot-tool init the ESP partitions from a live system (Proxmox VE 7.3 on USB stick, UEFI booted) in chrooted environment, like this: Proxmox VE Installer: Advanced Options Install Proxmox VE (Debug mode) Ctrl-D root@proxmox:/# then running chrooted...

Hey @Stoiko Ivanov that was simply astonishing, your great support and in-depth knowledge! Thanks a lot for sharing and clearing up all my questions. I'll do the Live-CD fix / migration to UEFI when I find some time and are near the datacenter. Yes, that was it! `proxmox-boot-tool init` worked...

so, this previously was possible? why then no longer and why is such a complicated workaround needed? I don't quite get what's the point in proxmox-boot-tool then. I thought its sole purpose was to write kernel/boot configurations to both partitions, bios_grub and ESP. What's the difference if...

Thanks @Stoiko Ivanov I just find the output of proxmox-boot-tool status confusing then. I would have expected something like: $ proxmox-boot-tool status System currently booted with legacy bios XXXX-XXXX is configured with: uefi (versions: 5.15.74-1-pve, 5.15.83-1-pve), grub (versions...

On PVE Wiki: Host Bootloader it says: I still have some Proxmox VE systems which were installed in the old days. Some report: $ parted -l /dev/sda Model: ATA INTEL SSDSC2KG01 (scsi) Disk /dev/sda: 1920GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number...

On PVE Wiki: Host Bootloader it says: I still have some Proxmox VE systems which were installed in the old days. Some report: $ parted -l /dev/sda Model: ATA INTEL SSDSC2KG01 (scsi) Disk /dev/sda: 1920GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number...

GitLab runs perfectly fine in an LXC container on Proxmox VE! I am running several rather large GitLab instances (both CE and EE) in this environment, some of them for years and also some fresh installs, so can confirm it is working 100% fine. For those who followed above advice and feel a bit...

Hi there, Does the latest pve-kernel-5.13.19-6-pve version 5.13.19-14 (currently in pve-no-subscription) contain any improvements for CVE-2022-0847 from a security perspective? Cheers, Philip

@Fabian_E Thanks for your feedback. Did you consider feeding the rep_.* snapshot matching into official pve-zsync?

Thanks a lot @Fabian_E for this simple patch which does exactly what we needed! It is now tested and already runs on production. We can easily maintain this in the future, as anyway I have implemented a safety check which would bail out a pve-zsync backup run, if unpatched. But what hinders you...

Thanks @Fabian_E for explanation. We need daily/weekly/monthly backup rotations (for up to 6mo) and use zfs-auto-snapshot for that which makes it very painless. AFAIK, pve-zsync currently does not offer such a thing (apart from -maxsnap which is not an option - we cannot keep all pve-snapshots...

Hi there We have now used your pve-zsync for ZFS snapshot backups by pulling from remote hosts via SSH. This worked wonderful until your latest commit of pve-zsync 2.0-4 on master branch, namely this change: pve-zsync: Flip Source and Dest in functions to so jobs can share Dest...

filed the issue here: Bug 1730 - Process hiding in container (hidepid proc mount option) no longer works since LXC 2.1 no response yet. Thanks a lot for taking this upstream!

Thanks for your hints. I am using 100% Debian Stretch in all LXC containers, all running on Proxmox VE 5.1 host nodes. It was quite weird as half of the containers had the cap_net_raw+ep capabilities set on /bin/ping, the other half were missing it. Also on Proxmox host nodes, only half of the...

On Proxmox VE 5.1, inside an LXC container, I cannot ping with unprivileged user. It gives me the following error: $ ping google.ch ping: socket: Operation not permitted On the hostnode itself I can ping with both unprivileged user and root, but inside an LXC container only as root. The...

Hi @fabian Thanks for your feedback. Definitely looks like something is broken here. Are you aware of anybody working on it or are you going to look into it by yourself in more detail? Best regards, Philip

BUMP I still cannot get `hidepid=2` proc mount option running on latest Proxmox VE 5.1 (4.13.13-6-pve kernel). I tried it again using lxc.apparmor.profile as exactly described in my previous post from Sep 29, 2017. Won't work and I am not getting any apparmor error messages in syslog, checked...

Is there still no easy way to disable "New software packages available" messages in Proxmox VE 5.1? For us, this information is of no importance as anyway we are monitoring new package availability with apticron on every host.