Search results

I'm testing the behavior of BTRFS in case of disk failure. As a first test, I disconnect one of the two disks in "RAID 1". I get errors whether it's boot disks or not, but the errors are different. In case of boot disk I have this screen: Otherwise I have: How can I fix? Ask if you need...

Ok, I enable the the no-subscription repository with the WeGUI, run tis comand: apt update apt install pve-edk2-firmware Then disable the no-subscription repository with the WeGUI. Thank you

I'm trying the latest stable version of proxmox. proxmox-ve: 7.4-1 (running kernel: 5.15.102-1-pve) pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) pve-kernel-5.15: 7.3-3 pve-kernel-5.15.102-1-pve: 5.15.102-1 ceph-fuse: 15.2.17-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client...

I managed to connect proxmox to influxdb2 (and to create graphs in grafana), the question was not about that. In the past information there is a lot of information missing, such as those deriving from devices such as GPUs for example, but also the various temperatures of the server or more...

It is possible to change monitoring configurations with influxDB in proxmox? Things like decreasing the time frame of the measurements, adding devices like GPU, etc...

I had the same problem, what caused it was a cable, used for ceph and as a secondary interconnect between two nodes. Once the connection was re-established it was possible to enter a WebGUI.

Ok, it seems to work. The PGs, during maintenance, stay degraded but the virtual machines are responsive.

Thank you for the extended explanation. How?

Given the problem described above I moved on to: osd_pool_default_min_size = 1 AND osd_pool_default_size = 2 I know it's not ideal but now I don't think I can do otherwise. Tonight I will try to shut down a server, as I will need to add a graphics card. I have a question, could the fact that I...

Now i have this message: Degraded data redundancy: 189517/12115939 objects degraded (1.564%), 6 pgs degraded, 6 pgs undersized pg 2.d is stuck undersized for 13h, current state active+undersized+degraded+remapped+backfill_toofull, last acting [1,3] pg 2.2f is stuck undersized for 13h, current...

I just set osd_pool_default_size = 3 through the webgui. I expected there were only remapped PGs. The reconstruction should finish in two / three hours Tomorrow I try to restart a node to confirm that the change has the desired results.

So I could set up osd_pool_default_min_size = 1 or osd_pool_default_size = 3 In the first case I would have more space and less redundancy, in the second the opposite.

I have a 4 node cluster with two disks each node. When for maintenance or upgrade of a server I have to shut down or restart a node become degraded. Initially the degraded PGs are exactly half of the total, in the image the reconstruction had started a few minutes earlier. The problem is that...

Does it work for more than 24 hours straight?

Tried, no improvement.

I'm on 5.16 and GPU passingthrough didn't give me any problems.

It seems to be talking about a problem related to virtualization nested all in the Windows environment and does not mention AMD environments. But it sure is worth a try.

I've read wrong.

You can try with the 5.15 kernel. https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/ The problem seems to be limited to nested Hyper-V on AMD environments.

So I don't think there is any hope that this will be fixed. Seems like a kernel-level problem, I'm also trying 5.16 but unsuccessful for now. The other nested virtualizations seem to be fine, I tried another proxmox and virtualbox under windows environment, no problem. The problem is that I...