Un'aiutino by scelta raid by a data store...

Similar Questions

• ESXI & HP VSA data store size

  Is - well configured?

  I have 2 hosts HP DL360P VMware 5.5 with 2 500 GB hard drives with hardware raid 1. iSCSI data store configured with 690 GB of disk space in vSphere. 2 HP VSA is appearing 350GB of storage available. The HP CMC shows 690 GB of available disk space. When I install the volume, RAID10, and available disk space as thick, it shows a maximum of 347GB - because of RAID10 storage space.

  My concern is the gap in the amount of available storage space depending on whether display you the data in vSphere (690 GB datastore) store and the CMC showing only 347 GB of usable storage space. So in vSphere it will probably lead someone to believe that there are more storage available there are currently available on the volume.

  Is something wrong with that or should it?

  Mystery solved, someone has decreased the size of the volume in the CMC, which explains the difference in size.

• Replacement of a data store - migration of virtual machines

  We have a VMware ESXi 4.0 installed on a SD card and our data store is on a dedicated internal RAID array. Our data store is running out of space... what we would do is remove the old hard drives and add new - therefore, delete and re-create the matrix RAID and the data store.

  What is the best way to migrate our existing data store / VMs from the old array to a new one using vSphere or vSphere CLI? How we then re - associate VMs on the SD card with the new data store? Advice would be appreciated. Thank you very much.

  Hello

  Looks like it's a single ESXi host.

  You will need to copy/save all the contents of the data store existing to another location (external HARD drive) while all virtual machines are closed.

  Once it's done and you are sure that the copied data are intact, you can:

  -remove all virtual machines of the inventory

  -remove the data store

  -Stop the host

  -replace the HARD drive with the new

  -Launch the host and to reconfigure the new raid

  -Create the new data store in ESXi

  Copy/restore all data to the new data store

  -Browse the data store and add all the virtual machines to the inventory (create a list to make sure you get all the)

  -Start the virtual machines

  May be a good time to do an upgrade of ESXi5 as well

  Please allow points to useful/correct answers

• 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.

• After a failed raid array recovery my data store is missing

  Hi all

  I'm under ESXi at home, but I have a problem with that I need help

  First of all, let me start with the specs:

  ESXI: 5.1.0,799733

  RAID Controller: Adaptec 6805 (driver of the community with the support)

  Configuration of RAID: RAID 5 12,71 TB of disk

  I had some problems with my RAID controller which I solved it using the Adaptec article: a table failed can be recovered? I ended up drop the table and re-create it.

  The RAID array is now in OPTIMUM condition, so I started ESXi and connected using vSphere to find all my virtual machines as unknown (Inaccessible).

  I started googling and found some information, but nothing so far to solve this problem.

  I tried info from these links:

  - Problems after RAID5 which are now resolved, I am not able to mount VMFS

  - VMware KB: Re-create a missing partition of VMFS datastore in VMware vSphere 5.0/5.1/5.5

  ~ # df k

  1 k-blocks used available use % mounted on file system

  VMFS-5 483131392 319600640 163530752 /vmfs/volumes/500 GB 66%

  vfat 4192960 141952 4051008 3% / vmfs/volumes/51f45583-c7047877-9ff7-0015178fcc59

  vfat 255716 138872 116844 54% / vmfs/volumes/55f80475-edb62e49-366c-1f1975e107c2

  vfat 255716 135420 120296 53% / vmfs/volumes/8367f77f-57cb0e3e - 888-b-046f29890a95

  vfat 292688 206792 85896 71% / vmfs/volumes/51f4556a-e6c74124 - 5A 63-0015178fcc59

  ~ # fdisk-l

  ***

  The fdisk command is deprecated: fdisk does not support GPT partitions.  Thank you for using partedUtil

  ***

  Disk/dev/disks/t10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000: 500,1 GB, 500107862016 bytes

  255 heads, 63 sectors/track, 60801 cylinders

  Units = cylinders of 16065 * 512 = 8225280 bytes

  Device boot start end blocks Id system

  / dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p1 1 115 917504 5 extended

  Partition 1 does not stop the limit of cylinder

  / dev/Disks/T10. 115 637 4193280 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p2

  Partition 2 will not stop the limit of cylinder

  / dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p3 637 60802 483271704 fb VMFS

  / dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p4 * 1 1 4080 4 FAT16 < 32M

  Partition 4 does not stop the limit of cylinder

  / dev/Disks/T10. 1 33 255984 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p5

  / dev/Disks/T10. 33 65 255984 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p6

  / dev/Disks/T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p7 65 79 112624 VMKcore fc

  / dev/Disks/T10. 79 115 292848 6 FAT16 ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000p8

  Partition table entries are not in the order of disc

  Fdisk: device has more than 2 ^ 32 sectors, each of them is unusable

  Found valid GPT with protective MBR; using GPT

  Disk /dev/disks/mpx.vmhba1:C0:T0:L0: 4294967295 sectors, 4095 M

  Logical sector size: 512

  Identifier (GUID) of disc: 0652d5d8-10f3-4264-9d35-1e12b2d23b76

  Partition table contains up to 128 entries

  First usable sector is 34, last usable area is 27304898526

  Starting number (sector) end (sector), Code name of size

  1 2048 27304898526 25.4 G 0700

  ~ # esxcfg - volume - l

  < no results >

  # ls/vmfs/devices/drives.

  MPX.vmhba1:C0:t0:l0 vml.0100000000343130313131435043353336363200000000000053414d53554e

  MPX.vmhba1:C0:t0:l0:1 vml.0100000000343130313131435043353336363200000000000053414d53554e:1

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000 vml.0100000000343130313131435043353336363200000000000053414d53554e:2

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:1 vml.0100000000343130313131435043353336363200000000000053414d53554e:3

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:2 vml.0100000000343130313131435043353336363200000000000053414d53554e:4

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:3 vml.0100000000343130313131435043353336363200000000000053414d53554e:5

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:4 vml.0100000000343130313131435043353336363200000000000053414d53554e:6

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:5 vml.0100000000343130313131435043353336363200000000000053414d53554e:7

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:6 vml.0100000000343130313131435043353336363200000000000053414d53554e:8

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:7 vml.01000000003630356634396164524149443520

  T10. ATA___SAMSUNG_HD501LJ___410111CPC53662000000000000:8 vml.01000000003630356634396164524149443520:1

  # partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

  TPG

  1699651 255 63 27304898560

  1 2048 27304898526 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  [EDIT] I have not noticed before that the mpx.vmhba had an additional entry in/vmfs/devices/disks

  # partedUtil getptbl /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:1

  unknown

  1699651 255 63 27304896479

  I have attached vmkernel.log

  I hope someone can point me in the right direction, I have a backup of my criticism/personal data, but it would be nice to recover the rest as well...

  Thanks in advance for the help!

  Post edited by: Sebastiaan Grob adding info on /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0:1

  Running orders more:

  ~ # esxcli instant vmfs storage list

  51f4625a-6482a0da-c112-0015178fcc59

  Volume name: Adaptec RAID 1

  VMFS UUID: 51f4625a-6482a0da-c112-0015178fcc59

  Can mount: true

  Reason of mountability-United Nations:

  Can will: true

  Reason for non-resignaturability:

  County of measure pending: 1

  Then I tried add the option of storage as described in the present (KB VMware: vSphere management LUNS identified as LUN snapshot ) KB article and my data store is back, no loss!

• ESXi 4.1 with 2.7 to RAID server only has a 750 GB data store

  I have a server ESXi 4.1 Build 260247. It has a controller Adaptec 5805Z with 2.7 TB RAID6 material. The ESXi is installed and running on a USB key. The server runs a lot and don't have any problem with the performance, but what I failed to note (after the creation and configuration of the 7 servers for an Exchange 2010 lab) is that the datatstore1 is only 740,75 GB. I looked everywhere in vSphere and online on how to access the rest of this storage. Under configuration > hardware > storage it shows the 'Adaptec disk Local (mpx.vmhba2:C0:T0:L0)", type = parallel SCSI disk to Transport, 2.73 Capasity TB.

  How can I access the additional storage on the disk? I certainly don't want to have to reinstall the LAB if I have to. Attempts to increase its size in the properties of the data store has failed. No error, that he just does nothing nothing found...

  

  

  Creating logical volumes on the RAID is a feature or function of the RAID controller, respectively the RAID controller software. Most RAID controllers authorize splitting of the RAID (unless it's a RAID level 0 x) in several logical volumes. You will need to check this for your RAID controller.

  You should probably migrate VMS off the coast of the current data of 750Go store and delete data store. Then, remove the current volume of 2.75 to logical and create a new logical volumes - maximum 2 TB - 512 bytes by using the controller BIOS or software RAID.

  André

• Error in creating data store Local VMFS 2.3 TB RAID - 5

  Hi all

  I just reinstalled my ESXi 4.0u1, the local disk is configured as 6 x 500 GB SATA RAID - 5 altogether, it gives me 2.3 TB of disk capacity

  However, when I am about to create VMFS Local data store on the ESXi server it was fll of error as the following attached photos:

  can someone help me please in reconfiguring the VMFS 2 TB and 300 GB each?

  Thank you.

  Kind regards

  AWT

  Maximum size of the LUN is a little less than 2 TB.  Re-create the matrix, with two LUNS that is two 1.15 TB, both RAID-5.  Create a data store on the first, then add the second as a measure.

  Please give points for any helpful answer.

• ESXi data store on virtual drive

  Client a BE7K servers (M4 UCS C-240), it came pre-installed with ESXi 5.5 and 4 virtual drives, each virtual drive is configured with RAID 5. Now, we need to install a UC application that requires RAID 10. We use not one of the data store for any guest operating system so our plan is to remove this DS and respective Virtual Drive, break this RAID and rebuild than RAID 10 is here the challenge how can we identify which Datastore, mapped with which virtual drive? My understanding is that ESXi does not map 1-1 (IE VD0 = DS1). If anyone can shed some light on to identify what would be really appreciated.

  Thank you.. !

  I hope it's a little more concise:

  Take the exit of

  ~ # esxcfg-scsidevs - m

  NAA.678da6e715d760101f0aa4a61d982f63:1/vmfs/devices/disks/naa. 678da6e715d760101f0aa4a61d982f63: 1 5777f3b3-7bd4c97a-4ba0-a0369f9400b4 0 datastore4

  Then this match with the release of the list of esxcli storage base path:

  Unknown.vmhba1 - unknown.2:2 -naa.678da6e715d760101f0aa4a61d982f63

  UID: unknown.vmhba1 - unknown.2:2 - naa.678da6e715d760101f0aa4a61d982f63

  The Runtime name: vmhba1:C2:T2: L0

  Feature: naa.678da6e715d760101f0aa4a61d982f63

  Full device name: Cisco's Local disk (naa.678da6e715d760101f0aa4a61d982f63)

  Adapter: vmhba1

  Channels: 2

  Target: 2

  LUN: 0

  ... snip

  This must match your 3rd VD, since the target and VD #s start with 0.

  It confirmed in the laboratory: see below

  vd_order_1.jpg

  

  VD0 (1 virtual drive created) corresponds to T0... and VD3 corresponds to T3.

  These figures are of course unique to each hba/controller if you want to ensure the vhba # and controller # (vmhba1 and C2 in my example) come from the device even when they match.

  Kirk...

• Please help: measure is missing from the data store

  Hello

  I have an a 20 TB drive data store and a magnitude of about 40 TB (local disks, areca raid controller).

  Long story short, I had to delete and re-create the volume 40 to on the RAID controller (without initialization, of course).

  Now all the data is there but eui has changed for the 40 to volume and vmware is unable to mount.

  log/hostd.log:2016-05-10T07:17:16.107Z of information pass [3D380B70] [Originator@6876 sub = Vimsvc.ha - eventmgr] event 118: a connected device eui.001b4d2051676528:1 may be offline. [Backvol1, 55e980d4-386dfa7f-7cb2-0cc47a09ba36] file system now is in a degraded state. While the data store is always available, parts of data residing on the extent which went offline may be inaccessible.

  [root@esxi2:/vmfs/volumes/55e980d4-386dfa7f-7cb2-0cc47a09ba36]

  esxcli instant vmfs storage list

  Volume name:

  VMFS UUID:

  Can mount: false

  UN-mountability reason: a few missing extensions

  Can will: false

  Reason for non-resignaturability: some missing extensions

  County of measure pending: 1

  Can someone help me please?

  Thank you!

  Hello
  You asked for instructions on how to readd a missing measure.
  Basically, it's pretty easy:
  in the VMFS to VMFS-based volume header section, you can assign extends it.
  Lets say that the basic volume is mpx.vmhba1:C0:T3:L0:1
  first of all extend is mpx.vmhba1:C0:T4:L0:1
  second extension is mpx.vmhba1:C0:T5:L0:1
  Then you will see this string in the VMFS header:
  vmhba1:3:0
  and a little later

  MPX.vmhba1:C0:T3:l0:1

  MPX.vmhba1:C0:T4:l0:1

  MPX.vmhba1:C0:T5:l0:1
  Just change the list of stretches.
  But: normally you can't change this section at all, and to add to the confusion, these values are stored in RAM is not trivial to change this value correctly.
  I highly recommend that instead of try it yourself and repeat all the mistakes I made while learning it - call me.
  I rather help you personally to give dangerous advice that will probably make things worse.

• ESXi 5.5 only 4 TB usable for the data store

  Hi all

  Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

  Configuration:

  -HP Proliant Microserver N40L

  -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

  -4 x 2 TB as a Raid5

  HP-ESXi - 5.5.0 - iso - 5.72 A

  I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

  But I could not understand the problem.

  The P410 controller shows 5.5 TB:

  ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

  Smart Array P410 in slot 1 (sn: PACCRID110510NR)

  Array A (SATA, used space: 0 MB)

  logicaldrive 1 (5.5 TB, RAID 5, OK)

  then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

  then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

  then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

  then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

  MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

  ESXi obviously knows the same size:

  ~ # Esxcli storage core devices list

  NAA.600508b1001ca5e68adc0bc4bc508d6e

  Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

  Definable display name: true

     Size: 5723091

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

  Vendor: HP

  Model: VOLUME LOGIC

  Review: 3.66

  SCSI level: 5

  (etc.)

  But does that 4 TB:

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

  vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

  vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

  vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

  I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

  Thanks for your help.

  DC

  Your output, it shows that there are two partitions vmfs

  3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

  I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

• Expand the Local data store

  Hello

  I have an ESX 4.1 with only a data store local (RAID5) on virtual machines on a DELL Server

  I want to enlarge the data store, I don't have enough free space to create multiple virtual machines.

  To do:

  -Install a new hard drive (with vmware powered)

  -Add the new hardisk to Raid5 with DELL Open manage

  -wait finally extend raid 5

  -Power Off Vmware machines?  or continue started?

  -Develop with local Vshpere the data store vmware (what time must expand?)

  I want to know if I can do an extension with the new space unpartitioned on local existing datastore without losing my virtual machines? I have only the local data store with esxi when I develop the esxi continue to work?

  Can someone help me?

  Concerning

  Yes, it's quite OK.

  If this solved your problem, please mark it as answered.

  See you soon,.

  Adil Arif

• Data store is not mounted automatically after updating the Firmware of the LSI

  I've recently updated the card RAID LSI firmware on my ESXi 5.5 system (patched and update top of page)

  When I rebooted, took place the following:

  1. the associated VMFS volume RAID was mounted

  2. the data on the volume store was not mounted

  I mounted the data store manually and restarted my VMs

  Do I have to re-signing the Volume and/or the data store to raise it properly.

  Steve

  The command should be ok and do the same thing as the command esxcli esxcli storage vmfs snapshot mount -l label|-u uuid (for details, see http://kb.vmware.com/kb/1011387).

  André

• Lost access to local data store

  Hi people:

  I have ESXi 6.0 running on an Intel S2600CWTS motherboard using the LSI SAS controller onboard and six readers Samsung 850 Pro SSD in a RAID 5 configuration.  This server is about a month and a half, and it worked fine for the first month, but in the last few weeks I started to do in the case where journal messages saying that ESXi has lost access to the data store, then, most of the time, about 15 seconds later access is restored.   Several times it took more time, which one crashed the server.  On these long, the motherboard Intel event log showed that a player had failed and began a regeneration and once the motherboard has shown that two different drives had failed, and it took both offline originally ESXi crashing.  On it that I was able to bring the two records back online via the RAID bios and everything worked fine again.  I suspect that I have hard disk problems because these discs are new and because different readers have been reported as failed, and also because no data has been lost even if 2 drives went offline at the same time.   I guess I could have a bad controller LSI, or a cable has come loose somewhere, but I expect to happen if it is really the case of data loss.

  I also noticed that lost access messages tend to appear in the log at the moment I start a virtual machine.  At first I thought that it would be one thing to flow, thinking a VM departure did a lot of IO, but this happens immediately, before even the bios of the virtual screen machine disappears, so I don't think that the virtual machine is actually reading the disc again.  In addition, as a precaution, I started the migration of some virtual machines on the server to the old server I still had available, and there is no lost access messages in the event log while that was happening, while about 50 megabytes per second of i/o has reached the disk during transfers.  I put the last patch on ESXi in mid-May, about two weeks before this started, and I begin to suspect that the patch may have something to do with it, because it seems to me that if something is happening between ESXi and the disk controller making hang up or lose interruptions during a short period of time , and I wonder if it goes pretty long if material in the motherboard sensors interpret this as some sort of hardware and simply brand failure according to readers I / O was hooked as bad then.

  Unfortunately I'm out of town now so I wanted more I had to the remote server, lest I do not not get back to the top.  I moved a couple of the most critical virtual machines from the old server which I was remotely start and transfer to virtual machines.  I also noticed that this issue tended to occur more frequently when I got to the top of the VCenter Server apparatus that any other (sometimes to others, but has happened every time I tried to start the device VCenter).  So who was the first that I moved to the old server, but strangely enough there is no error logged when I transferred the files, so the issue is not that ESXi had trouble reading the VMs vmdk file when I started it.

  I also wanted to ask you if there are any vibs for the LSI Megaraid controller on motherboard S2600CWTS I could install that would allow me to access the RAID controller without having to pick up the server and do it from the BIOS configuration screens, similar to how you can access the controller RAID from Dell while ESXi is running via a vib add-on.  So far I have not found one.

  My intention when I go to the server is to run an integrity check against the RAID 5 array via the controller and then use the AIMÉ ESXi utility on the data store to see if something is wrong here.  If not, then I guess I'll rewritten can patch.

  Ideas or suggestions welcome.

  Success!  I finally understood what the problem was corrected.  The problem is the fact that although the last vib driver LSI has been installed, for some reason any it would not automatically replace the default ESXi pilot lsi_mr3.  I did not notice that even though the latest driver package vib properly installed LSI controller was still using the original driver.  This could be considered by a 'esxcfg-scsidev - a' command showed that even "vmhba1 lsi_mr3 link-n/a sas.5001e67ca647e000 (0000:0: 00.0) controller LSI MegaRAID SAS Fury."  The second field after the controller (vmhba1) is the current manager used.  The pilot, which was to be used was: "vmhba1 megaraid_sas link-n/a unknown.vmhba (0000:03:00.0) Avago (LSI / Symbios Logic) Invader MegaRAID SAS controller.

  To fix this I had to disable the lsi_mr3 driver so that ESXi is forced to use it.  The procedure to do is the following:

  (1) make sure you have the new EXSi driver you want to use already installed.  I assume that bad things would happen if you have disabled the only driver who could run your disk controller.  Use this command to view the drivers installed: "esxcli software vib list" and you should get something similar to the following:

  [root@intelserver:~] esxcli list of software of vib

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  MegaRAID SCSI-sas 6.608.11.00 - 1OEM.600.0.0.2494585 Avago VMwareCertified 2015-07-19

  LSI - mr3 6.606.10.00 - 1OEM.550.0.0.1391871 LSI VMwareCertified 2015-06-19

  mtip32xx-native 3.8.5 - 1vmw.600.0.0.2494585 VMWARE VMwareCertified 2015-04-28

  ATA-pata-amd 0.3.10 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-atiixp 0.4.6 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-cmd64x 0.2.5 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-hpt3x2n 0.3.4 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-pdc2027x 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-serverworks 0.4.3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-sil680 0.4.8 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-via 0.3.3 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  block-cciss 3.6.14 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  CPU-microcode 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  EHCI-ehci-hcd 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  elxnet 10.2.309.6v - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Emulex-10.2.309.6v - 0.0.2494585 VMwareCertified-2015-04-28 VMware esx-elxnetcli

  ESX-based 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  ESX-dvfilter-credits-fastpath 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  ESX-tboot 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  6.0.0 - 0.0.2494585 of xserver-ESX VMware VMwareCertified 2015 - 04 - 28

  IMA-qla4xxx 2.02.18 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-devintf 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-paremeter 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-TR-drv 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LPFC 10.2.309.8 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSI-msgpt3 06.255.12.00 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-hp-hpsa-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-lsi-mr3-plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-lsi-msgpt3-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU lsi megaraid sas plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-mpt2sas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-mptsas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Misc-cnic-register 1.78.75.v60.7 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Misc-pilots 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  NET-bnx2 2.2.4f.v60.10 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-bnx2x 1.78.80.v60.12 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-cnic 1.78.76.v60.13 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000 8.0.3.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000e 2.5.4 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-enic 2.1.2.38 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-forcedeth 0, 61 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-igb 5.0.5.1.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NET-IGB 3.7.13.7.14iov - 20vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-core 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-en 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-nx-nic 5.0.621 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-tg3 3.131d.v60.4 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-vmxnet3 1.1.3.0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  nmlx4-core 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-en 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-rdma 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nVMe 1.0e.0.35 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  OHCI-usb-ohci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  qlnativefc 2.0.12.0 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  REST 2.0.2.0088 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Ahci SATA 3, 0 - 21vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  ATA-SATA-piix 2: 12 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NV-sata-SATA 3, 5 - 4vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  SATA-sata-promise 2: 12 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil24 1, 1 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil 2, 3 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-svw 2, 3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-aacraid 1.1.5.1 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-adp94xx 1.0.8.12 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-3, 1 - aic79xx 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2fc 1.78.78.v60.8 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2i 2.78.76.v60.8 - 1vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  SCSI-DNI 1.5.0.45 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-hpsa 6.0.0.44 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-ips 7.12.05 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid-mbox 2.20.5.1 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid2 2.00.4 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mpt2sas 19.00.00.00 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptsas 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptspi 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-qla4xxx 5.01.03.2 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  UHCI-usb-uhci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  VMware-esx-dvfilter-maclearn-1, 00 1.00 VMware VMwareCertified 2015-05-12

  xHCI-xhci 1, 0 - 2vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Tools-light 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  [root@intelserver:~

  Verify that the scsi-megaraid-sas driver is installed before proceeding.

  (2) to disable the lsi_mr3 driver do the following: "esxcli set of module system - enabled = false - module = lsi_mr3 '

  (3) reboot

  After restarting, do: "esxcfg-scsidev - a" to check megaraid_sas driver is assigned to your disk controller.

  I don't know how ESXi decided to prioritize if two or more drivers are applicable to a single hardware device, or if the installation of the new driver LSI process is supposed to disable or remove default lsi_mr3 driver and simply failed to do so.  Also, I don't know what's going to happen when I put on the next patch of ESXi, specially if the lsi_mr3 driver will be once more the priority.  If anyone knows how the driver installation process is supposed to work in this situation, please let me know.  I am so happy that I finally got this problem because the server has been seriously covered with the data store become unaccessable for 5 to 10 seconds every time a VM started or stopped, and the former driver at least once done something bad enough to deceive the controller into thinking that one of the disks has went wrong and began a RAID Resync.

• Disc SSD data store unavailable after reboot

  I have a Kingston SSD drive installed in a Dell T620 SAS (Controller H710) basket bottom. It is configured RAID 0 (disk). Therefore, it is OK, and I created a data store using the full disc. It works very well in the virtual machine that it is assigned to you. However, when I reboot and look in the configuration of the storage is not there. I can add and it remembers. The bad news is that the virtual machine, it is affected to cannot start as long as I add back in manually.

  A look at the list of devices, it shows that mounted. The difference between it and other readers is it says unknown partition format, it also says non - ssd.

  I'm just against a unit of failure in charge here? I do not see the SSD drives listed in the list of supported devices, but I hardly find this page.

  < small mug shot >

  Why he let me a second hard drive configured to use the rest of a store of data and then not start because there is not enough room for the Swap and not remove the second disk hard when I tell him?

  < / small rant >

  Hi Lou

  Why do not connect you to a port SATA (my last one)?

  This seems to fix. Also, he appeared as an SSD and remembered all the stuff.

  I guess it has to do with the SAS/RAID connection. Will try another drive to be sure.

  Lou

• Migration of virtual machines from a data store, and then delete the data store?

  Hello

  I have a future deployment this month and my Director wants to build a new RAID 6 array, create a store of data with the new table and then move all the VMS to the newly created data store.

  Then he asked me to take the old data store and remove it and the available space between the deleted data store and other stores of data in our shared environment. The question is when the new raid is created and vm has migrated to the new data store, which is the best way to remove the data store empty and make sure that the space available for other data stores? Any help would be appreciated...

  Greg ~.

  If all controls are met, you can go ahead and take it apart without any problem.

  I have re-iterate below checks:

  -No virtual machine is in the data store

  -The data store is not part of the cluster data store

  -The data store is not managed by the DRS storage

  -IGCS is disabled for this data store

  -The data store is not used for vSphere HA heartbeat.

  Especially highlighted 2 controls. Please note that SIOC can be enabled on the data without SDR photo store