Switching to "host" as the CPU did not solve the problem unfortunately. As noted, the x86-64-v2-AES host is not available in the list of CPUs. I wonder if that was ever available in Proxmox 7 or I need to bite the bullet and upgrade my Proxmox...
Then don't, this is a good thing imho.
Yes, we are all part of a big conspiration to gatekeep this forum from ai-generated messages and newbies.
Please do!
We know this already from this other thread of yours:
Since then I didn't bother...
Dieser Pfad existiert innerhab des Containers, darauf werden die Volumes wie data, pgdata etc gemapped und innerhalb des Containers gemounted:
https://www.ionos.com/digitalguide/server/know-how/docker-container-volumes/...
Pretty sure that CPU is unsupported in Windows. Try x86-64-v2-AES or v3. Host should also work unless it’s really old but there are issues with the nested virtualization/security and idle cpu usage if you search the forum.
In most cases it should be sufficient to install the Proxmox packages which also includes an kernel with ZFS support. According to the ops linked manual chapter "apt install proxmox-backup-server" should do the trick. The image provided by the...
It looks like the ZFS snapshot command timed out on ernie.
Could you check whether I/O delay increased around that time, or whether any I/O-intensive tasks, such as a ZFS scrub or backup, were running?
Since I cannot check the system’s state at...
Then don't, this is a good thing imho.
Yes, we are all part of a big conspiration to gatekeep this forum from ai-generated messages and newbies.
Please do!
We know this already from this other thread of yours:
Since then I didn't bother...
This thread has run its course, so I’m locking it. For future postings: Please follow the rules you agreed on when signing up here, and stay civil and keep discussions on topic. This is the Proxmox Community Forum, not a source code forge - yes...
ich habe gerade gemerkt, dass es weder beim Nutzer root noch beim Nutzer paperless den Pfad /usr/src/paperless gibt. Wir ihr oben seht wird der aber anscheinend local verwendet. Kann es etwas damit zu tun haben?
Wenn du den Marvell als Einsteckkarte besitzt, oder ihn auf deinem Mainboard deaktivieren und durch eine externe Karte ersetzen kannst, wird das vermutlich die einfachste Lösung sein.
Das Letzte Mal, als ich von (=über) Marvell SATA Controllern...
Sometimes it's simply best to avoid further efforts and just accept, that not every problem can be solved (with any kind of acceptable effort).
Your choice for a replacement board was probably not the worst. So have fun with it and hopefully this...
I agree with your your points but for me this also is reason why I think that the community scripts and the youtubers clickbait are actually doing more harm than good, greybearded gatekeeper I am.
Then don't, this is a good thing imho.
Yes, we are all part of a big conspiration to gatekeep this forum from ai-generated messages and newbies.
Please do!
We know this already from this other thread of yours:
Since then I didn't bother...
True. But since the forum isn't primarily about hosting scripts, and there's a perfectly viable workaround in the form of uploading a file, I don't see an issue with that.
And for regular posts, having a limit is definitely a good thing...
True. But since the forum isn't primarily about hosting scripts, and there's a perfectly viable workaround in the form of uploading a file, I don't see an issue with that.
And for regular posts, having a limit is definitely a good thing...
Nobody cares. You come here to bitch that the software you got for free isn't good enough but you'll deign to fix it if we just allow gigantic unreadable AI slop in the forum. Boo-hoo, you insufferable jerk.
As long as you have only enlarged the partition, no harm has been done. LVM would require a separate pvresize command to make use of the additional space. However, I strongly suspect that you haven't actually changed anything.
By default...
OK, so I came up with this brief patch against PVE/QemuServer/Cloudinit.pm:
diff --git a/src/PVE/QemuServer/Cloudinit.pm b/src/PVE/QemuServer/Cloudinit.pm
index c1311da8..b3d2e9e2 100644
--- a/src/PVE/QemuServer/Cloudinit.pm
+++...
I was doing this pretty early before i had all my coffees...im concerned about potential issues down the road
im not sure about how proxmox uses the free space
also i only ran cfdisk but did not run resize2fs
# lsblk /dev/sda; lsblk -f /dev/sda...