Recent content by danypd69

Ok thanks for the reply, I will try as soon as I get the nas.

I am waiting for my supplier to deliver a UC3200 that will be connected to a cluster of 3 nodes. Were you able to solve the problem?

Hello, I get the timeout message and I have installed proxmox-backup-file-restore version 2.0.7-1. After clicking OK in the dialog the list of files was loaded correctly. Here is my pveversion output proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve) pve-manager: 7.0-10 (running version...

I get the same errors, it worked well until I tried to add a fourth node to a working cluster. All the nodes are fully updated, i ran apt-get dist-upgrade before joining them to the cluster. The pvecm add ip hung after "creating certificates" and from there everything broke. I cannot migrate vm...

try to add this to multipath.conf blacklist_exceptions { property "(ID_WWN|SCSI_IDENT_.*|ID_SERIAL)" wwid .... } it worked for me. I found it here: https://elkano.org/blog/set-up-multipath-iscsi-targets-on-debian/

I have the same problem, did you manage to fix it ?

Ok I solved it using block_job_cancel drive-virtio3 in the monitor window .

Hello, I interrupted a storage migration by mistake and now I cannot do the migration anymore. the qm move_disk command gives this error storage migration failed: VM 300 qmp command 'drive-mirror' failed - Device 'drive-virtio3' is busy: block device is in use by block job: mirror Is there...

Hello rbg, did you solve this problem? I have a similar problem (conn error) and I cannot find the reason for it.

Thanks I will try with VLANs.

I alredy found that link but the interfaces are not teamed nor bonded. As I stated in a previous message the problem is present also when I simply enable the nics without activating iscsi.

It's not related to the iscsi service. I have disabled iscsi on nas4free, rebooted the server and done a ping on each ip address from the proxmox host. Result arp: 192.168.200.30 moved from 00:15:17:63:56:4e to 00:15:17:63:56:4f on em0 arp: 192.168.201.30 moved from 00:15:17:63:56:4f to...

Yes, it works very well; I have done lot of tests.

I am already using it, the multipath is configured and working ok, the only problem is the message in the nas4free console; I don't know if it is a real problem that can cause errors in future. root@px2950-01:/home/daniele# multipath -ll 3300000003f4b6f41 dm-3 FreeBSD,iSCSI DISK size=3.6T...