Update - turning off IGFX multi-monitor in my bios appears to have fixed it? I am not certain why, but I have gone 24 hours without a crash in either an application or VM so far.
Had the exact same issue as OP trying to install to Supermicro mainboard. Here to confirm that the "nomodeset" grub edit finally got me past the graphics incompatibility error and on to the install as well ...
cache=none leaves the cache of the storage system enabled, use directsync instead. See here for comparision of caching modes https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache
I would prefer the second one since with that you don't need a network connection for the verify and garbage-collection jobs. The German forum had a thread on it...
Ok. I'll do some investigation. I would just rebuild the container but I dont want to lose all the data. Ironically its the documentation on setting up proxmox etc that I've created.
Hey everyone ... I figured it all out .... .... lost about half my head of hair .. and my loved ones are avoiding me for being so grumpy .. but i WON...
OK so what i did was ... With the ESP32c6 Plugged into a USB port. in shell as root ...
I was using nic0.
/etc/network/interfaces returns:
auto lo
iface lo inet loopback
iface nic0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.18/24
gateway 192.168.1.1
bridge_ports nic0
bridge_stp off...
The init script responsible for settings /etc/issue is /etc/init.d/pvebanner, a small perl script that updates the file on every boot.
sudo update-rc.d pvebanner remove
will disable the script and allow you to set /etc/issue manually (we use...
Just upgraded from 8.1.x to 9.1.2 and noticed such messages here in system log, too:
However, I've already rebooted (after upgrade) and still continously get those messages. Any hint how to stop spamming my logs?
FWIW, I do see those messages...
I re-enabled the Debian repositories as suggested and ran `apt update`.
Everything updated correctly and there were no errors (output below).
However, the web GUI issue remains unchanged: the directories under `/usr/share/pve-manager/`
are...
LXC containers share the same kernel as the host system (proxmox) so it will be hard finding your specific logs. I could be wrong as ive never checked lxc logs, either way i don't think its the lxc container issue it is likely to be an issue with...
I would prefer the second one since with that you don't need a network connection for the verify and garbage-collection jobs. The German forum had a thread on it...
Update: I finally found the issue (i think) this is what i did, for those that may stumble across this thread.
I went in and rechecked the esxi host and saw that a snapshot had been created, i think by our backup manager, proxmox does not like...
If you say so...
The server has two network interfaces, a cable based one and a wireless adapter. Both report state DOWN. Which one were you using to connect the server to the network?
And would you like to post the content of file...
Tatsächlich funktioniert das Backup aktuell mit allen VM und Containern auch auf „Snapshot“ (ich hab aber nichts geändert).
Irgendwie finde ich den Backup Job für die einzelnen Maschinen nicht..
Wo könnte ich das im Zweifel umstellen ?
I would prefer the second one since with that you don't need a network connection for the verify and garbage-collection jobs. The German forum had a thread on it...