Storage SAN (data store) cannot be seen by guests

Similar Questions

• Impossible to add storage as data store

  Hello

  I started with 4 esxi servers 5 to test the object with the method of assessment and added the common datastore on all 4 servers for virtual machines that worked very well. but the tests I formatted 2 esxi servers and installed ESXi 4 top, now when I am adding common storage in these 2 ESXi 4 Server I get the error attached, I have found the solution so that it can delete the partition with fdisk command to this logical unit number, but this LUN is common for all 4 servers and virtual machines running on it for 2 ESXi 5 host , so please, someone has the solution to this problem

  Another problem is that showing time in hostd.log file is different because I have configured in Setup esxi why its different time showing.

  Thank you Sam

  Please mark question answers

  Frank

  Am 03.09.2012 um 18:49 wrote sagar_arora [email protected]<>[email protected]>:

  Http://communities.vmware.com/index.jspaVMware communities >

  Impossible to add storage as data store

  sagar_arorahttp://communities.vmware.com/people/sagar_aroraresponse > in VMware ESXi 5 - see the discussion complete onhttp://communities.vmware.com/message/2108663#2108663

• Get-hard drives - storage drives data store migrate between data warehouses

  Hi all

  
  

  Our current storage configuration with specially designed split-role of the bases of data storages (OS, LOG SQL, SQL DATA, APP, Exchange roles, etc.)  I do a storage store on my VMware Infrastructure and hoped to target only the disks of virtual machines that are on any data store and migrate them to another.  Rather new to PowerCli if you're wondering why the bellows of the command does not work and the reports that the file is locked.
  

  
  

  Get-hard drive - data store 'Datastore01 ' | Moving-hard drive - data store Datastore02

  If the machine virtual itself is made aware of the command?  Would I have to enumarte the virtual machines on the first data store and then target discs that everyone has and redirect it to the hard disk Move command?

  Thanks in advance

  Yes, you are banging in the sequence of commands trying to move a file on the data store without referencing the virtual machine. According to the State of the virtual machine (lit or not) of different things happen

  • VM power off - the disc is moved and the virtual machine is broken (the vmx file will always point to the original location for the HD that is no longer there)
  • Virtual MACHINE power - the disk is locked, so it cannot be moved (the error you have seen)

  Another thing to keep in mind is that the configuration of the VM is also on a data store, so if you want to move the entire virtual machine you can just move the hard drives

  If all the virtual machines on a data store have all their HDs on this data store then you can do something like

  Get - VM - data store 'Datastore01 ' | Move-VM - data store "Datastore02".

  To access the VM configuration, but also his records. If you have virtual machines where the disks into a single virtual machine, then you will have a little more work to do to sort the records that must be moved

  Get - VM - data store 'Datastore01 ' | Get-hard drive | Where-Object {$_.} FileName.Contains ("[Datastore01]")} | Moving-hard drive - data store "Datastore02".

  This is all virtual machines with a component (hard drive or configuration) on Datastore1, and then for each VM is all hard disks that are on Datastore01 and the Datastore02

• Data store can be seen from a host, and then disappeared...

  I had a store of data on LUN 2 point.  Two GB 425 our EMC SAN LUNS have been used and it worked well on one of our ESX host.  We had not realised the rest of the armed forces had not resumed the data store.  I tried a new analysis on all hosts without success, the data store would simply not appear.  All the guests could see the LUNS, but with the same identifier.  Resignaturing disc is already enabled as these hosts also replicated LUN mount so I had to the potential problem of LUN ID set match to discount.  I checked the presentation of storage, fiber channel, zoning, everything was OK.  So I turned off the virtual machine and decided to anyone two LUNS to the Group of storage and the re - present but things only got worse...

  The data store has now completely disappeared.

  I was wondering if anyone else had encountered / solve such a problem?  I did a search on the community and the knowledge base and could not find anything to help me.

  I run fdisk and checked the Lun, but I'm stuck now.  My next step will be to log a call of support with VMWare...  Fortunately, it's on our DR site ESX host, but now I lost just a SQL database more than 600 GB in size...

  Disk vmhba1:1:0/dev/sdq (435200 MB) has 4 lanes and more recently used strategy

  FC 13:0.0 2100001b328500a5 & lt;-& gt; 500601693ce03346 vmhba1:1:0 favorite standby

  FC 13:0.0 2100001b328500a5 & lt;-& gt; 500601603ce03346 vmhba1:0:0 On assets

  FC 13:0.1 2101001b32a500a5 & lt;-& gt; 500601613ce03346 vmhba2:0:0 On

  FC 13:0.1 2101001b32a500a5 & lt;-& gt; 500601683ce03346 vmhba2:1:0 watch

  Disk vmhba1:0:5/dev/sdf (435200 MB) has 4 lanes and more recently used strategy

  FC 13:0.0 2100001b328500a5 & lt;-& gt; 500601603ce03346 vmhba1:0:5 on favorite assets

  FC 13:0.0 2100001b328500a5 & lt;-& gt; 500601693ce03346 vmhba1:1:5 watch

  FC 13:0.1 2101001b32a500a5 & lt;-& gt; 500601613ce03346 vmhba2:0:5 on

  FC 13:0.1 2101001b32a500a5 & lt;-& gt; 500601683ce03346 vmhba2:1:5 watch

  Disk/dev/sdq: 456,3 GB, 456340275200 bytes

  255 heads, 63 sectors/track, 55480 cylinders, total of 891289600 areas

  Units is 1 * 512 sectors is 512 bytes

  Device boot start end blocks Id system

  / dev/sdq1 128 891286199 445643036 unknown fb

  Disk/dev/sdf: 456,3 GB, 456340275200 bytes

  255 heads, 63 sectors/track, 55480 cylinders, total of 891289600 areas

  Units is 1 * 512 sectors is 512 bytes

  Device boot start end blocks Id system

  / dev/SDF1 128 891286199 445643036 unknown fb

  See you soon,.

  Dave

  PS. This morning I had the upgrade, one of the hosts in the cluster to 4 upgrade with the latest security patches and executing tests is when I found I couldn't vmotion prompt on any other host, and then realized the missing data on other host store.  All other hosts are 2 update, but I don't think this is related.

  Gracias thank you and Marcelo vmw-sfraser,.

  I have placed a request for assistance with VMWare and see how I'm going.  I noted that the mistake so when I saw the exit and thought that it would be likely that I have to log a call.

  See you soon,.

  Dave

• Configuration of San - data store have more than 1 LUN

  Hello

  We look at our San configuration for improvements. Our San has about 10 TB total.

  We currently have 6 LUN 1.5 TB all which are enclosed in 1 store 10 TB data

  It was suggested that we should NOT combine multiple LUNS in a data store for the reason if 1 LUN goes wrong then the entire data store is non-refundable.

  Although our SAN LUNS are created on top of raid 6 and are therefore a bit 'protected' by councils LUN 1 data store is interesting

  Does anyone have ideas to share?

  Thank you

  Tom D

  I would say that having a single data store, regardless of the underlying storage architecture is probably not a good idea.  Although this configuration is authorized you can paint yourself in a corner fairly quickly.

  1. one wonders about the maximum number of VMDK you should have by the data store.  http://communities.VMware.com/message/944120  Basically the more s VMDK on the SCSI data store more blocking of activity taking place on the disk, causing performance problems.  Each VMware engineer, I've talked about seems to stay around the VMDK 20 a range of data store, but that could change with vSphere.

  2 - How this data store backup and how long does it take?  What happens during a restore scenario?  10 TB is plenty of space and could take some time for the backup.  If you push it on tape and you must always restore the together 10 to it could take weeks or months.  This space by breaking into warehouses of smaller data gives you smaller segments of data that you can restore in case of disaster.

  3 - the number of data warehouses you have is very important if you are always looking to implement the Site Recovery Manager.  SRM relies on your storage device to replicate data between the sites.  There could be serious consequences on the rate of change of the data for a single LUN 10TB.  If you are moving in several data stores that it will make it easier to handle your recovery plan.

  Apart from the considerations above of VMware. I guess 7 performance LUNS in RAID-6 is not so great.  You have a lot of protection, but you pay for it with capacity and performance.  If you went to 10 stores of data and the LUN 10 you can change RAID settings at each data store to optimize performance, protection, and capacity.  For example 4 LUN RAID-10 high performance DB apps and 6 LUNS to RAID-5 for the ability.  With smaller LUN and data warehouses a disk or LUN failure will affect only a smaller set of services rather than your entire data center.

  In short, unless there is a really compelling reason to go with a single store of 10 TB database, I recommend you to change your architecture.

• Data store cannot increase the size

  I have some data stores that I'm not able to increase the size of.  Increase button is just off hard.  Some other data warehouses, I am able to do it without problem.

  All data warehouses are connected to the unit number logic on a NetApp via an iSCSI connection.  I increased the size on the side of NetApp, but this does not seem to matter.  In fact, he sees the extra space when I go into the properties of the data store.  All servers are running the same version being esxi 4.1.

  Most data warehouses are 3.33 but I have some 3.46 versions, but on both versions, some may be increased and some may not.  I was hoping that was the problem...

  The size of the data store varries.  Most of them have a block size of 1 MB.  None of the data warehouses are more than 500 GB.  Mostly between 300-400 GB.

  So I'm a bit at a loss.  I tried to resize them using the vCenter server and goes straight to the server esxi itself.  None of that seems to matter.

  Right now, I'm just at a loss.  I have not really found too much online about this problem.  A large number of documents to make errors trying to increase, but not a lot of increase being disabled.

  Thank you for your time.

  See if this KB helps

  Cannot cultivate VMFS datastore, the increase of button is disabled

  http://KB.VMware.com/kb/1035285

• Using several data stores, cannot migrate the vmx file in a data store

  I am host migration between 3.5 and 4.0, and part of the migration requires me to vmotion data to a single shared LUN data warehouses.  From there on, I import the virtual machine in 4.0 and using the script to migrate the two VM disks at different stores of data below.  The problem I have is that the configuration (vmx) file not migrated and is left on the shared storage LUNS.  Anyone knows how to go beyond this?

  The Script:

  $VMDisk = 'disk 1 '.

  $VMName = 'TestVM '.

  $TargetDS = get-Datastore - VMHost (Get-VMHost-$S.id Id) | Where-Object {$_.} Name - like "PMV"} | "" FreeSpaceMB tri-objet-descending | SELECT name - first of all 1

  $vm = get-View - ViewType VirtualMachine-filter @{"Name" = $VMName}

  foreach ($dev in $vm. Config.Hardware.Device) {if ($dev. DeviceInfo.Label - eq $vmDisk) {$diskId = $dev. Key}}

  $spec = new-Object VMware.Vim.VirtualMachineRelocateSpec

  $diskspec = new-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator

  $diskspec. Data store = (Get-Datastore-name $TargetDS.Name |) Get - View). MoRef

  $diskspec.diskId = $diskId

  $spec. Disk = @($diskspec)

  $task = get-View ($vm. RelocateVM_Task ($spec, "lowpriority"))

  OK, I think I understand your problem now.

  I fear that in the current construction of PowerCLI, the Move-VM cmdlet does not destinations of individual data for each virtual hard disk store.

  With the RelocateVM_Task method, it is possible.

  The following script moves a guest at 3 different data warehouses:

  -the. VMX file for DS2

  -hard disk 1 for DS3

  -hard drive 2 TB DS4

  $vmName = "MyGuest"
  $vmxDS = "DS2"
  $osDS = "DS3"
  $dataDS = "DS4"
  
  $vm = Get-VM -Name $vmName
  
  $vm.Extensiondata.Config.Hardware.Device | %{
       if ($_.DeviceInfo.Label -eq "Hard disk 1"){
            $osDiskId = $_.Key
       }
       elseif($_.DeviceInfo.Label -eq "Hard disk 2"){
            $dataDiskId = $_.Key
       }
  }
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec
  
  $osRelocate = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $osRelocate.Datastore = (Get-Datastore -Name $osDS).Extensiondata.MoRef
  $osRelocate.diskId = $osDiskId
  
  $dataRelocate = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  $dataRelocate.Datastore = (Get-Datastore -Name $dataDS).Extensiondata.MoRef
  $dataRelocate.diskId = $dataDiskId
  
  $spec.Disk = @($osRelocate,$dataRelocate)
  $spec.Datastore = (Get-Datastore -Name $vmxDS).Extensiondata.MoRef
  $spec.Host = $vm.Extensiondata.Summary.Runtime.Host
  
  $task = Get-View ($vm.Extensiondata.RelocateVM_Task($spec, "lowpriority"))
  while("running","queued" -contains $task.Info.State){
       $task.UpdateViewData("Info")
       sleep 5
  }
  

  BTW, you can use the cmdlet Set - hard disk to a virtual disk that is specific to a data store.

  But as I understood what is not possible in your environment.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Storage vMotion a VM except disk that is in another data store

  Hello

  I'm looking to convert a large number of virtual machines clones related to thick.  I decided the best way to do this is probably a simple a storage vMotion, but all the virtual machines have a secondary drive that is in another data store.  I have to make sure that disk #2 stays at its current location, while the machine virtual (Config and disk #1 files) are transferred to a new data store data store.

  I figured out how to move a virtual machine complete or a single disc but not a virtual machine under a disc.  I am able to make it through the advanced options of puissancela vSphere client so I guess it is techinically possible.

  Pointers or other ideas would be greatly appreciated.

  Kind regards

  Ty-

  You will need to use the API method, see for example Re: using several data stores, cannot migrate the vmx file in a data store

• Cannot remove the data store

  Hello

  I am trying to remove a shared in Vsphere 5.0 SAN data store, and it fails to say that the datstore is in use. When I try to take it apart there is a red cross next to the statement that no virtual machines must be present. The data store is empty and afaics no point of virtual machines don't have any disk pointing it at all. He got a present HA heartbeat folder but I've reconfigured HA no to use the DS and could then remove the folder HA and empty so the DA, but still in use reports

  Gerry,

  Is it possible that your virtual machine contains a cd connected to the data store? I came across that once where a virtual machine was showing that the use of two data warehouses, but there files were only in one. I found that I had connected the reader of cd/dvd via the client to a file that was in this other data store. Just a thought.

  The f

• Upgrade from 3.5 to 4.0 - data store?

  Hello

  In the Update Wizard utility host, after the precheck, I choose a VMFS Datastore for storing my console service! http://communities.VMware.com/docs/ !! But I only see my VMFS shared SAN datastore. I think that it is not a good idea to install the service on SAN VMFS Datastore console.

  Have an idea or an explanation?

  Tom

  Hello.

  It is possible, make sure just that storage that houses the supreme court is zoned for only this single ESX host.

  "The service console must be installed on a VMFS datastore that resides on the local host drive or on a drive of SAN which is masked and zoned on that particular host only. The data store cannot be shared between hosts. "--p. 41 of the ESX and vCenter Server Installation Guide.

  Good luck!

• Add all the storages of data presented to the host, the virtual computer's registry

  Hello

  I'm sure that it was done already - perhaps someone has a useful script that they could share?

  I have a few instant volumes presented to an ESXi host, I want a script that will automatically appoint those and add them to the host. It could be a volume - it's maybe ten. I understand the mapping of storage to the host OK unit, but I have a problem with VMware. There is a chance that these data stores could be seen by the original host - so I have to will them.

  Once data warehouses are mounted, I want to find two machines in data warehouses and enter them in vCenter.

  Someone at - it something that they could share?

  Thank you very much!

  Do you get any error messages?

  It does not work?

  Valuable clues, sometimes it is the newspaper of vpxd.

• Orphan data store

  Howdy! We have a very minor problem with the removal of a data store ancient and inaccessible. The pleasure is gone, it appears same for one of our admins. It was a local storage on one of our 3 old hosts. Since then, we have moved to a SAN implementation with 4 new hosts. The data store is as inaccessible, which makes sense since the host used store is no longer in production.

  Disassemble is greyed out, and there is no host associated with the Bank. There is an old VM that has since been moved to a new SAN data stores. I double checked by starting a migration of data store = > advanced on the virtual machine and verified that the files of the virtual machine are not pointing to the old store.

  I have two questions. One, how in the world I have remove this entry in my list of data warehouses. Two, why would he appear for me and another admin, but not the 3rd admin?

  
  Thank you
  Brenden

  I have it! I had to delete the associated virtual machine to inventory and re-register again.

• Windows Server 2008 R2 NFS mounted data store is read only

  I've done this dozens of times in the past, but not with this exact combination successfully:

  ESX4 U1

  Windows 2008 R2 Server Datacenter edition

  NFS Server installed. TCP Version 3.

  The normal configuration that worked in the past:

  NTFS security - total control on ANONYMOUS logon, everyone control total

  The local policies, network access: Let Everyone permissions apply to anonymous users (applied automatically by Windows)

  NFS Sharing - ANSI encoding, allow anonymous access - UID = - 2, GID = - 2

  NFS share permissions - allow all THE MACHINES read-write, ROOT access

  The data store adds OK and appears in the list of data on vClient stores and can be viewed or directly via a Console logon.

  The problem is that the data store is read only! Nothing from ESX can write, delete, or update a folder or a file on the data store. Access Windows NTFS is very well.

  This means also you cannot boot from say a CD ISO on the data store, or create a VMDK guest virtual computer on the data store.

  Given that I had zero problems with this in the past, when with the help of ESX3 or ESX4 connect to Windows Server 2003R2 or several NAS with NFS devices supported I think Windows 2008R2?

  Has anyone seen anything like this before?

  I use it currently; It works fine, but it's the way that you configure the windows nfs export without having to use a mapping service (see images)

  Also, be aware that Windows System Cache is a bit less efficient than linux (but that's ok) you just need to add additional RAM at least 16 GB for the data store busy.

  I also recommend refining delays in setting up nfs for each virtual machine host:

  NFS. HeartbeatFrequency = 10

  NFS. HeartbeatFailures = 5

  And on windows change the properties of the NFS server in the locking tab

  customer collection lock wait 5

• Allocation of automated data store

  I am trying to determine if there is an automated method to invoke the discovery of a NFS or SAN data store.  Ideally, it would be a CLI or command scriptable which could be run to pick up a new volume, create a VMFS file system and assign a name to the data store.    No idea if something like that exists, or if all data storage must be allocated to the hand?

  Yep, you definitely can automate this process with the vSphere API, just present your LUN that it's FC/iSCSI or NFS and take action appropriate depending on the type of storage you are presented.

  Here are some of the useful methods that can be useful when you try to automate this process:

  RescanAllHba

  QueryAvailableDisksForVmfs

  CreateVmfsDatastore

  CreateNasDatastore

  You also want to carefully go over the document SDK: Getting Started with vSphere SDK - Update for SDK 4.1 release if you are new to VMware API/SDK and you can post in the developer community if you have any other questions.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  150 VMware developer

  If you find this information useful, please give points to "correct" or "useful".

• Error during activation of data store single heartbeat

  Hello

  I have a cluster HA (5.5) newly created using vSAN as a data store unique. HA cluster is configured with das.ignoreInsufficientHbDatastore, but when I select vSAN datastore in the favorite heartbeat datastore, I get the following error:

  The userHeartbeatDs setting is not valid for the cluster NOMCLUSTER

  Google could not find a single post/page mentioning this error.

  Any help would be much appreciated!

  Perhaps this explains - it.

  VSAN part 9 - host failure scenarios & amp; vSphere HA Interop | CormacHogan.com

  Another notable difference with vSphere HA on VSAN, it's that the VSAN data store cannot be used for the heartbeat of data store. ...

  I guess that this is due to the local VMFS-L version used with VSAN that does not use the same locking mechanism as a VMFS default data store.

  André