ISCSI on Dell MD Storage

khaled.j.hussein

Active Member
Nov 29, 2017
22
1
43
46
I am installing proxmox and I have Dell MD storage, I configure new virtual disk of 1.6 TB, and I mapped this disk to my pve host, when I try to add ISCSI storage on my pve, I entered the IP and it show me the IQN of storage but I cannot choose when LUN should I add, my storage have 3 virtual disks, the other disk are connected to xen virtualization (which we are migrating them to proxmox), I cannot fine a good document for how to configure ISCSI on storage array and configure LUNs

Regards.
 
Hi menk,

I read the above thread but I am not using multipath, currently I am using Xenserver and when I add new SR it show me the IQN then the LUNS available, for proxmox I am afraid of adding the SR with wrong LUN which may cause corruption of live SR on xenserver, I want just a way how to give the ISCSI SR on proxmox the LUN number to use,

I installed new 5.2 PVE

Thanks
 
I did the following steps

- add ISCSI target from web GUI, fill name and portal, in target i see IQN available, I leave default setting as them
- try to add LVM over ISCSI, when choose base storage I added, then try to choose the Base Volume but nothing appear, base volume is empty and did not show anything

Regrads
 
when you correct add iscsi Lun (first step), then you have to create pv and vg on this lun.
Then you can add lvm.
don't check the option "use luns directly" when add iscsi lun....
 
I connect the ISCSI to my proxmox and I can see the LUN from proxmox, but when I create SR and not check "use luns directly" it check it by default and cannot uncheck it, the I tried to add LVM on top of ISCSI but I got the following error

create storage failed: error with cfs lock 'file-storage_cfg': pvcreate '/dev/disk/by-id/scsi-3600a098000ab0a2a000018795aef3030' error: Device /dev/disk/by-id/scsi-3600a098000ab0a2a000018795aef3030 not found (or ignored by filtering). (500)

when I check fdisk on node I see two disk for the same target

root@pve1:/var/log# fdisk -l
Disk /dev/sda: 418.6 GiB, 449495171072 bytes, 877920256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 93DA2F58-D346-4203-9BBB-B562F8790832
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 528383 524288 256M EFI System
/dev/sda3 528384 877920222 877391839 418.4G Linux LVM
Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sdb: 1.6 TiB, 1782658891776 bytes, 3481755648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdc: 1.6 TiB, 1782658891776 bytes, 3481755648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Thanks in advance
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!