Search results

Hi, we've been using our own template (users, signatures, webmin, etc) for new CT based on a previous Debian 8 which we've been updating to 11. In order to have a proper a minimal CT template we started to personalize it again based on PVE's official Debian 11 template since a few things might...

Thanks that helps a lot. I have no intention of masking, as it might affect updates and that is why asking for some guidance about this. As for the firewall and login, I assume if it's not activated on the host or VMs it would not log anything anyway even if our firewall is using iptables. I...

Thanks @t.lamprecht for the detailed response regarding logs. We will look into that and review. For the tmps option we've been considering log2ram or a safe way to limit the tmpfs for certain logs without a flooding risk which is our only concern. But back to the services you mention: So I...

This has become a firewall discussion now, apparently. In our case I'll say we do use iptables, but rules are generated via CSF, including on the containers. In any case, I can imagine that the firewall service running would not likely affect performance, so not terrible concern with it. In any...

I understand this thread is old but as it still a "gray" area in PVE7, may I suggest for an easy way or a wiki document explaining how to disable unneeded services in single server PVE installations. In our case with PVE 7 we've stopped and disabled systemctl stop pve-ha-lrm pve-ha-crm corosync...

Hi, wondering if anyone had any luck with this setup or can point to an up-to-date guide to get ideally unprivileged and rootless docker. Alternatively, I'll just have to consider one or both or maintain our current docker on KVM if I can get a proper way to mount and share host directories. I...

We use it too and yes... quite a bit of tweaking of its alerts is required.

Hi, after a long time and due to an increase in used size of our main thinpool we realised we were having an issue like these: https://forum.proxmox.com/threads/lvm-horror-proxmox-reports-lvm-thin-full-when-actual-vm-disk-usage-low.108218/#post-464967...

Also very interested on this. We are running docker servers in VM as well as LXC on LVM with pve 6. We prefer lxc mainly for the bind mount options so unclear now if the new issues are due to pve7 or ZFS so it would be interesting to know before we upgrade. I understand the long reluctant...

Thanks, although we believe it was within host limits, that seemed the issue.

We have a windows 10 server running on a KVM for a while over PVE 6.4-4 We were trying create an updated version with a different W10 version on a new KVM created from scratch. We installed all correctly but after a few days we suddenly noticed that when we boot one of both... the other kvm...

Sorry for updating this old thread. Wondering if this method (just renaming) is still valid for Ubuntu 20 minimal LXD found at http://cloud-images.ubuntu.com/minimal/releases/focal/ or any other recommended source to create a minimal Ubuntu 20 container. thanks.

Additionally we've now noticed that one of our thin-pools has allocated the lvol0_pmspare on a disk we want to remove. Any way of moving it to another partition within the group?

We've now moved the mdadm + lvm to sinle partitions that we have included in the pve group, but we are now rather confused with the possibility or not of a lvm type raid1 converted to a thin pool. This is, can a thinpool be raid1 type as well? We have done something like: lvcreate -L 240G -n...

Yes, under the LVM group.

Further investigating these the filesystem corruption seem to have stopped by returning to kernel 5.4.65. We had similar issues when running rescue enviroiment under debian with kernel 4.19.0-12 which I assumme is perhaps the one PVE 5.4.73 is derived from, which would explain is something...

Due to some issues on the system we are considering moving from our lvm over linux raid to lvm-raid configuration. As I understand I can convert any LVM LV to thin I am assumming I can do so too with a mirrored (raid1) LV. Anyone has experience with this setup and implications I should...

We've now confirmed the this seems to have started after updating and running with kernel 5.4.73. After reconfirming no aparent phisical errors on NVM units, memory or power supply, our most reasonable conclusion is this is related to some form of issue with the linux raid10 bellow the LVM...

We are actually investigating how that could have happened. The latest kernel and its initram was correctly installed and updated and supposedly no manual selection was done, so we are now completely uncertain if the issues came up while running 5.4.73-1 or 5.3.10-1. Our rescue disk is a debian...

We've been struggling for a couple of days with an undetermined issue with corrupted filesystem on our root (LVM /dev/pve/root) and data (LVM /dev/data/home). Suddenly started reporting EXT4 errors till the system became unstable. Nov 30 00:05:52 e20home kernel: [543969.097160] EXT4-fs error...