Search results

i think i found something that cause it, hope you can recreate it: i just run manual back on lxc container (Ubuntu 18.04 ) with multiple nfs mount points, but one of the nfs mounts is unavailing (down) once the backup failed with the following error: INFO: excluding bind mount point mp7...

Nope, i guess i missed it, I thought this relatively basic and that that is already implemented.. * we did not change the ID or the name Ill probably wait for a beta of PBS to end..

We usually got for enterprise refurbished hardware (dell\supermicro 1-5 years) and used (but relatively new sas ssds 1-2 years old)) I guess our top budget for this is 1500$ (including storage) We dont need high (around 5-10TB redundant , with some scale options in the future) The question if...

this is for our work,currently all our CT's are ceph based (3 replication), it should be solid enough, but a bug in the ceph core can cause a issue that is beyond my capabilities to fix. so i am looking for something to feel safe ( another backup off site will be added later) what are the best...

Does the PBS require same storage as the normal proxmox servers? Currently have mainly lsi cards in IT mode. Will it work the pbs? Any suggestions on minimal requirements?, all i could find is 8GB ram, and high grade boot drive

i have a scheduled backup. on a nfs VZDUMP backup file that configured for 2 backups. the script files withe the following reason :ERROR: Backup of VM 112 failed - There is a max backup limit of (2) enforced by the target storage or the vzdump parameters. Either increase the limit or delete...

only solution i found so far is to delete the binds (nfs mount) clone and then remake them any other solutions ? example for bind that fails: mp3: /mnt/pve/docs,mp=/mnt/docs,backup=0,shared=1,replicate=0

i gave up. ill find another use for this server. thanks everyone

the first step i took is to upgrade all hardware, ipmi, bios .... yes same error on 6.2. running upgrade and dist-upgrade now

i just tried to install an older version image (6.1 instead 6.2) and this is the erros i found on of `journalctl -b' ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size efifb: abort, cannot remap video memory 0x1e0000 @ 0x0 efi-framebuffer: probe of efi-framebuffer.0 failed...

did you solve it ? i have similar issue at post-336153

i remved the "quiet" and press ctrl+x but i did not see any messages on the screen. i am able to ssh to the machine (under root) and print out the syslog: here is the end of if Sep 7 14:06:22 pve-srv6 systemd[1]: Startup finished in 8.236s (kernel) + 7.310s (userspace) = 15.547s. Sep 7...

after disabling all virtual devices (ipmi) it no longer look for sdb, but again a fresh install still heaving issues. i think there might be a bad ram module (running full diagnostic now )

Aa i remember on older version before we upgraded (i think it was v4 or v5) we had it hard-coded, Can i assume now 50%?

i looked for this file, but i can only change the vote size for each node there, i am looking to change the minimal total vote needed to achieve quorum. we added few more servers, i want to update the change the weight on some of them

did you hear about proxmox-backup-server (keep in mind it is still in beta) i am planing to use it once it get abit more stable

i made a fresh install on raid1(2*200 ssds) and after install stage i have the following hang screen: Loading Linux 5.4.34-1-pve ... Loading initial ramdisk ... tried to upgdate-grub and received the output : Generating grub configuration file ... /dev/sdb: open failed: No medium found...

yes a working cluster of 10 nodes, i gave some certification on the question on the first post, (change subnet mask)

is it safe to change (extend) the subnet mask for active proxmox servers ? is there any precautions i should take ?

i want to add few more servers, how i can change the voting of each server? how i can change the minimal quorum value ?