Cannot install guest OS on iSCSI LVM

M

Mr.SunStar

Member
Dec 22, 2011
4
0
21
We've created an LVM storage over iSCSI without any problem as described in the wiki page:

http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups_with_Network_Backing

Our problem is that the guest OS cannot recognize the storage device allocated to it from the iSCSI-LVM storage. The guest OS in this case is Windows XP and during the installation process, upon reaching the part where you select the partition to install Windows on, it says:

32766 MB Disk 0 at Id 0 on bus 0 on atapi
(Setup cannot access this disk)​

I don't know if this is related to the problem or not but after creating the VM (windows xp, 32GB, 512MB, raw, IDE) with the iSCSI-LVM storage selected as the Disk Storage device, the following messages show on screen:

/usr/sbin/qm create 102 --cdrom ISO_Images:iso/winxp_sp3.iso --name test_winxp_01 --vlan0 rtl8139=56:07:08:3D:26:0A --bootdisk ide0 --ostype wxp --ide0 ISCSI1_LVM:32,format=raw --memory 512 --onboot no --sockets 1
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc
Logical volume "vm-102-disk-1" created
VM 102 created

Here is the pveversion we are using:
pve-manager/1.9/6542
virtualmachine1:~# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

Any help is greatly appreciated.
 
This is the output for pvdisplay, lvdisplay and vgdisplay after connecting to the iSCSI target (but before creating the LVM):

virtualmachine1:~# pvdisplay​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc​
--- Physical volume ---​
PV Name /dev/sdd​
VG Name Thecus7700SS​
PV Size 1.53 TB / not usable 4.00 MB​
Allocatable yes​
PE Size (KByte) 4096​
Total PE 400127​
Free PE 400127​
Allocated PE 0​
PV UUID 4qsFBk-fuXU-fH0o-gFTs-65pi-Inbc-rvvOxX​

​
--- Physical volume ---​
PV Name /dev/sda2​
VG Name pve​
PV Size 135.62 GB / not usable 244.00 KB​
Allocatable yes​
PE Size (KByte) 4096​
Total PE 34718​
Free PE 1022​
Allocated PE 33696​
PV UUID cQZidr-kkEK-aEFH-6Q0Z-FMzB-Gawz-5ScUHc​

​
virtualmachine1:~# lvdisplay​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc​
--- Logical volume ---​
LV Name /dev/pve/swap​
VG Name pve​
LV UUID NjhPYz-bZh2-62VF-fV6Q-mkBt-skjX-z3aLpm​
LV Write Access read/write​
LV Status available​
# open 1​
LV Size 17.00 GB​
Current LE 4352​
Segments 1​
Allocation inherit​
Read ahead sectors auto​
- currently set to 256​
Block device 253:0​

​
--- Logical volume ---​
LV Name /dev/pve/root​
VG Name pve​
LV UUID ocJCGV-N7Mm-jTN6-kFT1-Ncr6-sQsU-sV7hKt​
LV Write Access read/write​
LV Status available​
# open 1​
LV Size 34.00 GB​
Current LE 8704​
Segments 1​
Allocation inherit​
Read ahead sectors auto​
- currently set to 256​
Block device 253:1​

​
--- Logical volume ---​
LV Name /dev/pve/data​
VG Name pve​
LV UUID qGbUtk-h0iB-JCeT-JAzA-u01F-puYY-DP5cIt​
LV Write Access read/write​
LV Status available​
# open 1​
LV Size 80.62 GB​
Current LE 20640​
Segments 1​
Allocation inherit​
Read ahead sectors auto​
- currently set to 256​
Block device 253:2​

​
virtualmachine1:~# vgdisplay​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdc not /dev/sdb​
Found duplicate PV 4qsFBkfuXUfH0ogFTs65piInbcrvvOxX: using /dev/sdd not /dev/sdc​
--- Volume group ---​
VG Name Thecus7700SS​
System ID​
Format lvm2​
Metadata Areas 1​
Metadata Sequence No 5​
VG Access read/write​
VG Status resizable​
MAX LV 0​
Cur LV 0​
Open LV 0​
Max PV 0​
Cur PV 1​
Act PV 1​
VG Size 1.53 TB​
PE Size 4.00 MB​
Total PE 400127​
Alloc PE / Size 0 / 0​
Free PE / Size 400127 / 1.53 TB​
VG UUID tXPwgD-UyRD-je33-9r3a-6ZCz-0csb-OCn4V0​

​
--- Volume group ---​
VG Name pve​
System ID​
Format lvm2​
Metadata Areas 1​
Metadata Sequence No 4​
VG Access read/write​
VG Status resizable​
MAX LV 0​
Cur LV 3​
Open LV 3​
Max PV 0​
Cur PV 1​
Act PV 1​
VG Size 135.62 GB​
PE Size 4.00 MB​
Total PE 34718​
Alloc PE / Size 33696 / 131.62 GB​
Free PE / Size 1022 / 3.99 GB​
VG UUID MDHzYf-c3Bx-QwEk-DG3L-cazC-8Bbc-ihBBsJ​






This is from dmesg after connecting to the iSCSI target:
scsi15 : iSCSI Initiator over TCP/IP​
scsi16 : iSCSI Initiator over TCP/IP​
scsi17 : iSCSI Initiator over TCP/IP​
scsi 16:0:0:0: Direct-Access SCST_FIO vg1i0 210 PQ: 0 ANSI: 5​
scsi 15:0:0:0: Direct-Access SCST_FIO vg1i0 210 PQ: 0 ANSI: 5​
sd 16:0:0:0: Attached scsi generic sg2 type 0​
sd 15:0:0:0: Attached scsi generic sg3 type 0​
scsi 17:0:0:0: Direct-Access SCST_FIO vg1i0 210 PQ: 0 ANSI: 5​
sd 17:0:0:0: Attached scsi generic sg4 type 0​
sd 15:0:0:0: [sdc] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 17:0:0:0: [sdd] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 16:0:0:0: [sdb] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 17:0:0:0: [sdd] Write Protect is off​
sd 17:0:0:0: [sdd] Mode Sense: 83 00 10 08​
sd 16:0:0:0: [sdb] Write Protect is off​
sd 16:0:0:0: [sdb] Mode Sense: 83 00 10 08​
sd 15:0:0:0: [sdc] Write Protect is off​
sd 15:0:0:0: [sdc] Mode Sense: 83 00 10 08​
sd 17:0:0:0: [sdd] Write cache: disabled, read cache: enabled, supports DPO and FUA​
sd 16:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA​
sd 15:0:0:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA​
sd 17:0:0:0: [sdd] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 16:0:0:0: [sdb] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 15:0:0:0: [sdc] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sdb:​
sdd:​
sdc: unknown partition table​
unknown partition table​
unknown partition table​
sd 16:0:0:0: [sdb] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 17:0:0:0: [sdd] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 15:0:0:0: [sdc] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sd 16:0:0:0: [sdb] Attached SCSI disk​
sd 17:0:0:0: [sdd] Attached SCSI disk​
sd 15:0:0:0: [sdc] Attached SCSI disk​
sd 15:0:0:0: [sdc] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sdc: detected capacity change from 0 to 1678258470912​
sd 16:0:0:0: [sdb] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sdb: detected capacity change from 0 to 1678258470912​
sd 17:0:0:0: [sdd] 409731072 4096-byte logical blocks: (1.67 TB/1.52 TiB)​
sdd: detected capacity change from 0 to 1678258470912​


Is there any reason why it's detecting 3 devices (sdb, sdc, and sdd) when there was only one iscsi target being connected?
 
BTW, will the iSCSI block size matter to Proxmox? There is an option on the SAN for iSCSI block size and it is currently set at 4KB. The only other choice is 512 Bytes.
 
We found that since the server has 3 NIC cards that are connected to the switch (not aggregated) that this may have something to do with Proxmox connecting to 3 iSCSI targets instead of one. Removing two of the NICs from the switch did solve the problem.

So, we do need to have all 3 NICs up. How can this be resolved?
 
if you use iSCSI you should use a dedicated network for accessing this storage.
 
You must log in or register to reply here.
Top Bottom