Initializing Disk in Windows 2008R2 VM with iscsi crashes machine

Hi,

I am using a HP Server running VMWare ESXi 5.0.0 with some local storage and also using a ReadyNAS NVX for iSCSI storage. The local storage contains all the vm's OS disks (currently 4 VMs) and the iSCSI will be used for secondary disks in the VMs (for file storage etc)

When we create a second disk located in the iscsi datastore to a virtual machine (powered on or off) and then login to the vm it asks if you want to initialize the disk and gives you the option to choose MBR or GPT. When we click ok the machine stops responding and the only option is to restart the VMware ESXi host to recover. This happens if MBR or GPT are chosen. I have outlined our setup below and troubleshooting steps we have already tried.

HP ML350 G6 Server with local SAS storage for the Virtual Machines OS
Netgear ReadyNAS NVX (firmware 4.2.19) - this has been factory reset
Dedicated nic directly connected between the ML350 and ReadyNAS
Server is running VMware ESXi, 5.0.0, 504890 (with iSCSI software patch)
Jumbo frames has been enabled on ReadyNAS, MTU has been set at 9000 in vmware for vSwitch and VMkernel Port
iSCSI Port Binding enabled in VMware
Static Discovery mode configured on iSCSI Initiator
I have created 2 luns and formatted one as VMFS 3 and one as VMFS5 problem exists with both.
Problem exists on 2 VMs one Version 7 and one Version 8
I have created 50-100GB disk to test.

Troubleshooting
Tried looped through switch
Set MTU to 1500
With and without CHAP and Access Control IQN on readynas

vmkping -s 8784 10.0.0.2 -d
PING 10.0.0.2 (10.0.0.2): 8784 data bytes
8792 bytes from 10.0.0.2: icmp_seq=0 ttl=64 time=0.452 ms
8792 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.444 ms
8792 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.541 ms



Any help is greatly appreciated as I'm running out of ideas!
skysysAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
A quick update the ReadyNAS NVX does not APPEAR on the VMware HCL for ESXi 5.0.

only 4.1 U2

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=san
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You may want to contact Netgear and VMware for confirmation, new firmware.

otherwise you could be wasting time.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

skysysAuthor Commented:
Hi,

Thanks for the quick response, I have read through your articles, we are not using multipathing or teaming but essentially the setup is the same.
I'm not using the Microsoft iSCSI intiator as I've created a datastore on the LUN and then added a virtual disk to the VM stored in the datastore.

HCL could unfortunatly be the answer, it was working fine with 4.1 U1

Thanks,

Ian
0
skysysAuthor Commented:
From the Readynas.com forums
For ESXi 5 if using iSCSI you will need RAIDiator 4.2.20 or later. RAIDiator 4.2.20 is currently in beta
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Again, it's not currently certfied for use with ESXi 5.0, missing from the HCL.

I would suggest upgrading at your risk.
0
skysysAuthor Commented:
I think we'll roll back to 4.1 and wait. At least we hadn't upgraded the VM Versions for our servers.

Thanks for your help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.