Search results

With “apctest” you can set the date again manually, maybe that will work. https://sourceforge.net/p/apcupsd/mailman/message/32125168/

Will a reboot fix it? @rzsis This is the same as removing it from the WebUI.

The topic is already being discussed here: https://forum.proxmox.com/threads/cannot-update-windows-11-to-24h2-cpu-not-supported.157850/

Ja, genau. So ist es.

Basically, it looks the way it should look. Please show me what's in your EFI partition in “loader.conf”. So mount one of your EFI Partitions on /boot/efi: On my example this is "sda2" NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 35G 0 disk ├─sda1 8:1 0 1007K 0 part...

HI :) bevor ich mir das jetzt im Detail ansehe... hast du deinem SSH-Key vielleicht ein Kennwort vergeben?

Das sollte dir helfen dein Thema zu lösen: https://deepdoc.at/dokuwiki/doku.php?id=server_und_serverdienste:ssh_mit_key_und_2factor

Really strange... I could not reproduce it here. And if you are currently a proxmox-boot-tool kernel list execute, does the newer kernel show up as pinned? Can you even manually boot the newer kernel from the boot menu? Do you use secure boot?

Should there be an error in ZFS, e.g. a device failure, too many read or write errors, an info mail is automatically sent to the email address stored under the root account. This works better with the integrated notification system. ZFS and BTRFS are both file systems that should be used on a...

Yes, BTRFS would work in a VM too. But the question is why would you want to use BTRFS in a VM? What do you hope to achieve by doing this? What is your goal?

That can be configured here:

Well, that was quite an odyssey. I'm very happy that you managed to do it. Good job!

Thanks for all your tests. I'm curious to see if it works with 8.1/8.2.

Ja diese Scripte sind ganz nett, aber man sollte vorher im Detail schauen was sie machen. Kann ganz schön in die Hose gehen ;)

Have you tested Kernel 6.11? apt install proxmox-kernel-6.11

Hmm... kannst du den CT bitte mal im Debug starten und das Log hier anhängen? lxc-start -n 101 -lDEBUG -o lxc-101.log Davon würde ich dir dringend abraten. Damit hast einen single point of failure. USBstick sterben gerne mal einfach so... wie wir ja alle wissen. Die von gibt es hier im Forum...

Ich hab hier auch noch ne 7er für special Tests am laufen. Du meinst vermutlich das LXC Menü? Heist hier auf Version 7 aber auch "Ressourcen". Sowas wie "USB Passthrough" gab es im Menü auch nicht: Kann es sein das du die Menü's verwechselst? Weil bei einer VM gibt es unter Hardware schon...

I already have the current version 0.1.266 running here. At least I couldn't find anything wrong. Couldn't find any other changlog either... :rolleyes: As far as we can see, Redhat has not provided a changelog for this version.

Bad Windows Updates... i guess? I would also recommend changing the CPUtype. At least on the default (simple remove qemu64), as this can result in better performance. Of course, CPUtype “Host” would be optimal. Is there a specific reason why you are still using Proxmox 7? This version has been...

It is possible that the errors coincided with the update to 8.3.x. Ok, let's go through things one by one: I've looked through my boot logs, and I don't have the message on any of my servers. So please have a look at your boot disks to see if they are OK. smartclt -a...