Search results

I am trying to restore a backup that is roughly 10GB in size however in the pct.config I manually referenced a mount point that was very large (excluded from backup). I cannot restore this backup via the GUI because it also wants to recreate the manually added mountpoint and I don't have...

Somewhere along the line I made a mistake and I suspect it happened when I was expanding storage on a mountpoint. I have storage allocated to the following CT but I am getting conflicting storage sizes. As a result and it seems to be negatively impacting performance on this CT once the disk...

I've messed something up along the way and need a little guidance to see where I have gone wrong! Kernel Version Linux 6.5.11-7-pve (2023-12-05T09:44Z) Manager Version pve-manager/8.1.3/b46aac3b42da5d15 Interesting it references dm3 which doesn't seem to exist in /dev/ Alos...

These are some of the the last logs before the system hangs/becomes completely unresponsive. I have to powerfail to get it back online. From what I gather corosync reports host 2 link seems to be going down repeatedly. What else should I be looking at to continue troubleshooting? Aug 26...

Kernel Version Linux 5.15.108-1-pve #1 SMP PVE 5.15.108-1 (2023-06-17T09:41Z) PVE Manager Version pve-manager/7.4-16/0f39f621 Jul 20 14:45:12 pm systemd-logind[7892]: Got message type=method_call sender=:1.2 destination=:1.1 path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties...

This morning my normal scheduled backup ran however the lxc would not start after the backup completed. Error after trying to start. lxc-start 113 20230704025941.778 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor lxc-start 113...

I noticed the syslog was filling up with the following message over and over. Can someone help me understand what I am seeing here? Kernel Version Linux 5.15.102-1-pve #1 SMP PVE 5.15.102-1 (2023-03-14T13:48Z) PVE Manager Version pve-manager/7.4-3/9002ab8a Apr 07 23:03:56 pm systemd[1]...

I replaced my i5-10600K with a i7-11700K (ASUS PRIME Z590-V MB). Booted up and Proxmox detected and identified CPU. Ran updates. Rebooted. Noticed my Open Media Vault VM which I pass through iGPU for plex transcoding is not booting. (*knew I forgot something*) VM still had the PCI passthrough...

Not sure what I did or what changed. Recently I had to reboot for some updates and to upgrade some RAM. I noticed my power consumption was about 20-30w higher than usual and I thought maybe that was because of the ram... then I recalled I dont have a cron setup for my cpu scaling governors...

I recently reinstalled netdata and have been receiving notifications like this: Output of ip -s link show vmbr0 20: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether fc:34:97:a1:31:7d brd ff:ff:ff:ff:ff:ff RX...

I feel that right out the gate I might be lacking details so let me know what what else you might need from me. I plan on dropping in a a new PCI card and I know it is going to shift addressing/naming and ultimately mess with my PCI passthrough, my NIC config (which is PCI), and whatever else I...

Try and say that that three times fast! So is it possible for me to back up my backups to backblaze.. or any other location? I could backup the datastore directory... but its thousands and thousands of directories (chunks)... not sure that would be feasible.

Can someone help me understand this error? /var/log filled up super quick eventually bringing my host system to a halt. I get this when I start my Win10 VM: Mar 7 18:45:13 pm kernel: [ 3976.900941] ------------[ cut here ]------------ Mar 7 18:45:13 pm kernel: [ 3976.900941] WARNING: CPU: 11...