O ESXi 4.1 não detecta mais o armazenamento de dados iSCSI

Question

Resumindo, tivemos uma falha de unidade em um destino iSCSI RAID5. Nós substituímos a unidade e reconstruímos com sucesso. Infelizmente depois disso, o ESXi perdeu o armazenamento de dados. Ele ainda aparece no adaptador de software iSCSI, mas não há armazenamento de dados correlacionado. Eu procurei em todos os lugares tentando corrigir o problema.

No console do ESXi:

esxcfg-scsidevs -c

Result:
Device UID                                            Device Type      Console Device                                                            Size      Multipath PluginDisplay Name
t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F  Direct-Access    /vmfs/devices/disks/t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F  1878417MB NMP     svndirect

Existem dois outros datastores, mas não estou preocupado com eles (são locais e funcionam). Aquele acima é o problema.

fdisk -l /vmfs/devices/disks/t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F

Result:
Disk /vmfs/devices/disks/t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F: 1969.6 GB, 1969663770624 bytes
255 heads, 63 sectors/track, 239464 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes


Device Boot      Start         End      Blocks  Id System
/vmfs/devices/disks/t10.9454450000000000C5544A6D0391F67FD6598A8260293F4Fp1             1    239464 1923494516   fb  VMFS

Ele diz que é o VMFS, então a partição não está faltando. Quando tento excluir e adicionar novamente o iSCSI, o seguinte é registrado em / var / log / messages:

May  9 16:35:58 Hostd: [2012-05-09 16:35:58.606 FFD97E90 info 'TaskManager' opID=4047693D-000001C2] Task Created : haTask-ha-host-vim.host.StorageSystem.addInternetScsiStaticTargets-871
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.629 47EF3B90 verbose 'StorageSystem' opID=4047693D-000001C2] SendStorageInfoEvent() called
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.630 47EF3B90 info 'TaskManager' opID=4047693D-000001C2] Task Completed : haTask-ha-host-vim.host.StorageSystem.addInternetScsiStaticTargets-871 Status success
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.643 47CE2B90 info 'App'] CreateISCSIHBA
May  9 16:35:58 vmkernel: 0:04:46:41.850 cpu14:4685)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x41027f9e6040) to NMP device "mpx.vmhba0:C0:T0:L0" failed on physical path "vmhba0:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  9 16:35:58 vmkernel: 0:04:46:41.850 cpu14:4685)ScsiDeviceIO: 1672: Command 0x12 to device "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.743 47CE2B90 error 'App'] Unable to build Durable Name dependent properties: Unable to query VPD pages from device, all paths are dead, no I/O possible.
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.794 47CE2B90 verbose 'App'] Looking up object with name = "firewallSystem" failed.
May  9 16:35:58 Hostd: [2012-05-09 16:35:58.857 47CE2B90 verbose 'NetConfigProvider'] FetchFn: List of pnics opted out
May  9 16:35:59 Hostd: [2012-05-09 16:35:59.492 47CE2B90 verbose 'NetConfigProvider'] FetchFn: List of pnics opted out
May  9 16:36:00 Hostd: [2012-05-09 16:36:00.072 47CE2B90 warning 'PropertyCollector'] ComputeGUReq took 1442151 microSec
May  9 16:36:02 Hostd: [2012-05-09 16:36:02.910 47CE2B90 info 'TaskManager' opID=4047693D-000001CC] Task Created : haTask-ha-host-vim.host.StorageSystem.rescanHba-872
May  9 16:36:02 iscsid: Login Target: iqn.2004-08.jp.buffalo:TS-RIXL6F4-0024A525A6F4:svndirect if=default addr=192.168.100.2:3260 (TPGT:65536 ISID:0x1)
May  9 16:36:02 iscsid: Notice: Assigned (H33 T0 C0 session=14, target=1/1)
May  9 16:36:02 iscsid: DISCOVERY: Pending=1 Failed=0
May  9 16:36:03 vmkernel: 0:04:46:46.282 cpu9:4812)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x4100a4317810 network resource pool netsched.pools.persist.iscsi associated
May  9 16:36:03 iscsid: Portal group tag mismatch, expected 65536, received 1
May  9 16:36:03 vmkernel: 0:04:46:46.554 cpu9:4812)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba33:CH:0 T:0 CN:0: iSCSI connection is being marked "ONLINE"
May  9 16:36:03 iscsid: Login Success: iqn.2004-08.jp.buffalo:TS-RIXL6F4-0024A525A6F4:svndirect if=default addr=192.168.100.2:3260 (TPGT:1 ISID:0x1)
May  9 16:36:03 vmkernel: 0:04:46:46.554 cpu9:4812)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000001 TARGET: iqn.2004-08.jp.buffalo:TS-RIXL6F4-0024A525A6F4:svndirect TPGT: 1 TSIH: 0]
May  9 16:36:03 vmkernel: 0:04:46:46.554 cpu9:4812)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.100.8:53668 R: 192.168.100.2:3260]
May  9 16:36:03 vmkernel: 0:04:46:46.554 cpu11:4134)WARNING: ScsiCore: 1353: Power-on Reset occurred on vmhba33:C0:T0:L0
May  9 16:36:03 vobd: May 09 16:36:03.447: 17206554467us: [vob.scsi.scsipath.por] Power-on Reset occurred on vmhba33:C0:T0:L0.
May  9 16:36:03 vmkernel: 0:04:46:46.555 cpu11:4134)vmw_psp_fixed: psp_fixedSelectPathToActivateInt: Changing active path from NONE to vmhba33:C0:T0:L0 for device "t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F".
May  9 16:36:03 vobd: May 09 16:36:03.448: 17206555428us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba33:C0:T0:L0 changed state from dead.
May  9 16:36:03 vobd: May 09 16:36:03.448: 17207216399us: [esx.clear.storage.connectivity.restored] Connectivity to storage device t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F (Datastores: Unknown) restored. Path vmhba33:C0:T0:L0 is active aga
May  9 16:36:03 in..
May  9 16:36:03 iscsid: connection 1:0 (iqn.2004-08.jp.buffalo:TS-RIXL6F4-0024A525A6F4:svndirect if=default addr=192.168.100.2:3260 (TPGT:1 ISID:0x1)  (T0 C0)) is operational
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.449 48840B90 info 'ha-eventmgr'] Event 94 : Connectivity to storage device t10.9454450000000000C5544A6D0391F67FD6598A8260293F4F (Datastores: Unknown) restored. Path vmhba33:C0:T0:L0 is active again.
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.449 47C60B90 verbose 'Hostsvc::DatastoreSystem'] VmfsVobUpdate: got Vob message [N11HostdCommon6VobMsgE:0x48d1cbb0] timestamp=17207216885
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.449 47C60B90 verbose 'Hostsvc::DatastoreSystem'] VmfsVobUpdate: Datastore Unknown not found
May  9 16:36:03 iscsid: DISCOVERY: Pending=0 Failed=0
May  9 16:36:03 vmkernel: 0:04:46:47.055 cpu1:8900)ScsiScan: 1059: Path 'vmhba33:C0:T0:L0': Vendor: 'IET     '  Model: 'VIRTUAL-DISK    '  Rev: '0   '
May  9 16:36:03 vmkernel: 0:04:46:47.055 cpu1:8900)ScsiScan: 1062: Path 'vmhba33:C0:T0:L0': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.949 48918B90 verbose 'StorageSystem' opID=4047693D-000001CC] SendStorageInfoEvent() called
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.949 48881B90 verbose 'StorageSystem'] StoragePathUpdate: Invalidate Path Cache immediately
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.949 48881B90 verbose 'StorageSystem'] SendStorageInfoEvent() called
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.949 48918B90 verbose 'Hostsvc::DatastoreSystem' opID=4047693D-000001CC] ReconcileVMFSDatastores called: refresh = true, rescan = false
May  9 16:36:03 Hostd: [2012-05-09 16:36:03.949 48918B90 verbose 'FSVolumeProvider' opID=4047693D-000001CC] RefreshVMFSVolumes called
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.047 48918B90 verbose 'FSVolumeProvider' opID=4047693D-000001CC] RefreshVMFSVolumes: refreshed volume, id 4c99efca-ac76eb4e-16a1-00219ba3e871, name datastore1
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'FSVolumeProvider' opID=4047693D-000001CC] RefreshVMFSVolumes: refreshed volume, id 4c99efd0-316cd952-d364-00219ba3e871, name datastore2
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'Hostsvc::Datastore' opID=4047693D-000001CC] SetVolume: Datastore 4c99efca-ac76eb4e-16a1-00219ba3e871 has changed provider volume pointer
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'Hostsvc::Datastore' opID=4047693D-000001CC] SetVolume: Datastore 4c99efd0-316cd952-d364-00219ba3e871 has changed provider volume pointer
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'Hostsvc::DatastoreSystem' opID=4047693D-000001CC] ReconcileVMFSDatastores: Done discovering new filesystem volumes.
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 info 'TaskManager' opID=4047693D-000001CC] Task Completed : haTask-ha-host-vim.host.StorageSystem.rescanHba-872 Status success
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.143 47C60B90 info 'App'] CreateISCSIHBA
May  9 16:36:04 vmkernel: 0:04:46:47.341 cpu12:4685)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4102bf1f8440) to NMP device "mpx.vmhba0:C0:T0:L0" failed on physical path "vmhba0:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  9 16:36:04 vmkernel: 0:04:46:47.341 cpu12:4685)ScsiDeviceIO: 1672: Command 0x12 to device "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
May  9 16:36:08 Hostd: [2012-05-09 16:36:08.591 48840B90 verbose 'Cimsvc'] Ticket issued for CIMOM version 1.0, user root
May  9 16:36:08 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:08 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:08 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:08 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0
May  9 16:36:09 sfcb-vmware_base[6314]: storelib Physical Device Device ID           : 0x0

Estou particularmente preocupado com estas linhas:

May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'Hostsvc::Datastore' opID=4047693D-000001CC] SetVolume: Datastore 4c99efca-ac76eb4e-16a1-00219ba3e871 has changed provider volume pointer
May  9 16:36:04 Hostd: [2012-05-09 16:36:04.128 48918B90 verbose 'Hostsvc::Datastore' opID=4047693D-000001CC] SetVolume: Datastore 4c99efd0-316cd952-d364-00219ba3e871 has changed provider volume pointer

Este parece ser o meu datastore iSCSI que foi detectado, mas não funciona? Não tenho certeza.

Eu até tentei me conectar ao iSCSI sozinho e usar as ferramentas do VMFS disponíveis no Ubuntu para tentar analisar os dados, mas ele sempre falhava sempre que eu tentava extrair informações ou listar arquivos. Eu até tentei com o aplicativo Java VMFS, que também falhou. Talvez o VMFS esteja corrompido? Não consegui encontrar uma maneira de tentar reparar o dispositivo, porque as ferramentas que o VMware oferece parecem funcionar apenas em volumes (e não aparecem como um volume VMFS).

O LUN aparece quando você adiciona, mas diz que quer formatá-lo e apagá-lo.

    

Answer 1

Eu acho que você tem um problema de direitos com o LUN, verifique se ainda é RW primeiro ok.