Search results

It won't work unless you have at least 1G empty space. You can try the opposite of that by first running lvreduce -L -1G /dev/pve/root then lvextend -L +1G /dev/pve/root but that can cause data loss if your drive is almost full or your data is scattered all over your drive.

Same issue, PVE & Grub version below. ❯ pveversion pve-manager/7.2-7/d0dd0e85 (running kernel: 5.15.39-4-pve) ❯ grub-install --version grub-install.real (GRUB) 2.04-20 I just booted up an Ubuntu Live ISO and ran the following command to extend the LVM size by 1GB. ❯ sudo lvextend -L +1G...

Installed the and tried out the the v5.15 kernel recently (pve-kernel-5.15.19-2-pve and pve-headers-5.15.19-2-pve). After installing the v5.15 kernel PCI passthrough stopped working even though on 5.13 it's working perfectly. My config: PVE v7.1-10, Ryzen 3600, Asus B450-F (BIOS version 4602)...

This is not a firmware issue, if it was Samsung would have fixed it by now. The "Error Information Log Entries" has been there since forever for Samsung SSDs and it has nothing to do with drive health. I have never faced any errors regarding this on any other OS or Hypervisor.

Same here using a Samsung PM983 (and Samsung 970 Evo Plus), PVE 7.1-10, Kernel version Linux 5.15.19-1-pve #1 SMP PVE 5.15.19-1.

Thanks! Issue fixed. One of my ISP seems to be blocking port 25 and 587, that was causing all the issues. {1} https://www.reddit.com/r/homelab/comments/5nzmm3/setting_up_the_proxmox_email_alerts/dcfihdw/ {2}...

I did provide a valid email at the time of PVE installation, do I need to do anything else to receive messages/notification via email? I removed it from the log before posting.

Mail queue was causing the issue, cleared it and the issue is gone. ❯ mailq -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- D75CB361C16 11490 Fri Jan 8 00:48:23 root@pve.lan (delivery temporarily suspended: connect to alt2.aspmx.l.google.com[2607:f8b0:4023:c03::1a]:25...

Proxmox querying Gmail/GSuite MX records 24/7, is this normal?

I guess I can just shutdown all the VMs and CTs and take backup of them. Is there a guide I can follow to delete and re-create the thin pool?

I want to know if there is any way to reduce size of the local-lvm? I would like to resize it and keep 100GB unallocated at the end of the SSD. > df -h Filesystem Size Used Avail Use% Mounted on udev 7.8G 0 7.8G 0% /dev tmpfs 1.6G 18M...