SAN access to VMFS volume snapshot

Similar Questions

• No write access to vmfs volumes

  Hi people,

  first my setup:

  SAN storage to a DataCore SANMelody Server (HP DL380 G5)

  2 2.5.4 ESX servers accessing the (VMFS 2.52) vmfs2 volumes via FC HBA (HP DL585 G2)

  ESX 3i (3.5.0, 123629 (1) to access the vmfs2 volumes via iSCSI (HP DL585 G2)

  In Configuration\Storage the volumes that all are listed (readonly or protected against writing).

  The server SANMelody says I have read/write access to the storage.

  What could be the problem? ESXi is not able to write to vmfs2?

  TIA

  Kelsey

  ESX 2.5 will not identify VMFS3.  Using virtualcenter?

• To access the servers non - VMFS volumes ESX (i)

  Suppose I have a FC LUN with a VMFS volume.  It is not accessed by a host ESX (i).  However, there are old VMDK on the logic unit number I want to recover.  If the LUN is delivered to a physical Linux server, and this physical server is zoned / correctly mapped to the FC LUNS, can I access the VMFS LUNS for the vmdk off of it?

  Thank you

  Yes.

  http://digfor.blogspot.com/2011/04/accessing-VMFS-partitions.html

• When I tried to power on VM ends up in the right error: the specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  I stop a virtual machine after a certain time, I tried to power. Its has ended up in the following error message

  Reason: The specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  The machine was working fine before the closure.

  In the data store, the file type of the virtual machine is 'file' instead of 'virtual drive '.

  Help, please

  You are missing the file descriptor hard. The xxxx - flat hard is the file that contains the data effectively. But the xxxx.vmdk is missing, which is a text file that connects to the flat file.

  AWo

• New SAN / VMFS Volume

  Hi all

  Hoping someone has seen this before.

  We have just put online a new SAN expansion tray. This new ferry has more storage than our previous trays in which we never created 1 TB LUN / VMFS volumes.

  This new Board has been configured with a 3.64 LUN TB. The LUN has been initialized and in good health.

  In an attempt to build the VMFS volume, he sees the 3.64 TB, but shows only 1.64 TB as being available.

  The SAN is a Sun 6140.

  Does anyone have any ideas / suggestions?

  Thank you

  Matt

  There is a limit of 2 TB on the size of the LUN that is presentable to the ESX host. When a logic unit number bigger 2 TB is presented the surplus we may be listed, so in your case you see the quantity is greater than 2 TB (1.64 TB)

  Try to create 2 MON 1 x 2 TB and 1 x 1.64 TB and host see storage without problem.

• Discs of ESXi supports local (UFS) as a Volume/vmfs/volumes - didn't want not!

  Hi all

  Updated from 5.5U2 to 6.0

  A race of NAS VM using two disks using RDM (virtual) to get direct access to disks and smart State - created with the flag - z.

  After the upgrade to 6.0, ESXi now mounted (s?) drive - which are SoftRAID(4) 1 and have a file system UFS - to/vmfs/volumes/sink. This happened only after the second start, but now there is no way back for me.

  After the first reboot after upgrade, I was able to assign the disks to a virtual computer and restart it. On the next reboot, the problem above has occurred.

  Perhaps interesting to note that the volume is not mounted as a VMFS storage (at least it seems), but directly in the folder/vmfs volumes - and it is not a symbolic link like usual data warehouses.

  Tried Altready:

  / recreate the files with vmkfstools RDM

  Unmount the volume/vmfs/volumes/disassemble sink via esxcli file storage system (using all the u/n/p options, but ESXi said he "can not find the nas drive", which is not really sense)

  There is a thread on serverfault (not mine) with the same problem and similar details.

  VMware - 6.0 ESXi RDM mounting as local volume - Super user

  For the moment, I went down to 5.5u2 to access the virtual machine to work.

  Any help is appreciated.

  See you soon

  IAM

  It is possible to blacklist the ufs module with the following command to esxcli, and won't automount in volumes of ufs. the host reboot is required

  $ esxcli system module set m eggs e fake

• Get the mistakes reached Maximum Volume Snapshots, trying to convert VMDK XP system hotcloning with converter last worm

  Hi I get this error reaches Max Volume Snapshots re trying to convert VMDK XP system with converter hotcloning latest version 5.5.1. Error results in the conversion of a physical machine to fail at 1%.

  I'm trying to convert a drive with a dual boot XP - 2 Xps on it for a Player 6 - a VMware VMDK as a C partition with W98SE original who no longer use.  The C partition has the bootloader boot ini for the dual Xps located on J and I have partitions.  Other partitions on disk cloning whole (need set as Xps access these disks at startup are: D, E: Docs program and shared (a logon for XP user profiles) and F, G and H (contains HD virtual 98SE VirtualPC) partitions.)

  I'm running a chkdsk /f /r on all partitions and deleted snapshots of volume system (from system restore) and disabled the system restore in case that is the question.  I also tried to disable firewall as shown in the manual and stop several 3rd party services to run.  Do not use additional options when cloning.  Target is a 1 to free space (more copy partitions/disc) on a USB external drive '3 '.

  I tried also with just J and no Partition selected with others and same error so not deliver the prob a system double - but do not know if the two will be not bootable in Vm together via boot ini choose as yet have on the physical machine.  Anyone know if this still works as a dualboot on VM or should I be cloning each with C separately like J or I become C as their drive letters are associated with many years of program installs don't want again.  Not sure if can fix these at the same time to be able to start or if on separate drives in the VM and always have access to all other partitions of two Xps - someone knows how to do better?

  Also re my mistake - it's mainly what need fixed so he can achieve it - or it will be allowed to do this conversion coldclone via Windows 8.1 I on another drive - however C drive I need appears as a V as W81 is C on the host.  This will allow even a dual boot VM or at least one of the Xps or bootable drive v - maybe if I move it to C partition 1st position when copying VMDK?  Please keep in mind I have no job and only will use VmWare Player 6 or try in VirtualBox or Hyper-V on the host Windows Pro 8.1 if VmWare Player fails.

  Thank you, but I had already done this and always says without clichés or none - questions - after even managed to fix my COM + install as well.

  Alternative SOLUTION for those who have problems making their host Xp Vm hotclone

  I finally used MOA Cold Clone ISO converter to make a virtual machine of my XPs and related partitions and now finally it seems to work after the configuration of the virtual machine created with the latest Vmware converter 5.5.1 (just to add Vmware Tools and remove selected restore points) via my host Windows 8.1 (such that it is impossible to configure via MOA but fact VM thin image).

  Anyone with problems of manufacturing since their host XP VM and if want to make a VMware Player image - search the Internet for MOA Cold Clone converter (it uses a worm old VMware Converter 3 that allows cold cloning, I think that later to not)-it was relatively easy to install and use.

  I could also dual boot via the boot ini file as before my 2 XP systems.

  Make sure you just prΘconfiguration your ini file to start I did before the virtual machine to the physical host partition is on - I've added a few other partitions to start from tests in case of boot partition number has changed as he did.

  For example: my Xp scores came after the 1st Partition C (boot ini containing the partition) and also a 2nd Partition - D and 3rd Partition - E (I left out F and G as agreed is no need as on the host) so my first XP became Partition 4, then 5 other XP Partition so in boot ini, I had put this :

  [boot loader]

  Timeout = 10

  default = multi (0) disk (0) rdisk (0) partition (5) \WINDOWS

  [operating systems]

  "multi (0) disk (0) rdisk (0) partition (5) \windows="XP Pro SP3 HAND J - C Bootini "/ EAP/fastdetect / 3 GB USERVA 2560/noexecute = OptIn

  "multi (0) disk (0) rdisk (0) partition (4) \windows="XP REPLACEMENT / OLDER I DRIVE - ADMIN USE ONLY - repair/rescue/Backup "/ PAE USERVA 2560/fastdetect/noexecute = OptIn

  multi (0) disk (0) rdisk (0) partition (6) \windows="TEST PARTITION 6" / EAP/fastdetect / 3 GB USERVA 2560/noexecute = OptIn

  multi (0) disk (0) rdisk (0) partition (7) PARTITION 7 "\windows="TEST / EAP/fastdetect / 3 GB USERVA 2560/noexecute = OptIn

  multi (0) disk (0) rdisk (0) partition (8) \windows="TEST SCORE 8" / EAP/fastdetect / 3 GB USERVA 2560/noexecute = OptIn

  multi (0) disk (0) rdisk (0) partition (9) \windows="TEST PARTITION 9" / EAP/fastdetect / 3 GB USERVA 2560/noexecute = OptIn

  Test scores from 4 as I thought new shoe that would be 4, then 5 and then others added in case

  You will need to change the number depending on how much other partitions are in front of your XP ones.

  I used free Easeus Partition Manager to control the order of the partitions I was cloning the drive.

  A free EasyBCD allows you also to modify and label your partitions to change your boot.ini file easily once you start in the right partition to boot ini that you set up above and before that you do / clone your Virtual Machine.

  Note: the boot ini can only contain a limited number of registrations or bloodlines tests then you partition carefully probably not exercising that your operating system will be on after cloning a Vm.

• "Access to the volume, batch" on a daily basis

  Hi all

  In the hope of a few tips see where to look because we know so many questions.

  The environment is:

  ESX 5.5 (last version update of this week)

  HP ProLiant BL460c Gen8 blade

  Brocade FC switches

  VNX5400 storage

  Everything is current patch level (HP Feb SSP, latest drivers etc from the latest edition of VMWare/HP Cookbook)

  On a daily basis, we see the messages of the following:

  Lost access to the volume 52e00703 - 7702b 882 - d845 - a 0017, 4779402 (data store) because of connectivity issues. Recovery attempt is underway and results will be communicated shortly.

  05/07/2014-07:50:16

  Access to the volume 52e0072b-0adb69f0-f97b - a 0017, 4779402 (DataStore) connectivity issues.info successfully restored the suite

  Of the vmkernal.log, I see these messages:

  (2014 05-07 T 02: 44:14.860Z cpu0:33743) lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0: (0): 3271: FCP cmd x2a failed < 2/4 > sid x0d0505, did x0d0100, oxid xd4 Abort requested host Abort Req

  (2014 05-07 T 02: 44:14.860Z cpu0:32813) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x2a (0x412e80450900, 32805) dev 'naa.60060160fd503600ea66bd8acb82e311' the path 'vmhba0:C0:T2:L4' Failed: H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 05-07 T 02: 44:14.860Z cpu0:32813) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.60060160fd503600ea66bd8acb82e311' of device NMP doubt; asked the State of the fast path update...

  (2014 05-07 T 02: 44:14.860Z cpu0:32813) ScsiDeviceIO: 2337: Cmd (0x412e80450900) 0x2a, CmdSN 0 x 299 worldwide 32805 to dev 'naa.60060160fd503600ea66bd8acb82e311' has no sense H:0 x 5 D:0 x P:0 x 0 possible 0-data: 0 x 0 0 x 0 0 x 0.

  (2014 05-07 T 02: 44:15.859Z cpu0:32881) lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0: (0): 3271: FCP cmd x2a failed < 2/4 > sid x0d0505, did x0d0100, oxid xe7 Abort requested host Abort Req

  (2014 05-07 T 02: 44:15.860Z cpu0:32813) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.60060160fd503600ea66bd8acb82e311' of device NMP doubt; asked the State of the fast path update...

  (2014 05-07 T 02: 44:15.860Z cpu0:32813) ScsiDeviceIO: 2337: Cmd (0x413682f6e580) 0x2a, CmdSN 0x29a worldwide 32805 to dev 'naa.60060160fd503600ea66bd8acb82e311' has no sense H:0 x 5 D:0 x P:0 x 0 possible 0-data: 0 x 0 0 x 0 0 x 0.

  (2014 05-07 T 02: 44:20.025Z cpu4:36428) World: 14296: VC opID 4CAEF736-0000009 D-0-fb maps to vmkernel opID 4f50e1ac

  (2014 05-07 T 02: 44:20.397Z cpu1:34426) capability3: 15408: Max (10) attempts exceeded for appellant Fil3_FileIO (status "IO has been abandoned by VMFS via virt-reset of the unit")

  (2014 05-07 T 02: 44:20.397Z cpu1:34426) BC: 2288: cannot write (couriers) object '. iormstats.SF': level core exceeded Maximum attempts

  (2014 05-07 T 02: 44:23.013Z cpu8:34236) HBX: 2692: waiting for [HB State offset abcdef02 4161536 gen 179 stampUS 1629072438 uuid 536997 d 8-04a1ea9d-6c9a - 0017 has 4779402 jrnl < 2656233 FB > drv 14.60] expired on flight 'uk1 - san01:Production data store 3'

  (2014 05-07 T 02: 44:29.645Z cpu4:33106) lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0: (0): 3271: FCP cmd xa3 failed < 3/4 > sid x0d0505, did x0d0000, oxid xeb Abort requested host Abort Req

  (2014 05-07 T 02: 44:29.645Z cpu20:33044) VMW_SATP_ALUA: satp_alua_issueCommandOnPath:651: path 'vmhba0:C0:T3:L4' (UP) command 0xa3 failed with status Timeout. H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 5 20 x 0 0 x 0.

  (2014 05-07 T 02: 44:29.755Z cpu7:32857) HBX: 255: recovered for volume 52e0072b-0adb69f0-f97b - 0017 has 4779402 heart rate (uk1 - san01:Production 3 DataStore): Offset [Timeout] 4161536

  (2014 05-07 T 02: 44:29.755Z cpu7:32857) [HB State offset abcdef02 4161536 gen 179 stampUS 1632947371 uuid 536997 d 8-04a1ea9d-6c9a - 0017 has 4779402 jrnl < 2656233 FB > drv 14.60]

  (2014 05-07 T 02: 44:31.808Z cpu0:32807) lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0: (0): 3271: FCP cmd x2a failed < 2/4 > sid x0d0505, x0d0100, x 112 requested Abort Abort Req host oxid fact

  (2014 05-07 T 02: 44:31.808Z cpu0:32813) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.60060160fd503600ea66bd8acb82e311' of device NMP doubt; asked the State of the fast path update...

  (2014 05-07 T 02: 44:31.808Z cpu0:32813) ScsiDeviceIO: 2337: Cmd (0x412e8349b000) 0x2a, CmdSN 32805 to dev 'naa.60060160fd503600ea66bd8acb82e311' world 0x2ab has no sense H:0 x 5 D:0 x P:0 x 0 possible 0-data: 0 x 0 0 x 0 0 x 0.

  (2014 05-07 T 02: 44:32.407Z cpu1:34426) capability3: 15408: Max (10) attempts exceeded for appellant Fil3_FileIO (status "IO has been abandoned by VMFS via virt-reset of the unit")

  (2014 05-07 T 02: 44:32.407Z cpu1:34426) BC: 2288: cannot write (couriers) object '. iormstats.SF': level core exceeded Maximum attempts

  (2014 05-07 T 02: 44:33.541Z cpu16:32855) HBX: 255: recovered for volume 52e0072b-0adb69f0-f97b - 0017 has 4779402 heart rate (uk1 - san01:Production 3 DataStore): Offset [Timeout] 4161536

  (2014 05-07 T 02: 44:33.541Z cpu16:32855) [HB State offset abcdef02 4161536 gen 179 stampUS 1646119268 uuid 536997 d 8-04a1ea9d-6c9a - 0017 has 4779402 jrnl < 2656233 FB > drv 14.60]

  Any help much appreciated.

  Thank you

  The problem was a combination of factors.  Specifically, THIN LUNS on EMC VNX with Windows 2012 R2.  It's to do with how 2012R2 TRIM questions and cancel orders MAPPING in the table.  Basically, he blows on MS and has a knock on effect on all LUNS.

  The thing in our case is that we have a chassis package HP blades, for the most part running ESX, Windows R2 2012... and we essentially had a single physical machine 2012R2 out the table in its entirety...

  Defrag on 2012R2 exasperated this issue and was a way to find the number of logic (light IO) massive unit on the Page file for example, LUN during the defragmentation operation

• 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

• A procedure to remove a VMFS Volume?

  Hello

  We use EMC CLARiiON CX4 SAN

  We have created 5 VMFS volume and am migrated VMs.

  We will remove the VMFS-3 volume.  We would like to ask for your opinion if the next step is correct?

  (1) remove the Volume VMFS VI client

  (2) remove the VI Client VMFS Volume

  (3) delete the storage group logical unit number in EMC Enterprise Manager

  (4) destroy the LUNS in EMC Enterprise Manager.

  Thank you

  Looks fine measures, more take a look at this article

• Lost access to the volume after upgrade 4.1

  Setup

  1 x HP c7000 blade box

  3 x HP BL460cG6 with dual Xeons 5540 and 48Gb of RAM, cards ISCSI HBA, QLogic

  3 x HP P4300 Lefthands

  4 x 3020 Cisco switches for blade in the back the c7000, 2 x dedicated to iSCSI traffic

  vSphere 4.1 Server

  The problem

  We went through the entire process of upgrading our server for vSphere 4.0 to 4.1 to manage a stand-alone ESXi 4.1 system, so our attentions turn to our 3 blades running ESXi 4.0u1 we used the built in Update Manager, downloaded the 4.0 to 4.1 upgrade file and we have improved our first blade and it did not notice problems as there put servers have was little used those.  We then upgraded the second and moved our main mail on her server.

  It was when we did that we started getting errors when people were losing connection to the exchange server, after some research we've seen of the event and we have been to see the error:

  "Lost access to the volume because of connectivity issues."  Recovery attempt is underway and the results will be available shortly"

  Then 10 seconds later we get the message:

  "Successfully restored access to the volume due to connectivity problems."

  This error only occurs on the blades of 4.1, we have restored a blade on 4.0 and errors are not displayed and no errors were reported with the servers on this blade.  As far as we can say it is not a network problem since all blades for iSCSI traffic flows on the same switches to the Lefthands, and we were losing the connection to volumes on the two Lefthands.

  We have a call connected with HP about this, but from the Yes, we cannot determine what is causing this problem and how to solve.

  So any help is greatly appricated

  Thank you

  Dave

  This is due to a combination of ESX(I) 4.1, QLogic and version Lefhand SAN/IQ 8.5 with the 10092-00 patch version. I did a blogpost on his problem:

  http://yuridejager.wordpress.com/2011/02/07/lost-access-to-volume-error-with-hp-lefthand-san-storage-after-upgrading-to-vmware-vsphere-41/. I hope this helps.

• VMFS volumes

  I use Virtual Center 2.5 with four ESX host in the same cluster. Through WinSCP, when I browse to the directory vmfs\volumes on the ESX host all it shows me all the files LUN that has a small black arrow. Does this mean that these folders are shortcuts that point to my CX 300 fibre channel storage array? My ESX servers have only 130 GB of total space so I know that it cannot contain information logic unit number. I boot from SAN and are all VMDK on the SAN. I'm guessing that they are shortcuts pointing to my SAN. Is this correct?

  Thank you

  Hello

  Yes, I think you're right, these shortcuts are your warehouses data pointing back to the LUNS on your CX300.

  I see the same thing using Veeam FASTSCP.

  Alex

• Access to VMFS existing via iSCSI storage

  Hi all

  In a test environment, I'm trying to access a VMFS existing via iSCSI data store.

  In the storage adapters, I clicked on Rescan. The SCSI target is displayed correctly. However, it is not in the storage, even after clicking on refresh.

  If I click on add storage and select disk/LUN, I can see the storage device, clicking on watch then the primary Partition as VMFS. Of course if I click Next again this reformatted it as a new data store, something I don't want to do.

  How can I get this existing VMFS volume is displayed in the storage?

  TYIA,

  Eric

  www.mymanagedbackup.com

  Have you tried to define enableresignature on 1 in the advanced settings (see attached) and then a new analysis.

• How to set the HostDiskPartitionAttributes property when creating Vmfs volume

  Hi all

  When creating vmfs datastore through vlume

  programmatically, I need to partition the vmfs volume. here my question

  is an idea how to set the HostDiskPartitionAttributes there is a

  parameter to create vmfs vloume. Here I use Vdisk lun san

  "that will have the size, raid, stripesize... by this I need to set this.

  HostDiskPartitionAttributes ' property.could someone help me please. "

  Note: it's links to the document:

  http://www.VMware.com/support/developer/VC-SDK/visdk25pubs/ReferenceGuide/index.html

  is the method that you need to find CreateVmfsDatastore.

  Thank you

  As partition is a contiguous series of blocks on a disk that is marked to be used and is considered in each sector of 512 bytes. Must divide the space into sectors and specify startSector and endSector according to your requirement, that the way in which large partition you want to create.

• Understanding and getting rid of the list of devices of "cliché generic volume snapshot.

  Under devices, I have a list of 40 generic volume snapshot: How can I get rid of them and what is everything?

  Hello

  Please read this on Volume Shadow copies: http://en.wikipedia.org/wiki/Shadow_Copy Best of Luck, Rick Rogers, aka "Crazy" - Microsoft MVP http://mvp.support.microsoft.com Windows help - www.rickrogers.org