Recent content by Grigory

It started some time ago, can't tell precisely. Maybe after adding iSCSI target on freenas. By the way I have 2 nodes: one of them working with this iSCSI target and giving errors, second is configured to work with this target, but do not have any partitions of vm's stored on it, and giving no...

Hello everybody! I've got a little problem with Proxmox 4.3 Here is my output of console. This disc is attached iSCSI storage. What should I do with this? Disk /dev/sdg: 21.8 TiB, 24001350991872 bytes, 46877638656 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical)...

Thanx again. Will try to create cluster in first days of january, when server C and another disk shelf arrives. Will have to stop entire system, both iSCSI disk shelf and server and VMs, and add another 10g switch to stack an so on. Happy working holidays there will be.

Thanks for care :). Do You really sure that I should first add iSCSI targets and then create cluster. I'm confused with fact that STORAGE settings is for whole datacenter. So, I'm not really sure how cluster will work with this in case if iSCSI with same names will be created.

The question is abought the order of actions, not the servers quantity. There will be four servers at all.

Hello! I have 2 servers A and B. Server A is configured PV 4.2 host with ~20 VM running with vm-disks on configured iSCSI storage(DELL MD3800i). Server B is clean installation with no iSCSI targets. Next I'm going to create cluster. Should I 1. First add iSCSI targets on server B and then...

A couple of advices: 1. Use separate networks interfaces for iSCSI and VM traffic, put them in different vlans on switch for example. 2. Set switch ports mtu 1500 for vm and 9000 for iSCSI if possible.

Do U use broadcom NIC? I've got this problem on Broadcom GbE 4P 5720-t rNDC. Worked fine in 3.4-10 version of proxmox. The other machine with intel NIC works fine with 4.2.

Got the same after upgrading from 3.x to 4.2. Try to ping something - may help, or may not.

Got the same situation. Appeared after upgrading from 3.x to 4.2. Network interface is active for some time and dies/falls asleep after short period. Tried to do clean install on the server - got the same effect. Server is dell poweredge720, 4xGbE built-in adapter. Updated adapter and bios...

Try to restart pveproxy and pvedaemon services.

Hello, comrades! I'm experiencing a little problem with moving large disk images from old servers. So, what we have: 1. Proxmox 4.2-15/6669ad2c installed and configured. 2. Dell PowerVault 3200i attached via iSCSI. 3. Old server with 2x1Tb drives. When i moved my less "massive" servers to VM I...