Latest activity
-
FFrank-75 replied to the thread VM Migration error.Thanks for your patience, but I just couldn't work on it yesterday. Here it is: source: root@DL160gen9:~# pveversion -v proxmox-ve: 9.2.0 (running kernel: 7.0.14-8-pve) pve-manager: 9.2.6 (running version: 9.2.6/7f8d010005bd72cb)...
-
Ddbrega replied to the thread no ssh and GUI access.make add as this screenshot but after restarting, I sent the requested files as attachments, and you told me that the change hadn’t been made. However, now that you’ve told me that the change appears to be in place on your end, the system is...
-
-
JJohannes S reacted to gyptazy's post in the thread ProxmoxVE and the shared root account for update/upgrades. with
Like.
What is stopping you from executing this by sudo, as you already mentioned this? I mean, ProxPatch exactly supports this for exactly this reason ;) -
Xxybo replied to the thread Wrong default bootloader entry: "Reboot into firmware interface".Have you checked this https://forum.proxmox.com/threads/advice-needed-upgrade-pve-8-to-9-using-systemd-boot-with-zfs-rpool-uefi-and-no-secure-boot.181956/
-
Jjedie replied to the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error.Hab mal einen Fall aufgemacht: https://bugzilla.proxmox.com/show_bug.cgi?id=7919
-
J_--James--_ replied to the thread ProxmoxVE and the shared root account for update/upgrades..The workaround isn't the issue. The issue is first-party ownership. I shouldn't have to deploy ProxPatch or another community project to achieve an enterprise identity model for one of the most fundamental lifecycle operations of the platform.
-
Jjedie replied to the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error.Und neu gebootet mit "intel_iommu=off" gibt es offenbar auch Fehler in relation zu dem Problem hier: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000080bffefff] System RAM [ 0.000000] NX (Execute Disable) protection: active [...
-
gyptazy replied to the thread ProxmoxVE and the shared root account for update/upgrades..What is stopping you from executing this by sudo, as you already mentioned this? I mean, ProxPatch exactly supports this for exactly this reason ;) -
JohnnieKF replied to the thread backup connect failed: command error: failed to set owner on s3 backend.Unfortunately some data's been missed off the end there: 400 Bad Request: [client [::ffff:192.16>... Can you try grabbing this from the WebUI where the text should be wrapped? Or try: journalctl -u proxmox-backup-proxy --since "1 hour ago"... -
J_--James--_ replied to the thread ProxmoxVE and the shared root account for update/upgrades..You're still conflating execution context with authentication. The process will always execute as root. My point is that no administrator should have to authenticate as a shared root identity to initiate that process. That's why sudo, polkit, and...
-
Wwaltar reacted to Bu66as's post in the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error with Like.
Das ist ein eingegrenztes Problem, jedie hat die eigentliche Arbeit schon gemacht. Ich häng mich mit einem fachlichen Punkt dran (VT-d/IOMMU ist die Ursache, der XFS-Fehler ist nur Symptom). Der XFS-Fehler ist hier gar nicht das eigentliche...
-
Iinfraerik replied to the thread backup connect failed: command error: failed to set owner on s3 backend.I see a couple of entries like this: Aug 04 14:12:57 syn-pbs proxmox-backup-proxy[628]: Upload backup log to datastore 'ImpossibleFR', root namespace vm/100/2026-08-04T12:03:51Z/client.log.blob Aug 04 14:14:41 syn-pbs proxmox-backup-proxy[628]...
-
Wwaltar reacted to jedie's post in the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error with Like.
So, nochmal ein paar tests gemacht. Mit der "Xeon E3-1241 v3" CPU. Die selben Probleme gibt es auch mit dem Proxmox Backup Server. Aber ist nicht verwunderlich, weil auch XFS als Boot mit den selben Kernel. Hab noch Kernel 6.17.4-2-pve und...
-
Eet1000 posted the thread [SOLVED] S3 backup hangs proxmox-backup-proxy in Proxmox Backup: Installation and configuration.Hello, I'm trying to back up some VMs and CT to a S3 bucket. PBS is a VM running on PVE. My cache is a dedicated ext4 disk, mounted on /var/cache/pbs-s3/, which is hosted on a ZFS datastore. Regularly, the backup job hangs in a middle of a...
-
Jjedie replied to the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error.Ja, ich werde GRUB_CMDLINE_LINUX='intel_iommu=off' in der /etc/default/grub setzten.
-
JJohannes S replied to the thread ProxmoxVE and the shared root account for update/upgrades..But if you do an update you also get the possibility to execute code that way. I'm aware of the issue with heavily regulated environments. My point is that introducing such a feature might check a box but won't change the fundamental security...
-
shanv replied to the thread backup connect failed: command error: failed to set owner on s3 backend.Hi, > Running the backups, I keep seeing the following errors on certain VMs: Does this mean some VM backups are working fine to the s3 datastore and some are not? Please also run the following S3 client sanity check and share the output... -
Wwaltar replied to the thread Hello, I need to change the IP of one host for corosync network link0..Save your /etc/pve/ha/resources.cfg ~/resources.cfg.save touch ~/resources.cfg mv ~/resources.cfg /etc/pve/ha/. Change IP manual in /etc/pve/corosync.cfg AND (!!) give it a "1" new higher config_version (below in config) BEFORE (!!) saving, eg...
-
JohnnieKF replied to the thread backup connect failed: command error: failed to set owner on s3 backend.The detail you need is on the PBS side. The actual S3 response will be logged there rather than the summarized message PVE gives you. Could you check the task log for that backup in the PBS UI, or check the journal around the time it failed...
-
Jjedie reacted to Bu66as's post in the thread Kernel 6.17.2-2-pve bootet nicht: XFS log recovery write I/O error with Like.
Das ist ein eingegrenztes Problem, jedie hat die eigentliche Arbeit schon gemacht. Ich häng mich mit einem fachlichen Punkt dran (VT-d/IOMMU ist die Ursache, der XFS-Fehler ist nur Symptom). Der XFS-Fehler ist hier gar nicht das eigentliche...
