FYI. This solution still works, as I had a kernal panic issue that prevented boot. I ran the process from a USB boot of Linux Mint and my Proxmox is Linux pve 7.0.0-3-pve. Debian Trixie 13.4.
if you are using PVE >= 9.0 you can try the new "snapshot-as-volume-chain" feature ..... it should perform better on snapshot creation/deletion then internal qcow2 snapshots .... caveat: still technology preview .... qcow2 on ZFS (CoW...
Nur weil die NEU ist, muss man einen Defekt nicht ausschließen.
Smart meldet ja einen FAILED - Ersatz vorhanden?
Ich würde mich mit dem Gedanken mal anfreunden, das Ding zu tauschen.
Kannst aber auch mal schauen, ob es ein Firmware Update für...
Also ich sehe das nun so, dass Du deine Daten nebst LVM SnapShot auch bereinigen müsstest.
INFO: create storage snapshot 'vzdump'
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set...
By using ZFS over iSCSI, you can create and restore snapshots via the API without directly accessing Truenas, and thin provisioning is also available.
I recommend looking into it and testing to see if it behaves as you expect.
Great work moving s3 across the finish line. Now the next (really important) step there is immutability. So far I'm holding out for that to get done rather than start using Veeam for our Proxmox systems but that's literally the level of tradeoff...
> Having a thin provisioning would be great, expecially for the 4TB disks (because i'm sure that 4TB is just a "max recomended sizing" that the "app vendor" wrote in some document for his application sizing)
What's provisioned on storage are...
There are quite some pitfalls to using OpnSense under Proxmox, see this.
IDK if you passed your NICs through or used virtio drivers from what you wrote, also, bridging should be handled in OpnSense and it is a topic on itself (see OpnSense docs...
After the latest Kernel-Upgrade PSA-2026-00019-2: "DirtyFrag" Local Privilege Escalation on some nodes LXC containers don't start. The reason is, that /run/pve is missing. After creating /run/pve manually the container do start just fine.
I wanted to show the steps that I took to accomplish this task.
I am a real beginner to Proxmox, and I struggled with the idea of changing the disk partitions using a live disk and GParted, etc.
So, I looked for an easier method for me to do...
The errors are about repo fetched, the Nic is completely down. I tried to connect USB ethernet adapter but the system kills the connection instantly. It's marked "down".... No way
Follow this guide, step by step to split the 140T into 7 virtual GPUs. You can then pass-through one of the virtual GPUs to a VM. Remaining vGPUs can be assigned to other VMs. I have 140T on my Proxmox 9.1 host and have followed that guide a few...
I can confirm, this did the magic:
# systemctl edit container-getty@.service
fill in:
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin root --noclear --keep-baud tty%I 115200,38400,9600 $TERM
Save & reboot. Tested with Debian.