Disc SSD data store unavailable after reboot

Similar Questions

• Performance of SSD data store

  I'd like to get some info on whether or not there are specific settings ESXi for best performance of VMs, sitting on a SSD data store.

  Configuration of the laboratory:

  LSI 9260-8i RAID card

  8 x 500 GB Samsung 830 SSDs (TLC, terrible I know), RAID5 (Yes, I must have parity protection)

  I've constantly tweaked the 9260 and RAID settings to achieve the best possible configuration according to my bearings: 128 KB stripe size, direct IO, reading ahead, disk cache enabled, rewrite with BBU...

  I see that a fairly large performance hit comparison performance native RAID performance vs windows in ESXi when I transplant the same RAID card/SSD in my lab and test ESXi host from inside a virtual machine.  Understood, it is fresh generals of the hypervisor and then overload the virtual machine... but still...

  Looking for someone who has experience with a similar configuration and can provide suggestions/settings...

  Thanks in advance!

  You have option FastPath? This will significantly improve i/o for SSD performance.

  I would also create RAID-50 for the SSD 8.

• Data store missing after the reconstruction of the raid array

  One of the players in my raid array has failed a few days ago.

  I had a spare drive in the table so the controller immediately began the process of rebuilding and all servers were running throughout.

  When the reconstruction has been completed (I checked this via the user interface of raid array and the newspaper), I had to stop the server to remove disc defective (not replaceable chassis hot) and when I restarted the server, the data on the raid array store isn't there anymore.  I also checked through the raid controller interface that I removed the (defective) drive and that the table was always in a ready state when he came.

  In vsphere client, when I click on the storage... Add link, the server sees the material but if I click then it tells me that it will be re - format the volume.  See attachment.  I have most certainly does not take the next step and reformat.  Simply, I took the screenshot and regularized.

  I found these instructions, but they are for an older version of ESXi and am unsure if they are correct for ESXi 6.0.0 338124

  VMware KB: Lack of data store after the reconstruction of the RAID disk/LUN

  Here are the steps I should follow?

  If these aren't the right instructions can you tell me the version which is for ESXi 6.0.0 338124 that I couldn't find anything either.

  Thank you

  Hi ThompsG,

  Yes, there are two data stores for the virtual machine located on the RAID array.  The virtual machine itself was stored in a different data store that was not in the raid array.

  I spent about 48 hours last week, including this morning, trying to coax ESXi recognizing volumes, with no luck.  Finally, I gave up and I removed the virtual computer hard drives that were on the corrupt data store.  Then the virtual machine came without problem.

  Finally, since I have everything on these 2 volumes backed up to a cloud provider, I have recreated the two data stores in the raid array and began the restoration process. It is currently running and has about 16 days left to go.

• Data store lost after SAN restart / modify LVM. EnableResignature

  Hi all

  We just had a blackout (planned) and once we have start the SAN and the ESX, one of the LUN seems to have disappeared. I tried to anyone she / it presents another ESX, it seemed that the server did not recognize that it was formatted in vmfs. He would see only as a new partition and asked to formatted it again. After several hours of research and testing, I was able to get my store of data by changing the value of LVM. EnableResignature to 1. Rescan HBAS and he was there like an old snag-00000002-DataStore name... From there a creation of computer virtual and added new disc, from the existing drive and pointed at my old vmdk files. I have no idea of the will what exactly is and if I can set it to 0 (or I'll lose all my vm once again) and why a data store had this problem?

  Any idea?

  That's right, don't let not the will option is enabled.
  This event does not occur very often.

  http://blog.laspina.ca/

• Data store renamed after failover

  Hello

  I use vSphere U2 with SRM 5.0 5.0.  Storage is a synchronous of NetApp V3210 at FAS2240-4.

  I did a cover of the SRM and I found that the data store in vCenter was renamed snap-xxxx-datastore_name.  Why the data store has been renamed?  Can I prevent SRM to rename the data store?  Is it possible to get the data store named return to what it was originally?  If so, how can I do it?

  Thank you

  Frank

  This is the default behavior of MRS, and yes it can be changed.  Page 89 of the Administrator's guide.

  Keep the SRM of renaming of the warehouses of data recovery | virtual insanity

  http://www.VMware.com/PDF/srm_admin_5_0.PDF

• ASM disk unavailable after reboot

  Hello!
  
  We have three discs in oracle asm CRS1, FRAVOL1 and RACDB1. Sometimes after restarting the server, the drives are not available. Allows you to redo the reboot and the drive appears. For example
  
  orcl0: ~ # oracleasm listdisks
  FRAVOL1
  RACDB1
  
  -restart
  
  orcl0: ~ # oracleasm listdisks
  CRS1
  FRAVOL1
  RACDB1
  
  
  Should what log files I check to see the error message? How to solve this problem, do you have any suggestions?
  
  Thank you.

  Use ORACLEASM_SCANORDER = "map".

  It should work.

  Concerning
  http://www.oracleracexpert.com
  Install the ASM lib in 10g
  http://www.oracleracexpert.com/2009/08/install-and-configure-asmlib-in-10G.html
  createdisk, deletedisk, and querydisk in ASM
  http://www.oracleracexpert.com/2009/09/createdisk-deletedisk-and-querydisk-in.html

• Increase in size of data store ESXi after increasing the size of the LUN

  Hi all

  Scenario is as follows.

  Remote site with Dell r710 ESXi 4.1 servers 2, 1 Dell MD3200i SAN with 12 600 GB drives.

  Initially when I implemented the San, I created 2 LUNS with 1 TB in each LUN.

  Now, we ran into a situation where we have 1 server which is now need more than 1 TB of sapce on it.

  I've reconfigured the table and now have a unit number logic that I spent in 2 TB to 1 TB and I now need to increase the store of data on the ESX Server.

  If I increase the size he reformatted the LUN whole or just the free space that I create?

  I don't want to remove any exisitng s VM on the SAN.

  maximum size of a vmfs is 2 TB-512 b only. extend wouldn't format the LUNS. Look at this blog: http://www.yellow-bricks.com/2009/03/26/resizing-your-vmfs-the-right-way-exploring-the-next-version-of-esxvcenter/

• VM shows always refers to the old data store after storage vMotion?

  All the:

  We have recently set up a SAN Equalogic and plugged into our environment vSphere. We are moving our VM to SAN storage, off the coast of local disk. After treatment of a virtual machine, we always show the reference to the old data store on the summary page when you look at this VM. However, when we look at the settings, HARD drive shows that the vmdk file is infact on the SAN?

  Is there a reason why it would still showing upward for both?

  Thank you

  (1) check if the virtual machine has snapshots and maybe its pointing to the old datatore

  (2) check if any ISO is mounted on the virtual machine to the old data store

  After the screenshot of the VM folder by browsing the old data store

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Add the new data store

  Hello

  I'm sorry if someone already asked this question before.

  I'm just starting with VMWARE.

  my main at work gave me an old DELL Poweredge 2950 and asked me to install esxi 5 and set up a network and separate area to work with.

  This server got a limitation of 400 GB of HARD drive. I want to use the external USB HDD as additional storage. I got the rank of server 2 TB external HARD drive to use.

  in the start-up phase, is to recognize the HARD drive, but when I want to add as a data store, it does not show anything.

  is there a way I can use the HARD disc as data store extra or not. If I can, can someone please help me with this.

  Thank you

  Krishna

  Unless this HARD drive can be connected to a supported interface card you won't have much luck. You don't mention the interface - if "Server Grade" arrives as meaning 'external SAS port to support RAID card' then it should 'work '.

  From what you describe, I'm imagining a USB - this is not taken care of for a data store.

• data store is not accessible vsphere 4.0

  data store unavailable on vsphere 4.0... We have a server with connection zFCP on hitachi ams2100 datastore and have 2 LUNs connected 4 days ago, I try to restart my host. and all of a sudden one of my lun is not accessible, I already try to Reanalyze the data store. and nothing happens, I always get the error data store can not accessible. any body can help me please...

  is this LUN presented on othe so hosts? If so, then remove the host in question and add it again

  to do a new analysis...

• Question about the replica data store

  I am set up a plan view and I can't find anything on the lines how much I should put on a data store. We have a pretty small environment with approximately 120 related clones.

  Can I create pools of 5 to 10 for all use the same data replica store? I don't want to have all these little datastore who chew on the SAN iSCSI connections. It would be easier to have a data store that is easy to move all replicas.

  Thank you.

  Yes, you can store several replicas to a data store.  It is often considered to be best practices in order to unload the aftershocks of a SSD data store.    I just would make sure that the data store can handle IO reading for all replicas.

• Storage Vmotion to a new data store get UUID and MAC change to hot after reboot

  Hello

  I have a strange thing that happened on my vcenter.

  Just do a vmotion hot storage between two data store.

  I reboot the virtual machine and received no message to validate if I moved or copied.

  When the virtual machine is restarted, I see that changing the UUID and MAC address.
  Make me an error with an application running on it.

  Did anyone see that already?

  We do some testing and solution for this problem is to download the VM's vmx file on the local system and apply these settings:

  If you want to change the setting always or always create , power off the virtual machine and change its configuration (.vmx) file. Remove the line containing uuid.action = "crΘer" or uuid.action = 'keep'.

  The configuration line such as this to keep the UUID and MAC after vmotion: uuid.action = 'keep '.

  Reupload the file on the data store and restart the virtual machine

• ESXi host sees no data store after the reboot

  Hi all

  I'm new to the community and ESXi itself.  Everything has been working great until today when I rebooted my host.

  I installed it on a Dell T110 server, we had in the back for testing.  It has a 250 GB HARD drive installed in the case.  ESXi installed fine and I had 220 GB or more storage at my disposal.  Multiple VM installed, and once again, everything seems to work properly.

  Today, I wanted to activate usb passthrough for a Server 2008 VM I installed it, I went through the process and had to reboot the host at the end.

  After the restart, he seems to have forgotten the HARD disk that is installed and is no longer, I see my store data or virtual machine access I had running.

  There are a couple screenshots attachedthat screen what I see.

  Thanks for any help or advice!

  Is this the same controller that is attached to the 250 GB HARD drive? Passing the controller to the virtual computer may have unpresented it host, then you won't be able to access and to store configuration settings. Since this is a test system you can consider / try to run "Reset System Configuration" from the DCUI. If this does not work, you may need to reinstall ESXi of CD (the VMFS retaining of course data store).

  André

• ESXI 5.1 "the disc is not thin-provisioned" after copying to the new data store vmdk

  I wanted to create an external backup as a 2nd VM ready-to-run on the 2nd data store.

  I've removed all snapshots, stop the machine virtual and exported the OVF file to a computer, adjusted to the size of the original virtual machine starts in Gparted to update the partition and restart. All very well.

  I then tried to deploy the OVF in the data store alternative (235GB slim, thickness according to the deployment of 250 Wizard). I tried both thick and thin but the error message "cannot deploy the OVF. The operation was cancelled by the user.

  I then manually downloaded the VMDK & OVF file to the 2nd data store and tried to inflate but then received the message "a specified parameter was not correct. The disc isn't thin provisioned. ».

  It seems I have dealing with the same thing, as this is the document here (http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3-release-notes.html).  However, I have no idea what to do now... and I'm worried because it seems that my backup plan may not work if I can't restore an OVF/VMDK from a disk of visas.

  The solution to the first problem here: https://communities.vmware.com/message/2172950#2172950 that solved my problem 2nd too.