Search results

i had the same problem, i solved with rufus and DD image mode when i created the bootable usb.

try with usb 2.0 if you can, can you post the name of your motherboard? i worked with rufus for create isos on windows, and always is fine.

Hi, i´m working with proxmox 4.1 and Hp proliants,(all is going OK but HA is not working good). so, i´m thinking to update to 4.4, i will do tests with other Hp proliants and proxmox 4.4 and backups too. but any feedback ? or any experience with proliant and proxmox 4.4? Have a nice day and...

Hi! im trying increase a Vm with Centos (Lvm partition), i run systemrescue and run gparted, and then resize2fs for this partition and it´s not working :S i did the same procedure on other centos and this worked for me. any idea? ty and sorry for my english!

thanks for reply :) and solved

Hi guys! my question is about wathdog and his trigger. If the node has connection with the cluster and has quorum, the watchdog will be reset. If quorum is lost, the node is not able to reset the watchdog. This will trigger a reboot after 60 seconds. can i set the trigger on 120 seconds, for...

Hi, you cant test ha with programmed reboot, ha is working with network problems(wire) or electrical, and you need shared storage for images of course.

you can add your third node with IP1Node Or IP2Node. (it´s the same one than other :) ) Node3:pvecm add IPNODEX im working with HA, proxmox and synology too. :D Good Luck!!

It might be interesting to you to work with clonezilla for backups, =)

You can have problem if your new node has the same name that the removed, you can work with old ip, but you must change hostname.(this worked for me) if you want work with old Ip and Old Hostname you must do the procedure :Reinstall Node cluster (i tried this and i couldn´t reinstall my node...

Hi, i saw your outputs and i see that you need the same version on both nodes for live migration, if no, you can´t.

can you test if the module hpwdt is loaded? lsmod|grep hpwdt see this for more info : https://forum.proxmox.com/threads/ve-4-0-kernel-panic-on-hp-proliant-servers.24015/

im working with proxmox 4.1 and HA and i think that it´s bad idea, if you lose physical node, you will lose all cluster, =S, the machines will have reboot and HA won´t work. and if you want HA, you will need Shared storage as NFS or SCSI. (for example)

im working with synology(RS815RP+ ) with shared folder on proxmox 4.1 and proxmox HA, Is the nfs rule set correctly on the same network as proxmox? i think that this can help you :) you should check the configuration on synology...

i solved the problem with backup but i don´t know =S

Hi, im running proxmox 4.1 and lxc containers were working good, but i installed snmpd for monitoring on containers and then when i shutdown the container, i can´t init again :S lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more...

Hi, thank you for reply, i had reinstall the system ); i tried first(reinstall the node cluster ) but the procedure doesnt work for me(), i had change the hostname and this worked for me pvecm add IPClusterProcedure:https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster .however thanks! :D

Update: If i delete network device on VM, the VM is started, with network device can´t boot. i don´t know why, yesterday, i was working good with this node and theses VMs Update2: Okay, i can´t install nothing with apt-get install,

hi, yesterday,the power went out and the system crashed, and proxmox couldn´t boot ,we did fsck -y /dev/mapper/pve-root Then, proxmox booted again, but we can´t init VM.(bios option is enabled of course) root@node1/home# qm start 114 Running as unit 114.scope. kvm: -netdev...

i think that the problem is on the nas, im working with nas, and i had the same problem, you need create a client with range ip (that you use on proxmox). on Nas. Good luck! :D