LVM on iscsi

N

niller

New Member
Apr 5, 2020
5
2
1
50
Hi all,
I have been testing out Proxmox on our lab setup which is 3 older Dell machines all equipped with 4 NICs and a Dell MD3200i iscsi SAN. For now I am only working on one machine.
The modules and configuration is done according to the iscsi multipath documentation.
Proxmox can see the san and multipath -ll shows:

# multipath -ll
mpatha (36782bcb00030f9e2000051735e6433ee) dm-5 DELL,MD32xxi
size=11T features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 rdac' wp=rw
|-+- policy='round-robin 0' prio=14 status=active
| |- 8:0:0:0 sdb 8:16 active ready running
| |- 7:0:0:0 sdd 8:48 active ready running
| `- 10:0:0:0 sdc 8:32 active ready running
`-+- policy='round-robin 0' prio=9 status=enabled
|- 9:0:0:0 sdf 8:80 active ready running
`- 6:0:0:0 sde 8:64 active ready running

It seems like the device is also presented to Proxmox

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi
└─sda3 8:3 0 223.1G 0 part
├─pve-swap 253:0 0 7G 0 lvm [SWAP]
├─pve-root 253:1 0 55.8G 0 lvm /
├─pve-data_tmeta 253:2 0 1.5G 0 lvm
│ └─pve-data 253:4 0 141.4G 0 lvm
└─pve-data_tdata 253:3 0 141.4G 0 lvm
└─pve-data 253:4 0 141.4G 0 lvm
sdb 8:16 0 10.9T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 10.9T 0 part
└─mpatha 253:5 0 10.9T 0 mpath
├─mpatha-part1 253:6 0 1M 0 part
└─mpatha-part2 253:7 0 10.9T 0 part
sdc 8:32 0 10.9T 0 disk
├─sdc1 8:33 0 1M 0 part
├─sdc2 8:34 0 10.9T 0 part
└─mpatha 253:5 0 10.9T 0 mpath
├─mpatha-part1 253:6 0 1M 0 part
└─mpatha-part2 253:7 0 10.9T 0 part
sdd 8:48 0 10.9T 0 disk
├─sdd1 8:49 0 1M 0 part
├─sdd2 8:50 0 10.9T 0 part
└─mpatha 253:5 0 10.9T 0 mpath
├─mpatha-part1 253:6 0 1M 0 part
└─mpatha-part2 253:7 0 10.9T 0 part
sde 8:64 0 10.9T 0 disk
├─sde1 8:65 0 1M 0 part
├─sde2 8:66 0 10.9T 0 part
└─mpatha 253:5 0 10.9T 0 mpath
├─mpatha-part1 253:6 0 1M 0 part
└─mpatha-part2 253:7 0 10.9T 0 part
sdf 8:80 0 10.9T 0 disk
├─sdf1 8:81 0 1M 0 part
├─sdf2 8:82 0 10.9T 0 part
└─mpatha 253:5 0 10.9T 0 mpath
├─mpatha-part1 253:6 0 1M 0 part
└─mpatha-part2 253:7 0 10.9T 0 part
sr0 11:0 1 1024M 0 rom

However when I try to create a LVM on top of the iscsi the 'Base volume' field is empty (See screenshot 22), like no LUN is available. Also looking at the iscsi storage under 'content' it just appear empty (See screenshot 21).

If you need more information, please do not hesitate to ask.

Thanks for your time,

Thomas
 

Attachments

  • Screenshot (21).png
    Screenshot (21).png
    64.1 KB · Views: 205
  • Screenshot (22).png
    Screenshot (22).png
    96 KB · Views: 213
  • Like
Reactions: aasami
Hi,
I'd also guess that you ran into this bug. As a workaround you can check the Use LUNs directly checkbox, then the LUNs should show up. Just make sure not to use the LUN as a VM disk at the same time, if you configure LVM on top of it. I think you can also uncheck Use LUNs directly again, once you've added the LVM storage. Please try it out.
 
  • Like
Reactions: Noa and Moayad
Fabian_E said:
[..]I think you can also uncheck Use LUNs directly again, once you've added the LVM storage. Please try it out.
Click to expand...
This is true. As soon as you have applied a disk to a vm then the content of the storage shifts from 'none' to 'images' in which case the storage will show as available for 'images'
 
I tried adding the iscsi with the 'Use LUNs directly', however the result is the same when trying to apply the LVM on top. The 'Base volume' field is still empty.
 
Could you post the output of
Code: 
ls /sys/block/*/holders
ls -l /dev/disk/by-id

Please use Insert > Code (it's in the formatting options) or use attachments for easy readability.
 
Code: 
# ls /sys/block/*/holders

/sys/block/dm-0/holders:


/sys/block/dm-1/holders:


/sys/block/dm-2/holders:

dm-4


/sys/block/dm-3/holders:

dm-4


/sys/block/dm-4/holders:


/sys/block/dm-5/holders:

dm-6  dm-7


/sys/block/dm-6/holders:


/sys/block/dm-7/holders:


/sys/block/loop0/holders:


/sys/block/loop1/holders:


/sys/block/loop2/holders:


/sys/block/loop3/holders:


/sys/block/loop4/holders:


/sys/block/loop5/holders:


/sys/block/loop6/holders:


/sys/block/loop7/holders:


/sys/block/sda/holders:


/sys/block/sdb/holders:

dm-5


/sys/block/sdc/holders:

dm-5


/sys/block/sdd/holders:

dm-5


/sys/block/sde/holders:

dm-5


/sys/block/sdf/holders:

dm-5


/sys/block/sr0/holders:


Code: 
# ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 Apr  5 17:15 ata-TEAC_DVD-ROM_DV-28SW_10070312033712 -> ../../sr0
lrwxrwxrwx 1 root root  9 Apr  5 17:15 ata-WDC_WDS240G2G0A-00JH30_19258S458012 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 ata-WDC_WDS240G2G0A-00JH30_19258S458012-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 ata-WDC_WDS240G2G0A-00JH30_19258S458012-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 ata-WDC_WDS240G2G0A-00JH30_19258S458012-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-name-hades -> ../../dm-5
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-name-hades-part1 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-name-hades-part2 -> ../../dm-7
lrwxrwxrwx 1 root root 10 Apr  5 17:15 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Apr  5 17:15 dm-uuid-LVM-eU469vRpQ2t8mMqx20I9mfF559b1s1XdBeLT5rvfocCsPSvlr4yqok6U8d3eFGoG -> ../../dm-0
lrwxrwxrwx 1 root root 10 Apr  5 17:15 dm-uuid-LVM-eU469vRpQ2t8mMqx20I9mfF559b1s1XdBpxWCjr0uKmXO5ANiX3V5wmIa1Hx4rnZ -> ../../dm-1
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-uuid-mpath-36782bcb00030f9e2000051735e6433ee -> ../../dm-5
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-uuid-part1-mpath-36782bcb00030f9e2000051735e6433ee -> ../../dm-6
lrwxrwxrwx 1 root root 10 Apr  6 18:16 dm-uuid-part2-mpath-36782bcb00030f9e2000051735e6433ee -> ../../dm-7
lrwxrwxrwx 1 root root 10 Apr  5 17:15 lvm-pv-uuid-IXH9ik-wCyJ-TLd3-DAXs-et7Y-cHNg-MzMKzd -> ../../sda3
lrwxrwxrwx 1 root root  9 Apr  5 17:15 scsi-0ATA_WDC_WDS240G2G0A-_19258S458012 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-0ATA_WDC_WDS240G2G0A-_19258S458012-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-0ATA_WDC_WDS240G2G0A-_19258S458012-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-0ATA_WDC_WDS240G2G0A-_19258S458012-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Apr  5 17:15 scsi-1ATA_WDC_WDS240G2G0A-00JH30_19258S458012 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-1ATA_WDC_WDS240G2G0A-00JH30_19258S458012-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-1ATA_WDC_WDS240G2G0A-00JH30_19258S458012-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-1ATA_WDC_WDS240G2G0A-00JH30_19258S458012-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Apr  5 17:15 scsi-35001b444a8e5379f -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-35001b444a8e5379f-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-35001b444a8e5379f-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-35001b444a8e5379f-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Apr  5 20:02 scsi-36782bcb00030f9e2000051735e6433ee -> ../../sdf
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-36782bcb00030f9e2000051735e6433ee-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-36782bcb00030f9e2000051735e6433ee-part2 -> ../../sde2
lrwxrwxrwx 1 root root  9 Apr  5 17:15 scsi-SATA_WDC_WDS240G2G0A-_19258S458012 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SATA_WDC_WDS240G2G0A-_19258S458012-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SATA_WDC_WDS240G2G0A-_19258S458012-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SATA_WDC_WDS240G2G0A-_19258S458012-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Apr  5 19:16 scsi-SDELL_MD32xxi_14I006J -> ../../sdc
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SDELL_MD32xxi_14I006J-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SDELL_MD32xxi_14I006J-part2 -> ../../sdc2
lrwxrwxrwx 1 root root  9 Apr  5 20:02 scsi-SDELL_MD32xxi_14I006V -> ../../sdf
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SDELL_MD32xxi_14I006V-part1 -> ../../sdf1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 scsi-SDELL_MD32xxi_14I006V-part2 -> ../../sde2
lrwxrwxrwx 1 root root  9 Apr  5 17:15 wwn-0x5001b444a8e5379f -> ../../sda
lrwxrwxrwx 1 root root 10 Apr  5 17:15 wwn-0x5001b444a8e5379f-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr  5 17:15 wwn-0x5001b444a8e5379f-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr  5 17:15 wwn-0x5001b444a8e5379f-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr  6 18:16 wwn-0x6782bcb00030f9e2000051735e6433ee -> ../../dm-5
lrwxrwxrwx 1 root root 10 Apr  6 18:16 wwn-0x6782bcb00030f9e2000051735e6433ee-part1 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Apr  6 18:16 wwn-0x6782bcb00030f9e2000051735e6433ee-part2 -> ../../dm-7
 
Turns out that this is an issue in PVE that sometimes happens with multipath devices. See this bug report.

As a workaround, please try:
Code: 
pvesm add lvm hades-lvm --vgname <name of volume group> --base hades:0.0.1.dm-name-hades <additional options>
Instead of using <additional options>, you can also modify the rest of the settings for the storage afterwards (assuming the command works).
 
  • Like
Reactions: aasami
Code: 
# pvesm add lvm hades-lvm --vgname hades-vg --base hades:0.0.1.dm-name-hades
  Can't open /dev/mapper/hades exclusively.  Mounted filesystem?
create storage failed: error with cfs lock 'file-storage_cfg': pvcreate '/dev/disk/by-id/dm-name-hades' error:   Can't open /dev/mapper/hades exclusively.  Mounted filesystem?
 
I think the problem might be due to the partitions on the device. It's recommended to use the whole device for LVM. If you wish to do so, make sure there's not any data you need on the partitions, erase the partition table and eventual file system labels and run the pvesm command again.

If you really want to create LVM on top of one of the partitions, again make sure that there's not any data you need on the partition and use hades:0.0.1.dm-name-hades-part<N> instead of hades:0.0.1.dm-name-hades. But be aware that you might run into other issues later if you choose this approach.
 
Fabian_E said:
Turns out that this is an issue in PVE that sometimes happens with multipath devices. See this bug report.

As a workaround, please try:
Code: 
pvesm add lvm hades-lvm --vgname <name of volume group> --base hades:0.0.1.dm-name-hades <additional options>
Instead of using <additional options>, you can also modify the rest of the settings for the storage afterwards (assuming the command works).
Click to expand...

I had the same problem as @niller except I've tried to use the whole device without partitions.
Bash: 
[sv20@08:27 ~]# ls /sys/block/*/holders
/sys/block/dm-0/holders:

/sys/block/dm-1/holders:

/sys/block/dm-2/holders:

/sys/block/loop0/holders:

/sys/block/loop1/holders:

/sys/block/loop2/holders:

/sys/block/loop3/holders:

/sys/block/loop4/holders:

/sys/block/loop5/holders:

/sys/block/loop6/holders:

/sys/block/loop7/holders:

/sys/block/sda/holders:

/sys/block/sdb/holders:
dm-2

/sys/block/sdc/holders:
dm-2

/sys/block/sdd/holders:
dm-2

/sys/block/sde/holders:
dm-2

/sys/block/sr0/holders:
[sv20@08:28 ~]# ls -l /dev/disk/by-id
celkom 0
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-name-klaster10 -> ../../dm-2
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-uuid-LVM-uI83a6zpfTG8hYM82monkRKHbtuZLdaT5WXc1bjJE4vNezay2KKanLOIhbv77irE -> ../../dm-1
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-uuid-LVM-uI83a6zpfTG8hYM82monkRKHbtuZLdaT9ofPFv4TuCaRqX6yT0U6VAMKPCM2aUSk -> ../../dm-0
lrwxrwxrwx 1 root root 10 jún 15 14:52 dm-uuid-mpath-360002ac0000000000000001e00005aab -> ../../dm-2
lrwxrwxrwx 1 root root 10 jún 15 14:52 lvm-pv-uuid-to4jDg-wjoA-TnGt-HOMr-8KdV-uNFA-57n2Q1 -> ../../sda3
lrwxrwxrwx 1 root root  9 jún 15 14:52 scsi-SSun_R5_FBB4572A -> ../../sda
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-SSun_R5_FBB4572A-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-SSun_R5_FBB4572A-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-SSun_R5_FBB4572A-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 jún 15 14:52 scsi-S3PARdata_VV_1623211 -> ../../sde
lrwxrwxrwx 1 root root  9 jún 15 14:52 scsi-1ADAPTEC_ARRAY_FBB4572A -> ../../sda
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-1ADAPTEC_ARRAY_FBB4572A-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-1ADAPTEC_ARRAY_FBB4572A-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-1ADAPTEC_ARRAY_FBB4572A-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 jún 15 14:52 scsi-22a57b4fb00d00000 -> ../../sda
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-22a57b4fb00d00000-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-22a57b4fb00d00000-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 jún 15 14:52 scsi-22a57b4fb00d00000-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 jún 15 14:52 scsi-360002ac0000000000000001e00005aab -> ../../sde
lrwxrwxrwx 1 root root  9 jún 15 14:52 usb-TSSTcorp_CD_DVDW_TS-T632A_B0439C72162E-0:0 -> ../../sr0
lrwxrwxrwx 1 root root 10 jún 15 14:52 wwn-0x60002ac0000000000000001e00005aab -> ../../dm-2
[sv20@08:28 ~]#
The workaround suggested by @Fabian_E worked for me. Thank you.
Bash: 
[sv20@09:03 ~]# pvesm add lvm LVM3PAR --vgname vg01 --base klaster10:0.0.1.dm-name-klaster10 --shared yes --content images
  Physical volume "/dev/disk/by-id/dm-name-klaster10" successfully created.
  Volume group "vg01" successfully created
[sv20@09:03 ~]#
Shouldn't this be noted in official documentation until the problem is resolved?
It's quite tedious to scan forum for this (kind of) basic task.
 
hi ,

i have the same problem ,
but i really don't understand what u did
ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB -> ../../sda
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Dec 14 14:53 dm-name-pve-vm--100--disk--0 -> ../../dm-8
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-name-vg--san01-vm--4001--disk--0 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-name-vg--san01-vm--4003--disk--0 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-uuid-LVM-LhvmFxptMyXeutYraeobpD3AVBRa5O874xgNEqGuJBcYmsZ5533JWQtc0Nn30E87 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-uuid-LVM-LhvmFxptMyXeutYraeobpD3AVBRa5O87NaD5YjjJ8nKNx08JaMtffiAns8TmP6IK -> ../../dm-6
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfape85rvPFCxBoYs57hvlMp1HZ1gLy3OB -> ../../dm-0
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfAwz7obiEtYYHNvFHtPJKWmHO8DKj2CWV -> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 14 14:53 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfnOd4FiyVT4gWauaIku3WjpkRTkcFClJA -> ../../dm-8
lrwxrwxrwx 1 root root 10 Dec 14 11:40 lvm-pv-uuid-OBseLV-PVMU-DOo8-22gv-V2LF-RJmK-JzJQvv -> ../../sda3
lrwxrwxrwx 1 root root 9 Dec 14 14:29 lvm-pv-uuid-pE5Ue3-nXDZ-Vp6F-HXhZ-GPC4-kN7P-pNgYYy -> ../../sdb
lrwxrwxrwx 1 root root 9 Dec 14 14:29 scsi-366fc281aae9e98545ea57315a4270be6 -> ../../sdb
lrwxrwxrwx 1 root root 9 Dec 14 14:29 wwn-0x66fc281aae9e98545ea57315a4270be6 -> ../../sdb

i need to create lvm using iscsi
 
Hi,
yasmine said:
hi ,

i have the same problem ,
but i really don't understand what u did
ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB -> ../../sda
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Dec 14 11:40 ata-CT240BX500SSD1_1949E3DA63CB-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Dec 14 14:53 dm-name-pve-vm--100--disk--0 -> ../../dm-8
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-name-vg--san01-vm--4001--disk--0 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-name-vg--san01-vm--4003--disk--0 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-uuid-LVM-LhvmFxptMyXeutYraeobpD3AVBRa5O874xgNEqGuJBcYmsZ5533JWQtc0Nn30E87 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Dec 14 14:29 dm-uuid-LVM-LhvmFxptMyXeutYraeobpD3AVBRa5O87NaD5YjjJ8nKNx08JaMtffiAns8TmP6IK -> ../../dm-6
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfape85rvPFCxBoYs57hvlMp1HZ1gLy3OB -> ../../dm-0
lrwxrwxrwx 1 root root 10 Dec 14 11:40 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfAwz7obiEtYYHNvFHtPJKWmHO8DKj2CWV -> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 14 14:53 dm-uuid-LVM-QYRlaJ8B1uAjbxCIN4XTqvHhooGxajdfnOd4FiyVT4gWauaIku3WjpkRTkcFClJA -> ../../dm-8
lrwxrwxrwx 1 root root 10 Dec 14 11:40 lvm-pv-uuid-OBseLV-PVMU-DOo8-22gv-V2LF-RJmK-JzJQvv -> ../../sda3
lrwxrwxrwx 1 root root 9 Dec 14 14:29 lvm-pv-uuid-pE5Ue3-nXDZ-Vp6F-HXhZ-GPC4-kN7P-pNgYYy -> ../../sdb
lrwxrwxrwx 1 root root 9 Dec 14 14:29 scsi-366fc281aae9e98545ea57315a4270be6 -> ../../sdb
lrwxrwxrwx 1 root root 9 Dec 14 14:29 wwn-0x66fc281aae9e98545ea57315a4270be6 -> ../../sdb

i need to create lvm using iscsi
Click to expand...
the bugs referenced in this thread should've been solved since libpve-storage-perl 6.2-1 and it should be possible to configure this using the GUI again. Do you have a recent enough version installed? Is there a problem when you try adding an iSCSI storage via the GUI and then the LVM selecting the iSCSI storage as a base storage? If you're using multipath, please have a look here.
 
  • Like
Reactions: menk
Using version 6.3 and i get the following error when trying to create and LVM on my ISCSI


RESOLVED!!! Needed to setup multipart

1614793548500.png
 
Last edited:
I'm having the exact error and I cant create the LVM over iSCSI, when I try "pvesm add lvm iSCSI-LVM --vgname LVM1 --base iSCSI:0.0.1.dm-name-iSCSI --shared yes --content images" I get an error Device /dev/disk/by-id/dm-name-iSCSI not found.
 
Hi,
joako537 said:
I'm having the exact error and I cant create the LVM over iSCSI, when I try "pvesm add lvm iSCSI-LVM --vgname LVM1 --base iSCSI:0.0.1.dm-name-iSCSI --shared yes --content images" I get an error Device /dev/disk/by-id/dm-name-iSCSI not found.
Click to expand...
does it work if you use the web UI? If not, please post the output of pveversion -v, the output of ls -l /dev/disk/by-id/ and the exact error message.
 
@Fabian_E thank you for replying so quickly, all of the sudden started working when I deleted and re-added the iSCSI disk image (I did this multiple times not sure what changed) I was able to see the name under VM Disk "CH 00 ID 0 LUN 0" before it wasn't showing. Then the base module showed up in the GUI when adding LVM to the iSCSI Disk.
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back