I have a cluster of two Proxmox, one of them I had to remove from the cluster. Then, I formatted it, readded to the cluster, and I have some problems (typical problems :) ) regarding visibility between them. No mind, I know that Proxmox clusters are very "delicate" :)
My question is...
Same problem here, instead of iSCSI i have a LSILogic SAS controller (SAS1064ET).
Obviously disks are fine, RAID is OK... and latest Proxmox 4.2 with 4.4.40-1-pve.
Any news from this?
[1038862.772719] blk_update_request: I/O error, dev sda, sector 14050080
[1038862.778778] sd 4:1:0:0...
Thanks for your answer.
I was thinking of I/O congestion too.... but I have other servers (some older) and I've never seen I/O problems while transferring VM into them.
This is a brand new Intel S2600WT2R with a LSI Logic / Symbios Logic MegaRAID SAS 2208 [Thunderbolt] (Intel...
Yes, /var/lib/vz it is present but inside root partition. I usually set maxroot to 10Gb... so now /var/lib/vz is 10Gb shared with system :)
I'd like that Proxmox during install let the user choose whether use local-lvm or leave an entire partition to /var/lib/vz as before :)
After deploying a new server with latest version (4.2) I've noticed that /var/lib/vz does'nt exists anymore.
Instead, it uses LVM as RAW storage for VMs.... (It created local-lvm datastore).
This is new in 4.2?
Is it better than qcow2 files into /var/lib/vz as used to be before as the...