Search results

i know, but we have daily backups and check backup status, normal storage and controller show us if a hdd was dead for changing. regards

ok thanks, well comes 1st with a last proxmox update...

you have only 1 socket, can also use only 1 socket with max 20 cores

hi what tell me this error message? i have installed 80 x Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz (4 Sockets), all vms have ion conf max 4 socket as config. regards

sorry i cant check all disc seperatly many vms run here, not available it. i have create new qcow2 with command of @fiona and rename org to old and new to org name, than vm start. backup i test yet. regards

Info, after fsck and reboot error are the same. i do test quemu-img convert yet in offline vm mode. same error kernel:critical medium error, dev sdb, sector how can i found which hdd numbner in storage it is?

i have make check raid system of storage (fsck -f -c -y /dev/sdb) after umount all /dev/sdb... /dev/sdb: ***** DATEISYSTEM WURDE VERÄNDERT ***** /dev/sdb: 134/488308736 Dateien (0.7% nicht zusammenhängend), 4661011542/7812939776 Blöcke it was repaired, i start system complete new and than i...

with megacli command in cli i have check all hdds and her status => megacli -PDList -a0

@fiona can you post complete command for qemu-img convert --salvage please and tell what do this? regards dd if=/var/lib/vz/images/5134/vm-5134-disk-0.qcow2 of=/dev/null bs=1M dd: Fehler beim Lesen von '/var/lib/vz/images/5134/vm-5134-disk-0.qcow2': Eingabe-/Ausgabefehler 57905+1 Datensätze ein...

hi this node havae raid 1 as system hdd for proxmox, a lsi raid controller for 32tb storage over sas 12g. this raid 60 storage is mounted as vz dir in server for all vms. as backup we use PBS. regards

/dev/sdb 29T 19T 9,4T 67% /var/lib/vz i must hold on all vms, than i can start fsck, well is storage raid 60, hdds in storage are all ok, it must be also a filesystem error, hope fsck can solve it. i do make tonight.

hi we have a 40 tb storage, all other vms run normal here. only this have the problem, how can we fix it @fiona? regards ps: i have checlk with megacli all hdds, no smart error or other erors are listed on hdds in storage

hi, yes everytime on 19% log PBS: Okt 19 22:07:37 backup-srv proxmox-backup-proxy[659]: TASK ERROR: removing backup snapshot "/mnt/backup/vm/5134/2025-10-19T20:07:27Z" failed - Directory not empty (os error 39) log PVE node: Okt 19 22:07:37 prometheus kernel: sd 2:2:0:0: [sdb] tag#712 BRCM...

hi we have since view days following error on backup. what can we do here to fix it? all other backups run normal. regards

i have change owner in gui on all backups.

Hi all, what tell this error? I have add a admin as admin role in pbs and same admin@pbs in promxmox storage entry, but i have following error on backups: VM 4444 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (admin@pbs != root@pam) Someone a idea...

ok have found solutions to bring all nodes with all vms in running mode without any problems to new cluster. with infos about on top but step by step with clean configs

@Fabxienx and all others... i must reinstall a cluster well ssd was dead, i have backup of /etc/pve i have also isntalled a new cluster on old cluster server with new hdd with same ip and name i would add old nodes to new cluster but at moment i dont find a solution thats works fine i have test...

I know, but i jave Backup of /etc/pve but i cant add nodes to cluster, look error message on top^^ i cant also add at moment notes to new cluster. if files are overwrite is no rpobpem i have backups but i cant add notes. normal i can add notes / rejoin it and can insert backup conf and it...

backup time is than many weeks for all vms, thats not a good idea. why i cant add a node to a new cluster with same ip and same name? is same server only new hdd with new isntalled cluster.... ? can i restore files to readd nodes with vms? i have clusters /etc/pve dir as backup.?