Latest activity
-
Hello rmaxhost, I must admit that I probably do not understand what you're asking, sorry. When you install PVE from the installation .iso (usually from an USB stick) you can select ZFS and create a mirror, utilizing those two S3610. That's fine... -
JJohannes S reacted to UdoB's post in the thread We accidentally install proxmox os on VM pool with
Like.
Hello rmaxhost, I must admit that I probably do not understand what you're asking, sorry. When you install PVE from the installation .iso (usually from an USB stick) you can select ZFS and create a mirror, utilizing those two S3610. That's fine... -
JJohannes S reacted to alexskysilk's post in the thread Proxmox Storage Recovery Challenge: Help Us Design a Realistic Data Loss Experiment with Like.
I think you're going about this the wrong way. the payload of virtualization or standalong filesystem are not materially different. when I fire up testdisk on a block device, it doesnt care whether its a fileset of naked pictures or a root linux...
-
JJohannes S reacted to leesteken's post in the thread Proxmox Storage Recovery Challenge: Help Us Design a Realistic Data Loss Experiment with Like.
This is not recommended for running VMs on, and therefore not realistic, according to the community: https://forum.proxmox.com/threads/fabu-can-i-use-zfs-raidz-for-my-vms.159923/
-
JJohannes S reacted to leesteken's post in the thread Windows VM Software Update on Proxmox 7 with Like.
You could start a new cluster with the latest 9.2 on one node and restore VMs from backups. Start with one node (which your cluster should easily be able to miss) and test your most important VMs on it. Then extend it with more nodes and more VMs...
-
JJohannes S reacted to nekton's post in the thread Windows VM Software Update on Proxmox 7 with Like.
I am going to consider this issue "solved" since running the x86-64-v2-AES CPU seems to be the solution. I will start another thread after I read through the update wiki docs if I have questions. Thanks for those who chimed in. One thing I see is...
-
Llouie1961 replied to the thread Proxmox in vlan setup - Subnet issues.I use VLANs in my home lab, but when you set up Proxmox for the first time, you can't make it VLAN aware (at least I haven't figured out a way). So I go through the standard install, then from the console (no network required) I will edit...
-
DDenschen replied to the thread Upgrade von Proxmox VE 8 auf 9 scheitert – 404-Fehler im Enterprise-Repository.Unfortunately, it didn't work. Yesterday, I also updated a standalone host from 8 to 9 with the same content: Types: deb URIs: https://enterprise.proxmox.com/debian/pve Suites: trixie Components: pve-enterprise Signed-By...
-
Christian Kraus replied to the thread Upgrade von Proxmox VE 8 auf 9 scheitert – 404-Fehler im Enterprise-Repository.there is missing the line Enabled: true in the sources file put it on thew last line andtrx again but 404 means no access and for what i saw in enterprice repo there is only pve-manager: 9.2.20 available pve-manager 9.2.21 is available in the... -
DDenschen posted the thread Upgrade von Proxmox VE 8 auf 9 scheitert – 404-Fehler im Enterprise-Repository in Proxmox VE: Installation and configuration.Hallo zusammen, ich möchte einen Standalone Proxmox-VE-Produktionshost im Rahmen eines Wartungsfensters von PVE 8 auf PVE 9 aktualisieren. Dabei erhalte ich wiederholt 404 Not Found-Fehler beim Herunterladen mehrerer Pakete aus dem offiziellen...
-
You could start a new cluster with the latest 9.2 on one node and restore VMs from backups. Start with one node (which your cluster should easily be able to miss) and test your most important VMs on it. Then extend it with more nodes and more VMs... -
Stoiko Ivanov replied to the thread proxmox-boot-tool kernel pin silently ineffective with GRUB + ZFS root when NVMe device names change between boots.managed to reproduce the issue on a VM (instead of playing around with the naming of the block-devices and numbering, I added a second disk to a single-disk rpool (causing the device-name to change from /dev/sda3 to /dev/sda3_/dev/sdb3) - this... -
I am going to consider this issue "solved" since running the x86-64-v2-AES CPU seems to be the solution. I will start another thread after I read through the update wiki docs if I have questions. Thanks for those who chimed in. One thing I see is... -
Nnekton replied to the thread Windows VM Software Update on Proxmox 7.I am going to consider this issue "solved" since running the x86-64-v2-AES CPU seems to be the solution. I will start another thread after I read through the update wiki docs if I have questions. Thanks for those who chimed in. One thing I see is...
-
Hi, I advise running Memtest for a good couple of cycles. Successful installations in the past don't guarantee that the hardware is in working order now. This applies to RAM as well. I have experienced myself RAM modules running properly in PCs...
-
UdoB reacted to alexskysilk's post in the thread Proxmox Storage Recovery Challenge: Help Us Design a Realistic Data Loss Experiment with Like.
I think you're going about this the wrong way. the payload of virtualization or standalong filesystem are not materially different. when I fire up testdisk on a block device, it doesnt care whether its a fileset of naked pictures or a root linux...
-
UdoB reacted to hetmansoftware's post in the thread Proxmox Storage Recovery Challenge: Help Us Design a Realistic Data Loss Experiment with Like.
Thank you for the suggestions! Unfortunately, I don’t have enough hardware available to build and test a Proxmox cluster, so I’ll focus on a single-node setup for this experiment. However, the idea of virtualizing the environment and using...
-
Ddeadseth posted the thread Kernel 7.0.14-23 boot failure: ata5 host bus error, ZFS key rejected on Haswell (i7-4790K) in Proxmox VE: Installation and configuration.Hello, After booting into the recent Proxmox kernel 7.0.14-23-pve, my system encounters critical hardware and storage errors during startup, forcing it into an unstable state. Reverting to kernel 6.8.12-43-pve completely resolves the issue...
-
WSince the installation failed on a different package each time but eventually succeeded, it may indicate an intermittent hardware issue rather than a corrupted ISO file...
-
Aalexskysilk replied to the thread Proxmox Storage Recovery Challenge: Help Us Design a Realistic Data Loss Experiment.I think you're going about this the wrong way. the payload of virtualization or standalong filesystem are not materially different. when I fire up testdisk on a block device, it doesnt care whether its a fileset of naked pictures or a root linux...