Can't activate LV of VM's after iscsi server restarted. Help needed!

ytra

New Member
Dec 6, 2012
5
0
1
Hi All,

I have a Proxmox cluster consisting 8 nodes. This worked flawless for almost a year now. Unfortunately the iscsi server crashed, after the restart the VM's on the nodes showed irratic behaviour. Therefore I restarted one of these VM's which resulted in the following message:

Error: can't activate LV '/dev/DATA07/vm-102-disk-1': Skipping volume group Data07

From that point I have checked the iscsi-server where everything shows correctly. The nodes have iscsi initiators running there.
The LVM's exist en check out ok as far as I can see.

Currently I am running out of options and have 20 VM's down, any help is VERY welcome!!

Thanks in advance!
Siebe
 
what do you get with:

> pvesm list <your_storagename>
 
what do you get with:

> pvesm list <your_storagename>

It returns nothing.

pvesm status returns:

root@vmnod5:~# pvesm status
BACKUP dir 1 17288012 1045224 15364608 6.87%
LVM_SAN01 lvm 0 0 0 0 100.00%
LVM_SAN02 lvm 0 0 0 0 100.00%
SAN01 iscsi 1 0 0 0 100.00%
local dir 1 34834128 297128 34537000 1.35%
 
have you tried:

iscsiadm -m node -R

Yes, I have tried it without success.
It does rescan the iscsi connection but the LV's are not reconnected to the node and its VM's.


The problem is solved and didn't originate in the proxmox cluster. The culprit was the iscsci-server itself, the iscsi connection was setup from the commandline. Unfortunately the iscsiadm doesn't add the configuration to the targets.conf to make the configuration persistent over reboots. Strangely enough the iqn was setup persistent but the backingstore wasn't.
 
Last edited:
Yes, I have tried it without success.
It does rescan the iscsi connection but the LV's are not reconnected to the node and its VM's.


The problem is solved and didn't originate in the proxmox cluster. The culprit was the iscsci-server itself, the iscsi connection was setup from the commandline. Unfortunately the iscsiadm doesn't add the configuration to the targets.conf to make the configuration persistent over reboots. Strangely enough the iqn was setup persistent but the backingstore wasn't.

How did you make it persistent? Also, my /etc/iscsi doesn't have a targets.conf file, but the iscsi target does have it under /etc/tgt/targets.conf.