Solved

Errors installing VM's directly on SAN

Posted on 2011-03-19
4
592 Views
Last Modified: 2012-06-27
I am running ESX 4.1 with connecitons to both an AX150 fiber SAN and an Openfiler iSCSI SAN.  All NIC's are 1Gb.  When I try installing a VM on either Fiber or iSCSI directly (instead of on local disk first then moving it to the SAN), I get errors.  The iSCSI network connection eventually starts freaking out part way through the install, at which point my continuous pings start dropping to 50% successful, which causes the VM install to fail.  

When I try installing directly to the Fiber SAN, it gets down to about 7 minutes left on Windows 2003 Server and gives me the error:  Windows was unable to save all the data for the file C:\Windows\System32\setupapi.dll.  The data has been lost.  This error may be caused by a failure of your computer hardware or network connection.  Please try to save this file elsewhere.  

So this leads to my question:  Is it always best to install a VM on the local disk then move it to the SAN, or should it not normally matter?  Note that after installing on local disk and moving to iSCSI, VM works fine.
0
Comment
Question by:B1izzard
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 30

Expert Comment

by:IanTh
ID: 35172873
is any vms currently working on the san
0
 
LVL 16

Accepted Solution

by:
danm66 earned 350 total points
ID: 35173325
That is not normal behavior, you should be able to create a new VM directly on the SAN.  Since it is affecting both iSCSI and FC, then I'd look for something wrong in the host logs /var/log/vmkernel
0
 
LVL 5

Assisted Solution

by:zazagor
zazagor earned 150 total points
ID: 35198674
Hi,

Both ways should work but local disk is faster.

//zaZagor
0
 

Author Closing Comment

by:B1izzard
ID: 35204520
Strangely enough, I used a different Windows DVD to install on fiber and it worked ok.  I created a 'bonded' NIC in OpenFiler so I now have 2 x 1Gb and it seems to be working.  Strange..
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
A look into Log Analysis and Effective Critical Alerting.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question