Prevent write access to a data store

Similar Questions

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

• Cannot write to a NFS data store

  Hello

  I built a test environment to test ESXi 5.5 u1 to work. I am able to mount the database, browse the data store, but cannot write to it. I mounted on a different host of production and can't read/write very well.

  This happens on both servers in this test configuration. I must add, they used to be the ESX 3.5 hosts and had no problem with NFS data warehouses. I used the same NIC cards to create similar vSwitches. Trunking VLAN on our physical switches has not changed.  The two test servers have access to reading/writing/root for NFS mounting in our SAN (same as before IPs and it worked).

  Any suggestion would be appreciated.

  Thank you

  Well I guess you've got most of the standard things cleared here.

  I fall on this blog:

  http://emcsan.WordPress.com/2011/09/01/VMware-cant-write-to-a-Celerra-RW-NFS-mounted-datastore/

  Which seems to point to a few additional authorization with the EMC Clariion problems that must be addressed to make NFS work in later versions.  This gives a whril on your new hosts and let us know.

• Unable to read / write in the NFS data store

  Hi all
  I'm having a problem with a NFS datastore in Vcenter. I have an NFS share on a Win2k3 server which I am able to mount. However... I can't write him even though the permissions appear to be correct.  This server is connected to an array of training Vault EVA Storage with 2 TB of storage.
  Looks like he's not more as when I try to mount ad content, it shows as 0.00 B ability... and I know that there are files in the NFS data store. Same Host, I can mount my other NFS datastore successfully since a 2008 Server, just do not know which cannot be configured correctly here.

  Help, please... been at this for 2 days banging my head on my desk!

  Screenshots are attached. If there are log files that I could post that would help, please let me know and I'll join them as well.
  Thank you!

  Woot! It worked. I changed the local article, but then authorized security strategy anonymous access with the 2 GID and UID - 2. Once this is done, it is now properly show in Vcenter and allow me to read and write in the data store. Before that I got the value 0.0 even with security policy, change that did not work. So I hope that this issue helps someone in the future, and they do not have a hair pulling experience like I did.

  WHAT A PAIN!

  in any case, thank you all for your time.

• Accessibility of the data store

  I need determine if a given data store is accessed from ESX

  hosts.  I noticed that the MO data store has a property named

  accessible.  However, in my tests, even when I take the data store down

  (it was a test NFS data store and I just close the NFS host), the

  accessible property always return true.

  Does anyone know how to determine when / if a given data store is no longer accessible by an ESX host?

  Thank you very much in advance for your help.

  -Moby

  Did you call UpdsateViewData after you turned off the NFS server?

  $ds = Get-Datastore  | Get-View
  ....
  # NFS server powered off
  $ds.UpdateViewData()
  ....
  

  Note that in PowerCLI 4.1, you have access to the MO via the ExtensionData property.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Windows 2008 Server NFS - permission denied when accessing the NFS data store

  Hello

  I'm trying to configure a Windows 2008 Server to store virtual machines on an NFS share.

  When I add the data store to my host, I have no Brown Read-only and the data store is added successfully.

  When I browse the data store, as soon as I try to delete a file or create a folder, I have an error message: "cannot delete" or "cannot complete the file was created.

  It seems to be a problem of rights NFS, but impossible to find what the problem is.

  In the/var/log/vmkernel, I see:

  Mar 23 17:43:07 vmw-esx1 vmkernel: 1:02:37:20.635 cpu4:4109) NFSLock: 2677: can't get the lock on the file new document texte.txt 0x4100070384d0 on circe (10.254.0.19): Permission denied

  Don't you have a howto use NFS with Windows 2008 to help me?  I found one for Windows 2003, but think are too different.

  Or another idea?

  See document attached with the NFS share parameters.

  Philippe

  You must configure the user name mapping in Services for UNIX/NFS and map the root user.  Detailed instructions here: http://www.sohoadvisers.com/tutorials/vmware-esxi/connect-esxi-to-windows-nfs.  I was able to implement some hosts to use my Windows NFS export, but it was a bit unreliable.  This is a configuration not supported with VMware...

  Josh

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

  Visit http://vmtoday.com for news, views and virtualization how - to of

  Follow me on Twitter - @joshuatownsend

• Multiple ESX servers to access the same data store

  We connect our ESX servers to an Equallogic SAN iSCSI using VMWare iSCSI card.   I have a data store that has ISO files to store.   So far, I can connect only this data to an ESX Server store on time.  I have to disconnect an and connect manually to the other.  We currently have a facility relatively bare bones (don't have vCenter again, grouping, etc.).

  Is there anyway to connect the same data store to multiple ESX servers?  I tried to adjust the volume of Equallogic SAN for read only (since I just need to read ISO files), but I can't connect to ESX servers when I do this.

  Remember that the volume is enabled for clustering.

  From v4.x Equallogic firmware, there is an option advanced on each volume.

  André

• VMware 5.5 Upgrade breaks access the VMFS data store (kind of)

  Now, before I get off, I will say that I am sure that the host I'm doing this on IS NOT on the HCL.

  (why I'm running old hardware?-c' is a community organization that I volunteer for which relies on hardware dontated)

  However, please read on.

  Updated an IBM x 3500 and a x 3650 (same generation - they are basically Tower and rack mount versions of the same kit) to esxi 5.1 to 5.5.

  (Exactly the same problem on both)

  Local storage - IBM Serveraid (aacraid)

  I was a bit confused as the controllers of disk and LUN show always also visible (just no VMFS didn't recognize any time how I rescan).

  (normally the LUNS do not appear due to a driver does not)

  I found that I was able to get future LUNS by practice

  'Add a storage '.

  "Disk/LUN.

  (30-60 seconds then shows the LUNS)

  

  It shows the drive bays, I click Next and select "mount disc and keep the signature '...

  

  The lun then comes fine and everything works.

  However rebooting it gets lost again and I have to repeat the process to get the VMFS volumes to come back.

  Possible entries for the vmkernel.log

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) vmklnx_aacraid bunch of module: creation succeeded. ID = 0x410a640c1000

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) < 6 > Adaptec aacraid driver 1.2.1.30300

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) PCI: driver aacraid seeks devices

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) DMA: 612: DMA engine ' vmklnxpci - 0:3:0.0' created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) DMA: 612: DMA engine ' vmklnxpci - 0:3:0.0' created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:42.308Z cpu2:33418) IRQ: 540: 0x2b < aacraid > shareable, flags 0x10

  (2014 04-22 T 19: 56:42.308Z cpu2:33418) VMK_VECTOR: 218: Manager registered for 0xff2b, 0x10 shared interrupt flags

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: kernel 5.2 - 0 [17003] July 25, 2011

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: monitor 5.2 - 0 [17003]

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: bios 5.2 - 0 [17003]

  aacraid0 < 6 >: serial

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) VMK_PCI: 395: 0000:03:00.0 device name: vmhba1

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) DMA: 612: DMA "vmhba1" engine, created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C0:T0:L0': seller: 'SERVERA' model: Rev "DIS1": "V1.0".

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 979: path "vmhba1:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiUid: 273: "vmhba1:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 1105: path 'vmhba1:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 1503: Add the path: vmhba1:C0:T0:L0

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C0:T1:L0': seller: 'SERVERA' model: Rev "SATA1": "V1.0".

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 979: path "vmhba1:C0:T1:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiUid: 273: "vmhba1:C0:T1:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiScan: 1105: path 'vmhba1:C0:T1:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiScan: 1503: Add the path: vmhba1:C0:T1:L0

  (2014 04-22 T 19: 56:44.018Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T0:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.018Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.020Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T0:L0: not found

  (2014 04-22 T 19: 56:44.021Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T1:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.021Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T1:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.023Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T1:L0: not found

  (2014 04-22 T 19: 56:44.025Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T2:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.025Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T2:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.027Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T2:L0: not found

  (2014 04-22 T 19: 56:44.029Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T3:L0': seller: model "IBM-ESXS": "N VPBA300C3ETS11' Rev:"A496.

  (2014 04-22 T 19: 56:44.029Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T3:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.032Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T3:L0: not found

  (2014 04-22 T 19: 56:44.034Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T4:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.034Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T4:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.039Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T4:L0: not found

  (2014 04-22 T 19: 56:44.041Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T5:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.041Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T5:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.047Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T5:L0: not found

  (2014 04-22 T 19: 56:44.049Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T6:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.049Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T6:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.054Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T6:L0: not found

  (2014 04-22 T 19: 56:44.056Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T7:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A3GA '.

  (2014 04-22 T 19: 56:44.056Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T7:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.061Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T7:L0: not found

  (2014 04-22 T 19: 56:44.844Z cpu3:33418) ScsiScan: 976: path 'vmhba1:C3:T0:L0': seller: "IBM" model: "SAS SES-2 DEVICE" Rev: "1.11'."

  (2014 04-22 T 19: 56:44.844Z cpu3:33418) ScsiScan: 979: path "vmhba1:C3:T0:L0": Type: 0xd, ANSI rev: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.845Z cpu3:33418) ScsiScan: 1503: Add the path: vmhba1:C3:T0:L0

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 976: path 'vmhba1:C3:T1:L0': seller: "IBM" model: "SAS SES-2 DEVICE" Rev: "1.11'."

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 979: path "vmhba1:C3:T1:L0": Type: 0xd, ANSI rev: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 1503: Add the path: vmhba1:C3:T1:L0

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) PCI: driver claimed aacraid device 0000:03:00.0

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) PCI: driver claimed aacraid 1 device

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) ScsiNpiv: 1510: GetInfo for adapter vmhba1, [0x4108991c4400], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) Mod: 4780: aacraid initialization succeeded with module ID 4174.

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) aacraid loaded successfully.

  (2014 04-22 T 19: 57:07.090Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba32:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.090Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba0:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C3:T1:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C3:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiUid: 273: "vmhba1:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C0:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.092Z cpu7:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba1:C0:T0:L0 unit could not detect. Failure of the error.

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba1:C0:T0:L0:1': not supported

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba1:C0:T0:L0" from plugin "NMP" of type 0

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiUid: 273: "vmhba1:C0:T1:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C0:T1:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba1:C0:T1:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba1:C0:T1:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.115Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba1:C0:T1:L0 of the unit could not detect. Failure of the error.

  (2014 04-22 T 19: 57:07.154Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba1:C0:T1:L0:1': not supported

  (2014 04-22 T 19: 57:07.154Z cpu2:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba1:C0:T1:L0" from plugin "NMP" of type 0

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C3:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C3:T0:L0

  0 x 50 0x05 0 x 07 0x6c 0 x 07 0xbf 0xe2 0 x 79 0 x 53 x 0 41 0 x 53 0x20 0 x 53 0 x 45

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "naa.5005076c07bfe279" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "naa.5005076c07bfe279" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe279' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 24 world 0-dev 'naa.5005076c07bfe279' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.187Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.207Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for naa.5005076c07bfe279 of the unit could not detect. Initiator error of storage.

  (2014 04-22 T 19: 57:07.217Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 25 world 0-dev 'naa.5005076c07bfe279' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.253Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 26 0-dev 'naa.5005076c07bfe279' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.289Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x27 0-dev 'naa.5005076c07bfe279' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.317Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.317Z cpu2:33204) ScsiDevice: 3443: device successfully registered "naa.5005076c07bfe279" from plugin "NMP" of type 13

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C3:T1:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C3:T1:L0

  0 x 50 0x05 0 x 07 0x6c 0 x 07 0xbf 0xe2 0x7b 0 x 53 x 0 41 0 x 53 0x20 0 x 53 0 x 45

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "naa.5005076c07bfe27b" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "naa.5005076c07bfe27b" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe27b' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 28 World 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.350Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.371Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for naa.5005076c07bfe27b of the unit could not detect. Initiator error of storage.

  (2014 04-22 T 19: 57:07.381Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 29 World 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.417Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x2a 0-dev 'naa.5005076c07bfe27b' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.453Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x2b world 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.479Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.479Z cpu2:33204) ScsiDevice: 3443: device successfully registered "naa.5005076c07bfe27b" from plugin "NMP" of type 13

  (2014 04-22 T 19: 57:07.501Z cpu2:33204) ScsiUid: 273: "vmhba0:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.510Z cpu2:33204) VMWARE SCSI Id: could not get the disc for vmhba0:C0:T0:L0 id

  (2014 04-22 T 19: 57:07.510Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba0:C0:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.511Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.511Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) VMWARE SCSI Id: could not get the disc for vmhba0:C0:T0:L0 id

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba0:C0:T0:L0 unit could not detect. Way to not found error.

  (2014 04-22 T 19: 57:07.520Z cpu3:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba0:C0:T0:L0" from plugin "NMP" of type 5

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: detected SCSI revision number 6 on vmhba32

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: correction of the survey data to change the revision number of the SCSI 6 to 2 on vmhba32

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: correction of the survey data to change removable media, bit of 'stop' on 'on' on vmhba32

  (2014 04-22 T 19: 57:13.043Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe279' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:13.043Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e80898f40) 0x1a, CmdSN 0xd0 world 0-dev 'naa.5005076c07bfe279' has no data of sense H:0 x 7 D:0 x 0 x 0 possible P:0: 0x5 0x20 0x0.

  (2014 04-22 T 19: 57:13.081Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe27b' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:13.081Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e80898f40) 0x1a, CmdSN 0xd1 world 0-dev 'naa.5005076c07bfe27b' has no data of sense H:0 x 7 D:0 x 0 x 0 possible P:0: 0x5 0x20 0x0.

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8355: mpx.vmhba1:C0:T1:L0:1 detected device can be a snapshot:

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8362: questioned disc ID: type 1, len 14, lun 0, devType 0, scsi 0, h (id) 16746273972281211240 >

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8369: ID of the disk drive: type 0, len 10, lun 0, devType 0, scsi 0, h (id) 1308713170419776745 >

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8355: mpx.vmhba1:C0:T0:L0:1 detected device can be a snapshot:

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8362: questioned disc ID: type 1, len 14, lun 0, devType 0, scsi 0, h (id) 15010766293529110797 >

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8369: ID of the disk drive: type 0, len 10, lun 0, devType 0, scsi 0, h (id) 13427631733060988540 >

  (2014 04-22 T 19: 57:13.131Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba0:C0:T0:L0': unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) Vol3: 714: could not read the header of control volume: unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) Vol3: 714: could not read the header of control volume: unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) SFS: 5092: pilot no. FS claimed "on the remote control": unsupported

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2059: device rescan time 101 msec (total number of 5 devices)

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2062: Filesystem probe time 70 msec (devices surveyed 5 on 5)

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2064: refresh the open volume time 0 msec

  (2014 04-22 T 19: 57:14.826Z cpu3:32851) LVM: 13089: one or more LVM devices have been discovered.

  Commissioning services2014-04 - 22 T 19: 57:16.014Z cpu0:32895) Tcpip_Vmk: 123: nd6_rs_timer: no router on 'vmk0 '. Waive

  (2014 04-22 T 19: 57:16.531Z cpu1:33651) VisorFSRam: 634: vsantraces with (0,300,0,0,755)

  (2014 04-22 T 19: 57:16.531Z cpu1:33651) SFS: 6895: mounting fs visorfs (4108aa584010) with o 0,300,0,0,1,0755, vsantraces on 4108af971220 file descriptor

  Possible the syslog.log entries

  2014 04-15 T 04: 50:20Z jumpstart: storage Info: unable to volume VMFS Mount with the UUID 522a475e-80e96251-5f62-00215e4e123e. SysInfo error on return operation State: County of parameter not valid. See the VMkernel detailed error information log

  2014 04-15 T 04: 50:20Z jumpstart: storage Info: unable to volume VMFS Mount with the UUID 522 a 4783-5bbdaecf-9237-00215e4e123e. SysInfo error on return operation State: County of parameter not valid. See the VMkernel detailed error information log

  Someone at - it useful ideas?

  Thank you!

  Either you have to will the volumes - or clean all paths dead in your esx.conf

• Clone the virtual machine to the local data store

  Hi all

  I'm looking to automate a task daily (or almost) of my friends with a small script with powercli.

  I'm trying to "backup" or to clone a virtual machine, I work in a storage of one of our servers.

  The servers are managed by a 5.1 vCenter and the machine is on a shared storage.

  From time to time, I clean, stop the machine, remove all snapshots and clone the virtual machine to one of the local server as a backup storage. So I put together a small script which almost works. It works as long as the target data store is a shared storage, but not with a local storage.

  I get always an error that claims it can not access the local data store and is not a permissions problem...

  Given that I can accomplish this via the customer without problem I thought it is possible via powercli too, or I'm wrong?

  My Script up to now:

  # Variables
  $VC = "vc.domain.com" #vCenter Server
  $User = "domain\user" #User
  $Pass = 'test123' #User PW
  $VMName = 'scripttest' #VM
  $BackupSuffix = "backup" #Suffix to add the name of VM to mark this as a backup
  $VmHost = "esx2.domain.com".
  $Datastore = 'ESX2-LocalData' #Datastore
  $BackupFolder = 'Backup' #Folder the VM gets classified

  
  

  # Register cmdlets to VMware
  

  If (-not (Get-PSSnapin VMware.VimAutomation.Core - ErrorAction SilentlyContinue)) {}

  Add-PSSnapin VMware.VimAutomation.Core

  }

  
  

  # Connect to the server

  SE connect-ViServer $VC - user $User-password $Pass

  
  

  # Remove the old clone

  $OldBackups = get - VM | WHERE {$_.} {Name: corresponds to '$VMName - $BackupSuffix'}

  If ($OldBackups - don't "")

  {

  If ($OldBackups.Count - gt 1)

  {

  Write-Host "better check! "Found several results:

  Foreach ($VM to $OldBackups)

  {

  Write-Host $VM. Name

  }

  }

  on the other

  {

  Remove-VM - VM $OldBackups - DeleteFromDisk-confirm: $false

  }

  }

  
  

  # Clone VM

  $VMInfo = get - VM $VMName | Get-View

  $CloneSpec = new-Object Vmware.Vim.VirtualMachineCloneSpec

  $CloneSpec.Snapshot = $VMInfo.Snapshot.CurrentSnaphshot

  $CloneSpec.Location = new-Object Vmware.Vim.VirtualMachineRelocateSpec

  $CloneSpec.Location.Datastore = (get-Datastore-name $Datastore |) Get - View). MoRef

  $CloneSpec.Location.Transform = [Vmware.Vim.VirtualMachineRelocateTransformation]: sparse

  $CloneFolder = $VMInfo.Parent

  $CloneName = "$VMName - $BackupSuffix".

  $TaskCloneID = $VMInfo.CloneVM_Task ($CloneFolder, $CloneName, $CloneSpec)

  
  

  # Check if the task is completed

  
  

  $Check = $false

  While ($Check - eq $false)

  {

  $Tasks = get-job | Select State, id | Where {$_.} State - eq "Running" - and $_. State - eq "pending"}

  ForEach ($Task in $Tasks)

  {

  If ($Task.id - eq $TaskCloneID)

  {$Check = $false}

  on the other

  {$Check = $true}

  }

  Start-Sleep 10

  }

  # Move clone to the backup folder

  Move-VM - VM '$VMName - $BackupSuffix' - Destination $BackupFolder

  
  

  # Disconnect

  Disconnect-VIServer-confirm: $false

  Can you show us the complete error message you get?

  BTW, the clone step can be replaced by the New-VM cmdlet with the setting of the virtual machine.

• 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

• Mapping in NFS data store fails in PowerShell

  I'm trying to access a data store NFS on my server ESXi of Powershell. I am able to access the VMFS data stores, but not my NFS datastore. I use this command:

  new-psdrive-location (get-data store Backup) - name dsBackup - psprovider VimDatastore-root ' '

  When I type cd dsBackup: I get this error:

  Get-Location: no player named ' \Datastore\ [email protected] \Datastore-172.XXX.XXX.XXX:\VM\' was found for the specified provider. Online: 1 char: 3 + cd & lt; & lt; & lt; & lt; dsBackup: Set-Location: cannot find path ' dsBackup:------' because it does not exist. Line: 1 char: 3 + cd & lt; & lt; & lt; & lt; dsBackup:

  I use the same command when you access warehouses of VMFS data without problems. I am able to browse, read and write in the VI Client NFS data store.

  Everyone knows this behavior? Any help would be much appreciated.

  Just tried with an ESXi 3.5 build 130755 store data as well.

  Works well.

  Note that I used VITK 1.5 build 142961 for this last test.

  Have you tried with VITK 1.5?

• VM HA (VM monitoring - response to the failure of data store)

  Hello

  2 ESXi hosts connected to a shared storage. We HA enabled with the default settings and "monitoring VM = Disabled.

  In the case where one of the ESXi hosts running VM1 lost access to Datastore1 that hosts VM1, HA the hang and restart this computer on the other host?

  If this isn't the case, it will be when the virtual machine monitoring is enabled? and if we have more than 10 guests, how does know where the relative data store is still active, I mean on what host?

  Kind regards

  Monitoring of virtual machine will restart a virtual machine if HA detects more VMtools beating heart, but also the network IO and storage to the virtual machine.

  If a host loses access to a data store that HA is concerned this depends on which version of vSphere is used and how to access that is lost (ODA or PDL - see details here VMware KB: loss of the device (PDL) Permanent and All - paths - Down (APD) in vSphere 5.x ).  If running vSphere 6, HA now has a feature (VM component Protection) which will restart all virtual machines affected by ODA or PDL on a host that is not affected. If using earlier versions of vSphere even with VM followed the active user intervention will be necessary since VM monitoring only restarts the virtual machine (and not on a new host) (vSphere5.1 storage improvements & #8211;) Part 4: All roads down (APD). CormacHogan.com).

  Does that answer your questions?

• 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

• Stats for each data store

  I am writing a script to determine the way to read and write rates, the average number of read and write average requests read and write latency for each data store.

  I tried to do two different ways, with my numbers to end 0.

  $startdate = (get-Date-time Minute 7 - 0 - 0 second). AddDays(-1)

  $enddate = (get-Date)

  $datastores = get-datastore

  {foreach ($DS in $datastores)

  #1

  = [string] $dswriterate ([Math]: Round ((($DS.datastore.write.average |))) Measure - Object - average value). Average), 2))

  #2

  = [string] $dswriterate ([Math]: Round ((($DS.write.average |))) Measure - Object - average value). Average), 2))

  }

  I understand that Get-Stat does not work with a store of data entity.  It would be great if I could get help with that!

  That is right.

  You can use my Get-Stat2 function to retrieve available data store counters.

  See monitor the size of your vDisks

  With the QueryMetrics switch you can see which parameters are available.

  See the usage statistics for the data store

• Data store is no longer visible in ESXi 5.0

  Hello

  I'm running the ESXi 5.0 and I recently updated.  I have a Dell PowerVault MD3200 connected, and a running data store called "Storegrid '.  I had extended hard disk MD3200 to 2.73 to space a few weeks without question or problem.  A few days ago, I tried to increase the size of the data store 'Storegrid' to include the size of the entire disk, previous size was 1.8 to.  I received an error message indicating that the operation has failed and has noticed that the data store is more listed.  I've attached screenshots showing the list of data stores and the list of storage adapters.  Any idea?

  Thank you!

  I just did some testing in my lab, reproduce your problem. It worked as planned, however I don't test the integrity of all virtual machines on this data store. Assuming that the host ESXi 5.0 is the only host access the data store, a possible solution could look like this:

  • resize the VMFS partition "lost" to a size > 1.8 to (~1.9 TB) to ensure that the 'old' end of partition is included
    partedUtil resize 1 128 4080219008 /vmfs/devices/disks/naa.6782bcb0003ec6c6000002364e5797e0
  • in the vSphere Client, perform a rescan (if the datatstore appears as invalid, wait a few seconds, then click Refresh)
  • If the data store becomes available, plan to run a full backup of the VM before

  The following steps should be done only, if no older than 5.0 ESXi host requires access to the data store.

  • Select the data store, and then click the link to upgrade to VMFS-5
  • Click with the right button on the data store, select Properties, and click the button increase to grow the data to the full size LUN store

  Yet once, I did in my lab. I always recommend to open a call with VMware.

  André