Hi all,
# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
I have a single Proxmox host connected via iSCSI to a Drobo B800i. This has worked fine for a while until recently when my LVs disappeared.
I am now in a position where I can see the iSCSI LUN and log in and out of it:
root@ess-prox-010:~# iscsiadm -m node -T iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1 -p 10.50.50.1:3260 --logout
Logging out of session [sid: 1, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]
Logout of [sid: 1, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]: successful
root@ess-prox-010:~# iscsiadm -m node -T iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1 -p 10.50.50.1:3260 --login
Logging in to [iface: default, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]
Login to [iface: default, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]: successful
But can't see any LV's inside of it:
root@ess-prox-010:~# lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID cxsffv-eysv-T6lQ-2nFS-J3cr-kV7H-tIDHnf
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 15.00 GiB
Current LE 3840
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID AK07vr-SQxp-bV1e-Yk4d-gLjD-aEqt-0UEe6l
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID o14S0s-kcoZ-Fxy8-xNm2-slf3-Q8bi-Yg1TZE
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 803.50 GiB
Current LE 205696
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
root@ess-prox-010:~# vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 1140
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 930.50 GiB
PE Size 4.00 MiB
Total PE 238207
Alloc PE / Size 234112 / 914.50 GiB
Free PE / Size 4095 / 16.00 GiB
VG UUID Th1fRX-9vhe-o0L8-fPPX-b1w4-IdJP-cdq6jh
root@ess-prox-010:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV Size 930.50 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 238207
Free PE 4095
Allocated PE 234112
PV UUID C6xSvu-hHdU-Eu7T-QInc-f0HH-0s0j-3KMHvR
"/dev/disk/by-id/dm-name-36001a620000142313132344230323135" is a new physical volume of "16.00 TiB"
--- NEW Physical volume ---
PV Name /dev/disk/by-id/dm-name-36001a620000142313132344230323135
VG Name
PV Size 16.00 TiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID Wa3Vtu-TUQN-qFXN-Vbub-oZ7b-RQTd-4wxeZW
Have tried doing hard reset on Drobo, switch and Proxmox server with no joy.
Syslog is showing this:
Aug 15 16:46:48 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:46:48 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:27 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:27 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:47 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:47 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:48:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:48:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Which I'm guessing is part of the problem.
Any ideas?
c
# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
I have a single Proxmox host connected via iSCSI to a Drobo B800i. This has worked fine for a while until recently when my LVs disappeared.
I am now in a position where I can see the iSCSI LUN and log in and out of it:
root@ess-prox-010:~# iscsiadm -m node -T iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1 -p 10.50.50.1:3260 --logout
Logging out of session [sid: 1, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]
Logout of [sid: 1, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]: successful
root@ess-prox-010:~# iscsiadm -m node -T iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1 -p 10.50.50.1:3260 --login
Logging in to [iface: default, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]
Login to [iface: default, target: iqn.2005-06.com.drobo:b800i.tdb1124b0215.id1, portal: 10.50.50.1,3260]: successful
But can't see any LV's inside of it:
root@ess-prox-010:~# lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID cxsffv-eysv-T6lQ-2nFS-J3cr-kV7H-tIDHnf
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 15.00 GiB
Current LE 3840
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID AK07vr-SQxp-bV1e-Yk4d-gLjD-aEqt-0UEe6l
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID o14S0s-kcoZ-Fxy8-xNm2-slf3-Q8bi-Yg1TZE
LV Write Access read/write
LV Creation host, time proxmox, 2013-01-07 10:22:53 +0000
LV Status available
# open 1
LV Size 803.50 GiB
Current LE 205696
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
root@ess-prox-010:~# vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 1140
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 930.50 GiB
PE Size 4.00 MiB
Total PE 238207
Alloc PE / Size 234112 / 914.50 GiB
Free PE / Size 4095 / 16.00 GiB
VG UUID Th1fRX-9vhe-o0L8-fPPX-b1w4-IdJP-cdq6jh
root@ess-prox-010:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV Size 930.50 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 238207
Free PE 4095
Allocated PE 234112
PV UUID C6xSvu-hHdU-Eu7T-QInc-f0HH-0s0j-3KMHvR
"/dev/disk/by-id/dm-name-36001a620000142313132344230323135" is a new physical volume of "16.00 TiB"
--- NEW Physical volume ---
PV Name /dev/disk/by-id/dm-name-36001a620000142313132344230323135
VG Name
PV Size 16.00 TiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID Wa3Vtu-TUQN-qFXN-Vbub-oZ7b-RQTd-4wxeZW
Have tried doing hard reset on Drobo, switch and Proxmox server with no joy.
Syslog is showing this:
Aug 15 16:46:48 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:46:48 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:27 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:27 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:47:47 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:47:47 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Aug 15 16:48:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Got wrong page
Aug 15 16:48:07 ess-prox-010 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Which I'm guessing is part of the problem.
Any ideas?
c