Recent content by lpallard

OK this morning I logged in to the webUI and its back to normal. I consider this not resolved. What may have happened and why?

Sorry for those who may have read this post just before I resolved my issue with VLANs... Its not irrelevant to the issue below. Hello, I changed the static IP of my PVE node by modifying /etc/network/interfaces and /etc/hosts and /etc/resolv.conf and AFAIK everything seems OK (I can now...

OK I'm both stupid and lucky... When I recopied the /etc/pve/nodes/ I accidentally included the domain in the folder name.... PVE could not find the conf files because the folder name didnt match the node name.... After renaming the folder, and rebooted PVE, everything came back as normal.

Long story short, I tried renaming the hostname of my PVE single host (no cluster) and it turned into a nightmare. If I'd knew I would have NEVER tried this... Please bear in mind "old" hostname was "proxmox" and new hostname is "srv-vir01" Basically I followed...

Thank God I found this thread because I noticed today that PVE 7 is EOL soon (in less than a month) and I happen to also run PVE 7 on a pair of SAS drives connected to a LSI 2208 (ServeRAID M5016) controller and I feared upgrading from 7 -> 8 would cause massive issues... Did you get your...

Thanks @tom for the input. @mow : Since it seems to be only a cosmetic issue, I think I will hold off on kernel 6.1 until its tested and in production for a while...

@mow : same for me with "LSI MegaRAID SAS 2208 [Thunderbolt] (rev 03)" I still can see the arrays and everything else seems to be in order but I am running "Linux proxmox 5.15.83-1-pve #1 SMP PVE 5.15.83-1 (2022-12-15T00:00Z) x86_64 GNU/Linux" I understand kernel 5.15 should fix this...

Okay, I didnt think of the possible difference between GB and GiB..... Can the size parameter be omitted in the VMID.conf line so its auto detected? Moreover, if I understand you well, since for PVE "G" means "GiB", and the space of the drive is 278.46GiB, then if the total indicated in the...

So I have a volume group (highperf) containing two logical volumes (lv1 and lv2) sitting on a RAID1 hardware array. Array size is 278.46GB as reported by the RAID controller and LSI.sh monitoring script: Virtual Drive: 1 (Target Id: 1) Name : RAID Level : Primary-1...

Got it working. All I needed is to reboot PVE. Thats weird because the UPS was listed with lsusb and udev but somehow the apcupsd service couldnt bind to the USB port without a reboot of PVE.

Hello Oguz, yes I see them: they are highperf_lv1 to lv3 root@proxmox:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert highperf_lv1 highperf -wi-ao---- 120.00g highperf_lv2...

Upgrade to 7.0 went smooth, but re-adding existing LV's to the VM's would have been difficult to do without looking in the qemu-server/VMID.conf files to remember how I got this up & running back in 2014.... :) I couldnt find a way to detect the LV's from the WebUI and add them to VM's. The...

Do you mind explaining a bit what you did? I just installed PVE7.0 and followed the instructions of https://www.brunweb.de/configuration-of-an-apc-ups-under-proxmox/ to get APCPUSD up & running, but when I do "apcaccess status" I get APC : 001,017,0422 DATE : 2021-10-10 20:06:20 -0400...

I have an ancient Proxmox server running 3.2-4 with the following packages versions: proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve) pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1) pve-kernel-2.6.32-29-pve: 2.6.32-126 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1...

You do not understand how this works. PVE is accessible from a webpage (pve_ip:8006 or something similar) and NOT using a GUI which Teamviewer will bind to. In other words, it has no desktop manager and so on like a standard linux desktop OS. Its like trying to install teamviewer on a headless...