Proxmox 6.1-3 iSCSI issue

ExtolCorp

New Member
Jan 28, 2020
8
0
1
Malaysia
www.extolcorp.com
Hello everyone,

Not able to communicate with HP MSA 2040 SAN device. This is the error i am receiving while trying to start VM's manually. Please help.

Code:
Starting VM 100

Starting VM 100 failed: can't activate LV '/dev/vmdata0/vm-100-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 101

Starting VM 101 failed: can't activate LV '/dev/vmdata2/vm-101-disk-0': Cannot activate LVs in VG vmdata2 while PVs appear on duplicate devices.

Starting VM 103

Starting VM 103 failed: can't activate LV '/dev/vmdata0/vm-103-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 105

Starting VM 105 failed: can't activate LV '/dev/vmdata0/vm-105-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 106

Starting VM 106 failed: can't activate LV '/dev/vmdata0/vm-106-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 107

Starting VM 107 failed: can't activate LV '/dev/vmdata0/vm-107-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 108

Starting VM 108 failed: can't activate LV '/dev/vmdata0/vm-108-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 109

Starting VM 109 failed: can't activate LV '/dev/vmdata0/vm-109-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 200

Starting VM 200 failed: can't activate LV '/dev/vmdata0/vm-200-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 210

Starting VM 210 failed: can't activate LV '/dev/vmdata0/vm-210-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 300

Starting VM 300 failed: can't activate LV '/dev/vmdata0/vm-300-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 302

Starting VM 302 failed: can't activate LV '/dev/vmdata0/vm-302-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Starting VM 303

Starting VM 303 failed: can't activate LV '/dev/vmdata0/vm-303-disk-0': Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

TASK OK

As an addition, this error occured right after a sudden power failure over the weekend.

Code:
Jan 28 14:18:20 megan pvedaemon[12364]: start VM 100: UPID:megan:0000304C:0006582B:5E2FD22C:qmstart:100:root@pam:

Jan 28 14:18:20 megan pvedaemon[1410]: <root@pam> starting task UPID:megan:0000304C:0006582B:5E2FD22C:qmstart:100:root@pam:

Jan 28 14:18:20 megan pvedaemon[12364]: can't activate LV '/dev/vmdata0/vm-100-disk-0':   Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.

Jan 28 14:18:20 megan pvedaemon[1410]: <root@pam> end task UPID:megan:0000304C:0006582B:5E2FD22C:qmstart:100:root@pam: can't activate LV '/dev/vmdata0/vm-100-disk-0':   Cannot activate LVs in VG vmdata0 while PVs appear on duplicate devices.
 

Attachments

  • pvscan.png
    pvscan.png
    24.2 KB · Views: 16
  • vgdisplay-1.png
    vgdisplay-1.png
    39 KB · Views: 17
  • vgdisplay-2.png
    vgdisplay-2.png
    17.2 KB · Views: 15
  • targetcli-ls.png
    targetcli-ls.png
    15.7 KB · Views: 9
  • discovery.png
    discovery.png
    32.7 KB · Views: 9
Last edited:
Hi,

as your iscsiadm show, your network is reset from the server-side.
Network problems maybe.
 
Thank you. I am able to ping out and ping in to my Proxmox host machine. I am also able to ping the SAN server IP as well as the both controllers in SAN. I doubt this is network issue. Strangely i am able to start VM placed in Controller A, but not in Controller B.
 

Attachments

  • Proxmox-Network-Config.png
    Proxmox-Network-Config.png
    36.6 KB · Views: 9
  • Proxmox-Error.png
    Proxmox-Error.png
    10.3 KB · Views: 9
  • SAN-Storage-Ping-Result.png
    SAN-Storage-Ping-Result.png
    17.4 KB · Views: 6
  • SAN-Controller-A-Ping-Result.png
    SAN-Controller-A-Ping-Result.png
    17.2 KB · Views: 6
  • SAN-Controller-B-Ping-Result.png
    SAN-Controller-B-Ping-Result.png
    17.1 KB · Views: 6
  • Remote-iSCSI-Portal-Scan-Result.png
    Remote-iSCSI-Portal-Scan-Result.png
    8.3 KB · Views: 4
Ok then the client has zombies.
Try to reboot the node.
 
Perhaps it would be very helpful if you could point me to links/notes that will guide me in starting fresh setup, The existing configuration was done by a former colleague, he has left the organisation with no notes/documentation left behind.

Current setup;
1. Proxmox running on Dell PowerEdge R710
2. HP MSA SAN 2040 with 2 Controllers (A,B)