Search results for query: "hook script"

Was für ein Pre Hook Script hast du denn da hinterlegt?

Nach dem heutigen Update über die GUI kam am Ende dieser Hinweis zu GRUB: update-initramfs: Generating /boot/initrd.img-6.8.12-8-pve Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids...

I think that I might have had the same problem this morning and believe that I have resolved it. I updated a couple of Proxmox servers this morning via the GUI. I didn't notice any errors, but I was a bit distracted doing multiple things at once, so I am not absolutely sure that there weren't...

The limit for the global delay is 300 seconds. If this is not enough, the ct/vm-based one doesn't have this limitation. Eventually an approach with a hook-script getting active in pre-start phase might work. Let the script test for availability of the storage and continue only, if this is given...

I upgraded PVE on my NUC which ended with Your System is up-to-date Seems you installed a kernel update - Please consider rebooting this node to activate the new kernel. starting shell So, I rebooted, entered the BIOS/disk passwords and then I got: Welcome to GRUB! error: symbol...

Run the command. The command is the fix. Before the fix was implemented, the command you see was not outputted After you run the command(s), it will properly update grub and you'll be able to reboot without issues.

Hi all I'm getting same error after proxmox-kernel-helper upgrade from 8.1.0 to 8.1.1 I've understood that a fix has been already requested (thanks), but I haven't understood if I can do something right now before restarting proxmox as suggested after a kernel update Should I execute what's...

I also did an update today: Log started: 2025-03-06 09:51:51 (Reading database ... 82047 files and directories currently installed.) Preparing to unpack .../proxmox-kernel-helper_8.1.1_all.deb ... Unpacking proxmox-kernel-helper (8.1.1) over (8.1.0) ... Setting up proxmox-kernel-helper (8.1.1)...

OK.... After coming out of the debconf window: root@datto-ssd:~# dpkg --configure -a Setting up ssh (1:9.2p1-2+deb12u5) ... Setting up grub-pc (2.06-13+pmx5) ... grub-pc: Running grub-install ... Installing for i386-pc platform. File descriptor 3 (pipe:[38761230]) leaked on vgs invocation...

Hallo, heute kam ein Upgrade des Pakets proxmox-kernel-helper rein. Nach der Installation kam die folgende Meldung: Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.8.12-8-pve Running hook script 'zz-proxmox-boot'.. Re-executing...

Sounds like file level restore from PVE gui is a sacrifice you have to make in your particular environment. You have a 3rd party storage design requirement for manual intervention to bring that storage online. You could experiment with hooks and report back whether it helped. Good luck...

So I also just ran an update/dist-upgrade, got the message from the patch & followed the commands listed. I attach all output: Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade...

Ohh, yea, I did not put any blacklist on the host. I have updated the /etc/modprobe.d/pve-blacklist.conf # This file contains a list of modules which are not supported by Proxmox VE # nvidiafb see bugreport https://bugzilla.proxmox.com/show_bug.cgi?id=701 blacklist nvidiafb blacklist nouveau...

Okay I just ran proxmox-boot-tool init /dev/sda2 which seemed to work without errors. I got the output below: root@pbs:~# proxmox-boot-tool init /dev/sda2 Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. UUID="1D5B-900D" SIZE="1073741824" FSTYPE="vfat"...

I have installed proxmox 8.3.4, kernel - Linux 6.8.12-4-pve (2024-11-06T15:04Z) I went through the tutorial for PCI(e) passthrough and updated the /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot...

Here is the part of the term.log file when the update was started and finished. It is showing the special characters also that the interactive prompt outputted to the terminal. Before this last update it seems there are this kind of entries in the term.log file relating to grub stuff when the...

> For anybody looking to get this running, again, feel free to use the modules. If anybody looking for help, we are happy to support this, as good as we can in an open source-ish manner! I followed the instructions on the webpage but it's not working for me in an rpool-boot VM: - There is no...

Absolutely brilliant. Thanks a lot!

For whoever end up here, having issues. The tutorial is great, the hookscript that is suggested to change the args of the qemu before executing the VM doesn't work for me unless the following patch is applied. I'm on PVE 8.3.2.

Dear Proxmox, Community, Is it possible to run a simple hook script when a cluster event is triggered? Ex. A node goes down or is up again. I would like to change nodes pve-zsync schedule or config based on the nodes availability. Basically simulating the VM HA behavior but for a storage...