VMware ESXi 4.0 can't access VMFS storage after every reboot host.

[Jae-Hoon_Choi]

I have 3 VMware ESXi 3.5 Hosts and all systems equip same below.

Intel Xeon 5420 2Way-SMP Processors

Supermicro X7DWA-N

32GB FBDIMM

Adaptec ASR3805 SAS Controller

SC743TQ-865B

Intel Pro 1000 MT Server NIC

Intel Pro 1000 PT Desktop NIC

System Disk Western Digital Raptor 73GB connected ESB6300 AHCI mode

VMstorage Disks connected Adaptec ASR-3805 SAS controller with RAID 5

I installed ESXi 4.0 to my host and boot successfully with system disk.

but, vmstorage can't access.

Storage Adapter 3805 was detected.

But, VMstorage was detect after rescan storage adapter after host was reboot everytime.

AHCI storage was detected Block SCSI device and ASR-3805 was detected SCSI device.

2nd) I was tried to install ESXi 4.0 on ASR-3805 VMstorage.

Installation was successfull, but boot was fail

it's a boot log image.

What's wrong?

P.S

ASR-3805, Supermicro X7DWA-N have latest firmware and ESXi 3.5 update 4 wasn't have

any problems.

Host installation completed with USB external DVDROM drive.

[Jae-Hoon_Choi]

At last, new builde 171294 was released and my test is going.

But, same conclusion.

Below is my VMware ESXi 4.0 logs.

What's wrong?

Why VMware ESXi 4.0 recognize as Parallel SCSI storage controller that my Adaptec ASR-3805 SAS controller?

2009-06-25 12:20:01.803 1D609D90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:20:02.704 1D609D90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:20:02.721 1D609D90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:20:21.871 1D84CB90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:20:21.874 1D84CB90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:22:25.523 1D80BB90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:22:25.557 1D789B90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:23.647 1D609D90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:23.650 1D609D90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:25.740 14FC1B90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:25.741 14FC1B90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:25.766 1D84CB90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:25.768 1D84CB90 error 'App' Error adding Target:key-vim.host.PlugStoreTopology.Target-pscsi.0:0 Path:pscsi.vmhba2-pscsi.0:0-mpx.vmhba2:C0:T0:L0 Device:0000000000766d686261323a303a30 to ScsiTopology. Msg: vim.fault.AlreadyExists

2009-06-25 12:30:34.420 1D8CEB90 verbose 'Partitionsvc' InvokePartedUtil /sbin/partedUtil "get" "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0"

2009-06-25 12:30:34.678 1D8CEB90 verbose 'Partitionsvc' Output Stream from partedUtil while getting partitions for /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:

2009-06-25 12:30:34.689 14FC1B90 verbose 'Partitionsvc' InvokePartedUtil /sbin/partedUtil "get" "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0"

2009-06-25 12:30:35.680 14FC1B90 verbose 'Partitionsvc' Output Stream from partedUtil while getting partitions for /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:

2009-06-25 12:30:45.464 1D88DB90 verbose 'Partitionsvc' InvokePartedUtil /sbin/partedUtil "get" "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0"

2009-06-25 12:30:45.700 1D88DB90 verbose 'Partitionsvc' Output Stream from partedUtil while getting partitions for /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:

2009-06-25 12:30:45.737 14FC1B90 verbose 'Partitionsvc' InvokePartedUtil /sbin/partedUtil "set" "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0" "1 63 2491408394 251 0"

2009-06-25 12:30:46.723 14FC1B90 verbose 'FSVolumeProvider' LookupVmfs: Cannot find VMFS volume with disk name mpx.vmhba2:C0:T0:L0 and number 1

[nicodr]

I have the same problem with ESXi 4 171294 on a system with an Adaptec 3805. I managed to get ESXi working by using an extra single disk as boot disk but when I try to put an image on the raid the system fails. I tried replacing the disks but that didn't solve anything.

I have another system with an Adaptec 2420SA which works perfectly using the same disks. The strange thing is that the 3805 is supposed to be officialy supported while the 2420 is not officialy supported.

Haven't found a solution yet.

Nico

[Jae-Hoon_Choi]

I found solution myself.

My Supermicro X7DWA-N BIOS setup is point.

The question is Advanced Chipset Control - Intel VT for Directed I/O option to disabled

Supermicro or Adaptec or VMware knows basic problem.

But, I can't say anymore.

I was just disappoint support from Supermicro, Adaptec and VMware.

That's all...

[Jae-Hoon_Choi]

I found solution myself.

My Supermicro X7DWA-N BIOS setup is point.

The question is Advanced Chipset Control - Intel VT for Directed I/O option to disabled

Supermicro or Adaptec or VMware knows basic problem.

But, I can't say anymore.

I was just disappoint support from Supermicro, Adaptec and VMware.

That's all...

[CraigJHCOPY]

Thank you for posting yousr answer. It unlocked my server. I have the adaptec 3805 and unsupported supermicro server as vmware support so kindly informed me. I had ESXI install successfully and then fail to find boot partition.I needed two bios changes. First, advance chipset control\Intel VT for directed I/O (VT-d) needed to be disabled and second the motherboard SATA needed to be set to compatible or enhance (ACHI is disabled but I did not test with this enabled.)