Search results

Hello. After a day or so, it was completed, freeing up: Removed garbage: 2.37 TiB Deleting old or large backups was possible. I ran the command you indicated correctly while it was running, but I don't know if it had any effect. Should I return it to 5? Thanks for the help.

It was an error when copying it here, but it doesn't apply, if I open the file with nano, it says 5 and I don't have permissions

Do you mean the following? I tried it, but I don't have permissions. I tried chmod. cat /sys/module/zfs/parameters/spa_slop_shift echo > 6 /sys/module/zfs/parameters/spa_slop_shift

lsblk -e230 -oNAME,SIZE,FSTYPE,FSVER,FSSIZE,FSUSED,FSAVAIL,FSUSE% NAME SIZE FSTYPE FSVER FSSIZE FSUSED FSAVAIL FSUSE% sda 1.8T ├─sda1 1.8T zfs_member 5000 └─sda9 8M sdb 1.8T ├─sdb1 1.8T zfs_member 5000 └─sdb9 8M sdc 1.8T ├─sdc1 1.8T zfs_member 5000 └─sdc9...

2025-05-30T12:36:08+02:00: marked 55% (197 of 357 index files) 2025-05-30T12:36:09+02:00: TASK ERROR: update atime failed for chunk/file "/mnt/datastore/Copias/.chunks/befd/befdcfb4c93666567c2ed93f572a688649bd1c143f2aedf06c1074ea0ce86952" - ENOSPC: No space left on device

Hello. The datastore I use for backups is full. I've set up a purge system, which is more restrictive so it removes more space. I've been looking at the forums and I need to run Garbage Collect, but I'm getting an error at the 2% mark, saying there's no more space. I've deleted more container...

Hello, I have recovered a snapshot from before the update and it worked for me.

Hello, It stays with the following message and does not start. Why could this be? Thanks, best regards.

Hello, I have done the solution in this post and it has worked for me https://forum.proxmox.com/threads/ubuntu-14-04-lxc-needs-to-be-started-manually-with-init-3-on-proxmox-7.106411/

Hello, Hello, I have managed to upgrade a node from 6 to 7, but some old containers start but cannot be accessed via Console. The only way to access is via PTC enter ID, where we found that it does not take IP, does not work, and therefore many services do not start. We have tried to enable old...

Perfect, it worked for me, thank you very much. I'm going to update the other node and test that all the containers are working fine.

Hello A question, is it possible to repair it and keep it in 6 as it was? I ask this because I have old containers that are giving me problems in a Proxmox v8 test, I am reviewing it.

I was getting an error saying that line 1 was duplicated with line 8 before trying to update, that's why I mentioned it. I've already configured it and I'm going to try it now with the command you've indicated, I'll let you know. Thanks.

Hi, From terminal, following this manual https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Testing_the_Upgrade I used: apt update apt dist-upgrade

Hello. We have gone to update a node of the Cluster, it has two, but after carrying out the process it has given the following error: This node appears with the following error and we cannot start the containers, although we can access it via SSH or terminal from the other node. pveversion -v

Hi, Can you help me? Please.

Hi. I have a cluster with two nodes but when I try to add a third node, to later upgrade Proxmox 6 to 7, I get this error listed here: tls_process_server_certificate: certificate verify failed (596) I have tried several solutions found on the forum but they have not worked for me. Can you help...

Hi. I have a cluster with two nodes but when I try to add a third node, to later upgrade Proxmox 6 to 7, I get this error listed here: tls_process_server_certificate: certificate verify failed (596) I have tried this solution without success. Can you help me?

Thank you, I managed to replace the system hard drive with the guide you sent me. Best regards