Search results

Thanks, while not the same output, I think it could serve my purpose well. Looking at the journal output below, I think I can grab what I want with this command. job_log="$(journalctl --no-pager -u pvescheduler _CMDLINE="task ${TASK_ID}" | tail --bytes=100000)" journalctl -n19 --no-pager -o...

In my testing, this file does not exist until after the job has fully completed, aka after my hook script is called for the job-end phase.

I am working on a hook script to integrate with a self-hosted version of Healthchecks.io when backing up my VM/LXCs to PBS. I have almost everything how I want it, but need a way during the Job-End phase to determine if there were any errors during the backup process. I was just going to parse...

Damn, ok. Well I guess I'll just stick with my 2Gb USB to boot off of.

Still not working, here is the output of the init command. $ sudo proxmox-boot-tool init /dev/nvme0n1p2 Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. UUID="4108-9365" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="nvme0n1"...

Ok, so if I understand correctly, the kernel only is installed on this partition if using UEFI? My motherboard does not support UEFI, so I should be good to go?

I am in process of migrating to use the PBT and it looks like everything is processing correctly as per the documentation. However, when I run proxmox-boot-tool status, I get the following output. $ sudo proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount...

That worked, thank you! May I ask where you found that change documented? It seems redundant to set that value there and for the storage option as well.

More details in this Github issue: https://github.com/ansible-collections/community.general/issues/3956 I am unable to create an LXC container in v7 via the API if I use the rootfs option to specify the disk size. If I omit the rootfs option, the container is created successfully. I have tried...

I don't believe so, o, p, q are regular disks, a-n and r-v are on the HBA.

Hello, I am unfamiliar with this bash convention, how can I setup multiple ranges? ex. char_index=({a..n,r..v}) In this case drives o, p, q need to be queried normally.