[SOLVED] Unbale to get "Base volume" to populate when iSCSI selected as "Base storage"

[bigun89]

I have a LUN configured on my SAN, and I can add the iSCSI storage without issue.

However when I attempt to configure a LVM volume on said iSCSI storage, the base volume never populates.

root@homeproxmox:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-14 (running version: 7.2-14/65898fbc)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-7
libpve-guest-common-perl: 4.2-2
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.2
pve-cluster: 7.2-3
pve-container: 4.3-4
pve-docs: 7.2-3
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.1.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-10
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1


root@homeproxmox:~# 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-6/holders:

/sys/block/dm-7/holders:

/sys/block/dm-8/holders:

/sys/block/dm-9/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:

/sys/block/sdc/holders:
dm-6  dm-8  dm-9

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

/sys/block/sr0/holders:


root@homeproxmox:~# ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 Jan 18 07:35 ata-PLDS_DVD-ROM_DU-8D5LH_C8XM57363953I6622A01 -> ../../sr0
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-name-DAS_Storage-vm--103--disk--0 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-name-DAS_Storage-vm--103--disk--1 -> ../../dm-8
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-name-DAS_Storage-vm--103--disk--2 -> ../../dm-9
lrwxrwxrwx 1 root root 10 Jan 18 07:35 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jan 18 07:35 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jan 19 21:06 dm-name-SAN_VG-vm--103--disk--2 -> ../../dm-7
lrwxrwxrwx 1 root root 10 Jan 19 21:06 dm-uuid-LVM-nGgdiX3Fdg0CqYoEuS4QY3vFhH32D2ywgBjIA1RpRndYX0pu6TwEM34bKgwB8zTv -> ../../dm-7
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-uuid-LVM-Pcyl8NiHQ2Zcwnsvof6doexGbsQg04JvGqjuoVTboV3G46wo8FNKz5a9nd5q3aBt -> ../../dm-9
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-uuid-LVM-Pcyl8NiHQ2Zcwnsvof6doexGbsQg04Jvs31iGEYXsWigPIww4BmH11cyMdYEiT1p -> ../../dm-8
lrwxrwxrwx 1 root root 10 Jan 20 12:37 dm-uuid-LVM-Pcyl8NiHQ2Zcwnsvof6doexGbsQg04JvsfhDj2m5GcrtODuBYVNj7oHgZTPuHy07 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Jan 18 07:35 dm-uuid-LVM-U1HJ9L8dWThTr7Gr5MfCPpfdnwMWQX3E8jLKYldeOYSRxaVwgRn2pdSk9Dq0JEge -> ../../dm-1
lrwxrwxrwx 1 root root 10 Jan 18 07:35 dm-uuid-LVM-U1HJ9L8dWThTr7Gr5MfCPpfdnwMWQX3ExSiDWcPsIbhubm08vp2WEbuz7HhQ0vG7 -> ../../dm-0
lrwxrwxrwx 1 root root 10 Jan 18 07:35 lvm-pv-uuid-0qJonD-h44Y-4RIx-5X0L-ofTD-HceJ-4qzm7d -> ../../sda3
lrwxrwxrwx 1 root root  9 Jan 20 15:29 lvm-pv-uuid-Lf3qf8-3WYu-a0VO-fQvC-Bu1r-NcMW-U14NhZ -> ../../sdd
lrwxrwxrwx 1 root root  9 Jan 18 17:56 lvm-pv-uuid-Se7s15-tKmR-6CJW-5naN-l7o2-6BfH-KhIHMY -> ../../sdc
lrwxrwxrwx 1 root root  9 Jan 18 17:56 scsi-200193c0000000000 -> ../../sdc
lrwxrwxrwx 1 root root  9 Jan 20 15:29 scsi-32034001378c2838a -> ../../sdd
lrwxrwxrwx 1 root root  9 Jan 18 07:35 scsi-3644a84202a8210002855032910fc88e8 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 18 07:35 scsi-3644a84202a8210002855032910fc88e8-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 18 07:35 scsi-3644a84202a8210002855032910fc88e8-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 18 07:35 scsi-3644a84202a8210002855032910fc88e8-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Jan 18 07:35 scsi-3644a84202a82100029e5936a0c057be1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 18 07:35 scsi-3644a84202a82100029e5936a0c057be1-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Jan 20 15:29 wwn-0x2034001378c2838a -> ../../sdd
lrwxrwxrwx 1 root root  9 Jan 18 07:35 wwn-0x644a84202a8210002855032910fc88e8 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 18 07:35 wwn-0x644a84202a8210002855032910fc88e8-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 18 07:35 wwn-0x644a84202a8210002855032910fc88e8-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 18 07:35 wwn-0x644a84202a8210002855032910fc88e8-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Jan 18 07:35 wwn-0x644a84202a82100029e5936a0c057be1 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 18 07:35 wwn-0x644a84202a82100029e5936a0c057be1-part1 -> ../../sdb1

 

[bigun89]

Odd, I may have found a bug, here's how I produced it.
1 - Configured a LUN with an ID of 0
2 - Setup iSCSI on Proxmox using LUN with the ID of 0
3 - Began use of LUN (put containers or VM's on it - I used it for quite some time)
4 - Setup alternate storage, and moved everything off of iSCSI to alternate storage
5 - Removed iSCSI storage, destroyed LUN, destroyed RAID on SAN, reconfigured SAN, setup on LUN 0 again
6 - Reattached iSCSI
7 - Base volume doesn't populate
8 - Destroy LUN 0, configured LUN 100 as test
9 - Base volume populates

However I'm getting an error putting an LVM volume on the iSCSI:

create storage failed: device '/dev/disk/by-id/scsi-32034001378c2838a' is already used by volume group 'SAN_VG' (500)

 

[bigun89]

Ok, I used the old volume group name (SAN_VG), now the storage I had removed previous to the reconfiguration, is now back. With the files I destroyed still listed. Some very weird things are going on.

 

[bigun89]

Ok, I think I figured out my own issue, I had to delete the volume group before I could reuse the iSCSI device. Everything seems to be working now.