长话短说，我们的 RAID5 iSCSI 目标上有一个驱动器故障。我们更换了驱动器并成功重建。不幸的是，完成此操作后，ESXi 丢失了数据存储。它仍然显示在 iSCSI 软件适配器中，但没有关联的数据存储。我到处搜索试图修复该问题。
从 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
还有另外两个数据存储，但我并不关心它们（它们是本地的，可以工作）。上面的那个是问题所在。
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
它说它是 VMFS，所以分区没有丢失。当我尝试删除并重新添加 iSCSI 时，以下内容会记录到 /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
我特别关心这些内容：
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
这似乎是检测到的我的 iSCSI 数据存储，但它不起作用？我不确定。
我甚至尝试自己连接到 iSCSI，并使用 Ubuntu 中提供的 VMFS 工具来尝试查看数据，但每当我尝试提取信息或列出文件时，它总是会崩溃。我甚至尝试使用 VMFS Java 应用程序，但也失败了。也许 VMFS 已损坏？我找不到尝试修复设备的方法，因为 VMware 提供的工具似乎仅适用于卷（并且它不会显示为 VMFS 卷）。
添加时 LUN 确实会出现，但是它表示要格式化并擦除它。
答案1
我认为您对 LUN 有权利问题，请先检查它是否仍然是 RW。