creating VG on ISCSI does not find LUN

P

pille

Member
Oct 21, 2009
79
0
6
hi,

i'm following http://pve.proxmox.com/wiki/Storage_Model#Use_iSCSI_LUN_for_LVM_base
to create a shared storage, but there's no value selectable for 'Base Volume'.
nolun.jpg

the target (SAN-ISCSI-Chunk1) is available as /dev/sda on my cluster master.
any reason that the select-box is empty?

[Update:
in the storage list SAN-ISCSI-Chunk1 'used (GB)' and 'capacity (GB)' report 'n/a'.
however - capacity is listed in dmesg und the LUN an be used directly on the server.
]

pille
 
Last edited:
did you add the LVM group?
what is the output of

Code: 
# pvs

are you sure you've acess to a LUN ?

Code: 
# lsscsi
 
whinpo said:
did you add the LVM group?
Click to expand...

??? (which group? added where?)
for testing i manually added a pv to it, but it didn't changed anything

whinpo said:
what is the output of

Code: 
# pvs
Click to expand...
just my pv for the standard local pve vg.
whinpo said:
are you sure you've acess to a LUN ?
Click to expand...
yepp, i successfully copied data on it for testing (and read it, afterwards)


whinpo said:
Code: 
# lsscsi
Click to expand...
Code: 
kvm1:/mnt# lsscsi -v                                                                                                                                                                                                        
[1:0:0:0]    disk    Novell   80181e4e-d54e-df 0     /dev/sdb
  dir: /sys/bus/scsi/devices/1:0:0:0  [/sys/devices/platform/host1/session2/target1:0:0/1:0:0:0]
[2:0:0:0]    disk    Novell   00cb045d-d54e-df 0     /dev/sda
  dir: /sys/bus/scsi/devices/2:0:0:0  [/sys/devices/platform/host2/session3/target2:0:0/2:0:0:0]

target1 is SAN-ISCSI-Chunk1 in proxmox.

dietmar said:
What is the output of

# pvesm list -a

Is any lun visable?
Click to expand...

no, just my local and nfs storage
 
If nothing helps, you can try to debug /usr/share/perl5/PVE/Storage.pm, function iscsi_device_list().
 
hi dietmar,

thanks for this hint. i managed to debug the problem, but don't understand its cause.
it didn't manage to get $blockdev. up until $bdev all goes well, but in my /dev/disk/by-id my ISCSI targets don't show up.
however they do in /dev/disk/by-path, so i exchanged the function call to find_dev_by_id with find_dev_by_path.

now my ISCSI targets show up in
Code: 
kvm1:/dev/disk/by-path# pvesm list -a                                                                                                                                                                                                   
local:101/vm-101-disk-1.qcow2 101 qcow2   33554432
local:104/vm-104-disk-1.qcow2 104 qcow2    4194304
local:109/vm-109-disk-1.qcow2 109 qcow2   33554432
SAN-NFS-Disk:108/vm-108-disk-1.qcow2 108 qcow2    4194304
SAN-NFS-Disk:96/var_spool.raw        96    raw    4194304
SAN-NFS-Disk:96/vm-96-disk-1.raw     96    raw    4194304
SAN-ISCSI-Chunk1:0.0.0.ip-192.168.2.5:3260-iscsi-iqn.1984-08.com.novell:00cb045d-d54e-df11-aab5-0013d4b31141-lun-0 0   raw  230399984
SAN-ISCSI-Chunk2:0.0.0.ip-192.168.2.5:3260-iscsi-iqn.1984-08.com.novell:80181e4e-d54e-df11-aab5-0013d4b31141-lun-0 0   raw  230470640
but the dropdown-box in the web-ui is still empty.
do they share the code?

the system was installed with your bare-metal-installer 1.5-4627-3 and is up-to-date.
don't know why the devices don't show up as expected.

pille

PS: some kind of error logging instead of silently dying would be great.
 
pille said:
but the dropdown-box in the web-ui is still empty.
do they share the code?
Click to expand...

yes - maybe you need to restart apache and pvedaemon.

pille said:
the system was installed with your bare-metal-installer 1.5-4627-3 and is up-to-date.
don't know why the devices don't show up as expected.
Click to expand...

Why does udev does not add them to /dev/disk/by-id ?
 
dietmar said:
yes - maybe you need to restart apache and pvedaemon.
Click to expand...
this did the trick. but one step later i hit the udev-missing-symlink-bug in another script, so symlinking by hand would be a workaround but no solution.

dietmar said:
Why does udev does not add them to /dev/disk/by-id ?
Click to expand...

don't know. /etc/udev/rules.d/60-persistent-storage.rules looks debian standard (SHA1: 5f8c2cc014940cc88910bbcb05c5cc5628d1f96c)
rules for by-id look slightly different than for by-path.

tried reloading udev and reconnecting the target, but without luck.
 
is you disk connected ?
maybe with another name

# lsscsi

and then the scsi_id command

Code: 
neptune2:~#  /lib/udev/scsi_id -g -x -s /dev/sdb
ID_VENDOR=DataCore
ID_MODEL=SANmelody
ID_REVISION=DCS
ID_SERIAL=360030d9050726f786d6f782d53520000
ID_SERIAL_SHORT=60030d9050726f786d6f782d53520000
ID_TYPE=disk
neptune2:~#
 
You must log in or register to reply here.
Top Bottom