Search results

Yeah, it seems that there is some incompatibility between ZFS and VirtIO Block devices

Yeah, already did it :-) all good. The issue disappeared! Many thanks. Bear in mind, Windows will go BSOD when doing such change. Or at least mine did it ;-) Luckily I don't have any production Windows OSs.

Actually I was wrong, because it uses UUID, the UUID remains the same, no matter you are using SCSI or VirtIO. Will change it and check if the errors still appear. Many thanks!

But this will change how the disk are recognized by the OS, which means - unable to boot the OS

I'm not sure what you are talking about, You want me to switch to Virtio Single or?

So maybe the last test we can do is to simulate many small writes, just to check if it will appear or not. Because by far as mentioned above, the issue comes up only when trying to store/write big piece of data.

This morning I tried to limit the network and disk speed to 1MB/ps, the problem still persist. From my point of view it is not about heavy load, but the amount of data being written to the disk. As you see, the gitlab installation is one huge package, which contain all the things related to...

On my side only Ubuntu VM's are affected, but I think this is shoot in the dark. How this can be related to distribution of the OS.. Here are the details about my hypervisor: root@proxmox-node-1.home.lan:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-6...

I have the same issue only for 1 VM, at least I have tried setting up native with no cache, but this makes the things even worst - the VM completely freezes. Other ideas how to resolve the issue? Thanks in advance.

No, one 1 interface in place. root@proxmox-node-1.home.lan:~# cat /etc/pve/lxc/121.conf #SERV%3A DNS, PIHOLE, LLDP, SNMP, LIGHTHTTP, POSTFIX, NRPE, PUPPET #IP%3A 192.168.10.5 #VLAN%3A 310 #PAT%3A NONE arch: amd64 cores: 2 hostname: pihole.home.lan memory: 768 nameserver: 192.168.0.7...

No one one this one? Do I made something bad from configuration perspective?

Hello guys, I'm working on an playbook (Ansible) intended to perform so called "unattended upgrades" of the whole environment. Because the playbook includes actions like setting up scheduled downtime in Nagios, rebooting the server and wait till it came up again online I created a logic, all of...

Sure, nothing special from my point of view. Here it is: A brief explanation: I have 3 physical interfaces, eth0 is set as trunk port which allow all VLAN's except vlan 35 which is set as native (because I have shared this between the OS and management), eth1 and eth0 allow all VLANs and are...

No one on this? If I did it wrong, blame me, I just want to fix it.

Hello, I know this topic is already discussed thousens times here in the forum, but it seems that my issue is somehow different.. The moment I activate a firewall interface for any of my guests I start receiving so called "alarms" like this one: Oct 01 10:19:26 proxmox-node-1.home.lan kernel...

Thanks for the replay @Dunuin. I already have backup of all the content on the filesystem of both of my PVE hosts, so the file level backup is fine. But I'm a bit worried about the block level backup. My servers use software RAID, and last time I tried to backup with CloneZilla I faced not...

Hello guys, I'm trying to replace my backup solution with Proxmox backup client, it seems that I will be able to achieve good automation by deploying and configuring the client on all VM's, containers and hosts. Back up or restore a Container or VM seems to be straight forward task, but what...

It's done. Thanks a lot @Stefan_R

Yeah, I want to mark it as solved, but to be honest, I'm not sure how to do it? :oops:

Thanks a lot for your explanation @Stefan_R, will continue to watch the behavior of the system, and if it freezes again, will setup kdump as you said. Do I have to close the thread? Or this doesn't matter for you?