ESXi 3.5 4 problem to upgrade by adding the VMFS partition existing on iSCSI SAN

Similar Questions

• 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

• Upgrade Wizard indicates the active partition is compressed

  Hello

  I have a MSI Netbook running Windows 7 Starter and want to go to Windows 10.

  I run the upgrade wizard that tells me the current active partition is compressed.

  I checked in the management of the computer - I have:

  Recovery partition - 8.35 GB

  Active, the recovery Partition - 100 MB

  Boot, page file, crash dump, primary Partition - 173,79 GB - OS_Install (c :))

  Primary partition - 115,86 GB - Data (d :))

  All are listed as single - base; C: and D: are NTFS; the other two have no file system listed.

  None of the partitions are indicating as "compressed". In Solution Explorer, I have the opportunity to make compressed (thus taken as it is 'uncompressed').

  All sitting on a WD 320 GB drive (289.1 GB used by partitions).

  I do not have access to any partition other than C: and D: and I imagine wouldn't upgrade.

  So why I said that the current active partition is compressed.

  I notice that I could make C: partition Active - but what effect would it have on the boot and the functioning of the netbook?

  Any help would be appreciated.

  Thank you.

  I notice that I could make C: partition Active - but what effect would it have on the boot and the functioning of the netbook?

  Not a good thing. Unless you run the following command as an administrator before:

  BCDboot C:\Windows /s C:

  the copy of your 'System reserved' start-up files in C: this way.

  Best regards, VZ

• The VMFS partitions and ESX in MUV upgrades

  Back in the day when you installed ESX it deems any VMFS partition is priese formatting for you even if you had all your machines on them

  I intend to upgrade ESX 4.0 to 4.1 using AUVS that resembles a simple process.  Anyone know if:

  1. it clears the local VMFS partition?

  2. He wipes SAN VMFS partitions that it finds?

  Thank you

  Stu

  N ° you don t be vmfs http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022140 loss

• ESXi 4.0 to 4.1 upgrade - cannot access the client

  Hi all, I'm quite new to VMware, I have a server I just start, it's a physical server for VMware Vsphere hypervisor, Esxi 4.0 on it and I am unable to connect to the machine using the clients that you download from the web interface as 4.0 does not seem to work because of the update of the .NET framework.

  To remedy this, I need to upgrade the server to 4.1 but my question is this... How change the server if I can't connect to the server using the client?, is there another way?

  Any help would be greatly appreciated

  Welcome to the VMware forums communities.

  For the client error this might help - http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vsphere-client-error-parsing-the-server-server-ip-clients-xml-file-login-will-continue-contact-your-system-administrator.html.

  To update the host, you can use (vCLI) vSphere command-line Interface.  You can download that from the VMware web site.

  (1) use the command of the vicfg-hostops put the host in maintenance mode - http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vicfg-hostops.html

  (2) use vihostupdate to upgrade your host - http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vihostupdate.html.

• Upgrade to ESX4 without VMFS partition

  Hello, I have a u2 ESX 3.5 with a tip of SAN a GB 20 LUN, without the local disks to the ESX 3.5, it is fine, but I need to upgrade to ESX 4 with VUM and to do this, I need to a data store VMFS 9.2 GB for the service ESX4 console.

  The 20 GB partition table. LOGICAL UNIT NUMBER.

  / dev/sdx3 9.2 G 1.2 G 8.0 G 19%.

  / dev/sdx1 97M 29 M 64 M 29% / Boot

  / dev/sdx2 5.2 G 121 M 4.8 G 3% / opt

  No 132M 132M 0 0% / dev/shm

  / dev/sdx8 985M 75 M 860M 9% / tmp

  / dev/sdx6 2.5 G 494 M 1.4 G 27% / var/log

  If I want to reinstall ESX 3.5 year create partitions and a data store vmfs 10GB for 4 ESX service console, I can restore the configuration if I only backup the directory "/ etc" and then copy over the new ESX 3.5 for the upgrade with VUM?

  Thank you.

  may be a stupid question, do you have the provision to add another 10 + GB of LUN\Disk? If so, create VMFS volume on this disk\LUN and use the same for COS vmdk during the upgrade.

  By the way, where is your current VMFS data store is located? It is not required to keep the vmdk cos in a Local data store, you can keep it in warehouses of data VMFS3 except SIN and SWiSCSI.

  : +: VCP, RHCE, EMCPA.

• ESXi 4.0 to 5.0 upgrade

  First of all the part I: good subject?

  HY,

  First part II: I'm new to VMware... Be prepared to explain the basics of... (I'm just learning by using and now need some more general information about the update process... to understand what the idea)

  I have 2 physical servers. One with ESXi 4.0 and the other with ESXi 4.1. On these systems of ESXi, I run a total of 10 servers. To manage them and all servers on them, I use two separate vSphere customers.

  Now I want to move to ESXi 5.0 and I don't know which way I have to choose...

  The simplest way seemes to vCenter Update Manager. But I do not have a vCenter. The first question is: should I buy a just save some time on the upgrade of my virtual "sphere"...? (Q1) Is there an update for vSphere Client Manager? (Q2)

  What are the other options? (Q3) so I have no vCenter should I do with the command line? (Q4)

  If you would like to recommend buying a vCenter I have a few questions:

  -Cannot run vCenter on the ESXi which should be updated... right? (because it cannot update its own ESXi host) (Q5)

  -I can run vCenter since a normal Dektop PC (not as a virtual machine)... right? (Q6)

  A few Questions about the update process:

  We always have an ESXi host with some servers on this... We must therefore update ESXi as well as all the servers that are running on it... (in addition, we need update vCenter and vSphere Client)

  Here is how I would do or how I understand the process: (with vCenter)

  (1) install vCenter 5.1 (which is compatible with 4.x and 5.x) on a Dektop PC and connect to my ESXi 4.0

  (2) install for my vCenter Update Manager...

  3) update ready for ESXi with UpdateManager

  4) update ready for all virtual machines with UpdateManager

  (4) start updates

  These statements are correct?

  -Can I update my ESXi and my VM automatically when I use and properly configure the Update Manager (Q7)

  -l'UpdateManager can roll automatically when an update fails? (but what when the ESXi update was ok, but some of the virtual machine cannot lie?) (Q8)

  Or... Would you recommend to separately update?

  -copy all the VM to a new location

  -convert the virtual machine is there to 5.0

  -ESXi 5.0 update and bind the new data store (where is all VM 5.0) and then test the 5.0 VM on the new 5.0 ESXi... if ok remove the old data store 4.0 (and if wanted to move the 5.0VM back to the old data store)... If NOK reinstall ESXi 4.0 and bind old data store where is all 4.0 VM...

  If you want, you can use the 'Qx' legend behind the question to answer a specific Question...

  Thank you very much in advance for your help!

  UPGRADE to ESXi:

  I checked again, the documentation and it looks really is possible to upgrade a host which was previously installed with ESXi 3.5 upgrade to ESXi 4 then 5 ESXi. I've never done, but in all cases the old hardware was not supported for the latest version of ESXi.

  In any case, the problem is not related to the VMFS version, but rather to the layout of the partition. ESXi 3.5 created 2 partitions bootbank with 48 GB each and with ESXi 4/5 the size of this partition must be of 250GB.

  I say try the interactive CD upgrade, but make sure you have a current backup of your virtual machines.

  UPGRADE of the virtual computer:

  The option to upgrade virtual hardware displayed only for virtual machines with older versions of hardware. If you want to see what it looks like, create a virtual dummy with HW version 4 machine by selecting "custom" in the installation wizard.

  Last UPDATED (general):

  Except for the order of upgrade of the tools and HW version, it seems ok. First upgrade tools to ensure that the virtual machine uses drivers required for the hardware upgrade.

  André

• How can I reinstall / store data recovery an ESXi 4.1 lost during an upgrade to 5.5?

  I was running a host of ESXi 4.1 on a Dell T110 II with two RAID, a managed arrays by the controller integrated RAID that contained the system of ESXi and a small data store (channel) and the other controlled by a 6405e Adaptec controller which contained my main data store (BunkerHill). In the process of upgrading from 4.1 to ESXi 5.5, I forgot to include the drivers for the Adaptec 6405e controller and even if the upgrade of the host, he did not see the BunkerHill data store.

  I downloaded and installed the VIB for the controller 6405e and after restart the host ESXi 5.5 shows the Adaptec RAID under storage adapters, but the BunkerHill data store is still not visible and all virtual machines guests appearing on this show as unknown in the inventory. The channel data store and two invited VMS it holds are visible. Below a part of the kernel log is filtered on the RAID controller device name.

  I would like to get the recognizable BunkerHill data store before continuing the upgrade and would be grateful if someone could point me in the right direction (KB article, display, etc. that explains what I do). I need to reinstall 4.1 on the work of RAID (ESXi 5.5 and channel data bank) and then trying to reconnect the main data store, or are there changes I can do from the console to manually get the market things?

  Tips are appreciated,

  Thank you

  
  

  rSid

  (2015 06-16 T 03: 39:59.758Z cpu1:33296) PCI: 1095: 0000:03:00.0 named "vmhba2" (has ")

  (2015 06-16 T 03: 40:08.781Z cpu0:33415) VMK_PCI: 395: 0000:03:00.0 device name: vmhba2

  (2015 06-16 T 03: 40:08.781Z cpu0:33415) DMA: 612: DMA 'vmhba2' engine, created using the Mapper "DMANull."

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 976: path 'vmhba2:C0:T0:L0': seller: model "Adaptec": "BukerHill" Rev: 'V1.0 '.

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 979: path "vmhba2:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 1105: path 'vmhba2:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 1503: Add the path: vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:09.238Z cpu1:33415) ScsiNpiv: 1510: GetInfo for adapter vmhba2, [0x4108984b0280], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2015 06-16 T 03: 40:19.582Z cpu2:33177) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba2:C0:T0:L0 '.

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba2:C0:T0:L0 for the device "unregistered".

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 7420: get VPD 83 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 7456: get VPD 86 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 6170: QErr setting for mpx.vmhba2:C0:T0:L0 of the unit could not detect. Failure of the error.

  (2015 06-16 T 03: 40:19.839Z cpu3:33177) SFS: 5091: pilot no. FS claimed device 'mpx.vmhba2:C0:T0:L0:1': not supported

  (2015 06-16 T 03: 40:19.839Z cpu3:33177) ScsiDevice: 3443: device successfully registered "mpx.vmhba2:C0:T0:L0" from plugin "NMP" of type 0

  (2015 06-16 T 03: 40:24.005Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:24.352Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:24.676Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:29.840Z cpu0:33780) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:29.990Z cpu0:33785) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:30.177Z cpu0:32908) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:30.177Z cpu0:32908) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:30.194Z cpu2:33786) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:36.672Z cpu3:34032) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8089cdc0, 34344) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089cdc0) 0 x 85, CmdSN 0x0 34344 to dev 'mpx.vmhba2:C0:T0:L0' world not a sense H:0 x D:0 x 2 P:0 x 0 0 data not valid: 0 x 5 0x20 0x0.

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x4d (0x412e8089cdc0, 34344) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089cdc0) 0x4d, CmdSN 0x1 worldwide 34344 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 03: 42:04.870Z cpu1:32909 opID = affe9c27) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 42:04.870Z cpu0:32909 opID = affe9c27) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 42:04.939Z cpu2:34420 opID = f965f306) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 43:25.893Z cpu0:32907 opID = de9d40eb) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 43:25.894Z cpu0:32907 opID = de9d40eb) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 43:25.976Z cpu1:34414 opID = 12fa472c) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 43:39.199Z cpu1:32906 opID = f8418990) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 43:39.199Z cpu1:32906 opID = f8418990) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 43:39.272Z cpu0:34043 opID = 8eb97c3d) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 32:43.729Z cpu1:33296) PCI: 1095: 0000:03:00.0 named "vmhba2" (has ")

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) VMK_PCI: 395: 0000:03:00.0 device name: vmhba2

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) DMA: 612: DMA 'vmhba2' engine, created using the Mapper "DMANull."

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 976: path 'vmhba2:C0:T0:L0': seller: model "Adaptec": "BukerHill" Rev: 'V1.0 '.

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 979: path "vmhba2:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 1105: path 'vmhba2:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 1503: Add the path: vmhba2:C0:T0:L0

  (2015 06-16 T 04: 32:51.940Z cpu1:33415) ScsiNpiv: 1510: GetInfo for adapter vmhba2, [0x4108984b0280], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2015 06-16 T 04: 33:02.185Z cpu2:33177) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba2:C0:T0:L0 '.

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba2:C0:T0:L0 for the device "unregistered".

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiDeviceIO: 7420: get VPD 83 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiDeviceIO: 7456: get VPD 86 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 04: 33:02.199Z cpu1:33177) ScsiDeviceIO: 6170: QErr setting for mpx.vmhba2:C0:T0:L0 of the unit could not detect. Failure of the error.

  (2015 06-16 T 04: 33:02.439Z cpu0:33177) SFS: 5091: pilot no. FS claimed device 'mpx.vmhba2:C0:T0:L0:1': not supported

  (2015 06-16 T 04: 33:02.439Z cpu0:33177) ScsiDevice: 3443: device successfully registered "mpx.vmhba2:C0:T0:L0" from plugin "NMP" of type 0

  (2015 06-16 T 04: 33:06.593Z cpu2:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:06.992Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:07.322Z cpu1:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.467Z cpu2:33780) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.608Z cpu2:33785) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.791Z cpu1:32908) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 33:12.791Z cpu1:32908) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:12.807Z cpu0:33786) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:21.919Z cpu2:34032) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8089db80, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089db80) 0 x 85, CmdSN 0x0 34335 to dev 'mpx.vmhba2:C0:T0:L0' world not a sense H:0 x D:0 x 2 P:0 x 0 0 data not valid: 0 x 5 0x20 0x0.

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x4d (0x412e8089db80, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089db80) 0x4d, CmdSN 0x1 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 04: 54:09.845Z cpu0:32906 opID = 372194ec) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 54:09.845Z cpu0:32906 opID = 372194ec) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 54:36.638Z cpu1:32910 opID = 6037ca3e) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 54:36.638Z cpu1:32910 opID = 6037ca3e) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 54:36.713Z cpu0:34040 opID = 2ffcf7c7) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 55:22.146Z cpu0:32909 opID = a7c2c9af) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 55:22.146Z cpu0:32909 opID = a7c2c9af) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 55:22.218Z cpu3:34041 opID = c15706cb) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8084d6c0, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8084d6c0) 0 x 85, CmdSN 0x3 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8084d6c0) 0x4d, CmdSN 0x4 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e80875440, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e80875440) 0 x 85, CmdSN 0x6 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e80875440) 0x4d, CmdSN 0 x 7 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x10

  (2015 06-16 T 05: 52:04.275Z cpu2:32787) WARNING: ScsiDeviceIO: 1223: mpx.vmhba2:C0:T0:L0 camera performance has deteriorated. Latency of I/O increased value average of 414 microseconds to 13216 microseconds.

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8083a380, 48445) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8083a380) 0 x 85, CmdSN 0x9 worldwide 48445 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8083a380) 0x4d, CmdSN 0xa worldwide 48445 to dev 'mpx.vmhba2:C0:T0:L0' has no meaning H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 05: 58:07.182Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:07.182Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:07.183Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x20

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8088b8c0, 50440) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) ScsiDeviceIO: 2338: Cmd (0x412e8088b8c0) 0 x 85, CmdSN 0xc worldwide 50440 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) ScsiDeviceIO: 2338: Cmd (0x412e8088b8c0) 0x4d, CmdSN 0xd worldwide 50440 to dev 'mpx.vmhba2:C0:T0:L0' has no meaning H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e80896800, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) ScsiDeviceIO: 2338: Cmd (0x412e80896800) 0 x 85, CmdSN 0xf worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) ScsiDeviceIO: 2338: Cmd (0x412e80896800) 0x4d, CmdSN 0x10 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  Hello

  looks like resignaturing volumes data store could help.

  Here is another discussion of a user to get similar errors: Vmware 5.5 Upgrade breaks access the VMFS data store (kind of)

  More information: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011387 and literature vSphere Documentation Center

  cykVM

• Keyboard problem after upgrade to 6.0

  Hello everyone

  I used 5.5 of Vmware Vsphere ESXI and Vcenter 5.5 without any problem of keyboard on the remote console on the guest operating system (win 7) after upgrade to esxi, vcenter 6.0 and 6.0, I have problems with the keyboard on the guest remote operating system, note I use french keyboard.

  french keyboard is also used by the operating system remotely.

  How can I solve this problem, so when I try the console remotely on the guest operating system display does'nt English keyboard us keyboard

  Thank you

  the problem is still persisting when using the web console, but when you use the remote console MRC the keyboard works normally

• ESXi 5.1 to 5.5 upgrade

  Hi all

  I intend to spend any esxi 5.1 5.1 to our newly built 5.5 vCenter vCenter army.

  We not have distributed switches, SRM, Vmware view etc...
  Not also concerned historical data in vCenter 5.1

  What is the best way to do it?

  Here is my planned approach

  • Create new cluster on vCenter 5.5 that will even
    as cluster in vCenter 5.1.
  • Disconnect hosts in vCenter 5.1 and register
    ESXi host to vCenter 5.5
  • I guess when I do this standard will all be
    always available as it is esxi host specific not vcenter.
  • We have 5 guests clustered, so I intend to
    remove a host both the cluster and esxi 5.1 to 5.5 upgrade using Update Manager
    5.5 the new vCenter.
  • Given that I don't update facility, I'm not sure will
    switch support will be always there after upgrade. We use iscsi for storage
    and it uses a standard switch. If it is not available I can recreate after upgrade.
  • Anything that suggests on pit fall that I need attention in this plan, please suggest.

  Thank you...

  I did these migrations several times in the past and that you are having problems.

  What I usually do in such cases is to:

  • Disable HA in two groups (the current/old as well as new)
  • Make sure you of EVC is configured correctly to the new cluster (if necessary)
  • disconnect and remove all hosts (one by one) from the old server vCenter Server and add them to the new cluster
  • configure settings like HA cluster, DRS...
  • Once everything works as expected begin the upgrade of the host

  Be sure to reconfigure your backup software (and any other 3rd party software and Add-ons) after migrating to the new vCenter Server hosts.

  André

• Live iSCSI SAN upgrade production network (Dell MD3000i and PowerConnect &amp; ESXi 4)

  Hi all

  For the moment, I have a direct connection to my Dell MD3000i iSCSI SAN in ESXi 4 2 x host with no switch between the two, all of the virtual machine is within the SAN and running on both hosts.

  If I want to put a switch between the two and add one more iSCSI SAN so that the two SAN can be accessed / shared with the 3 ESXi 4 guests total, how should I approach the issue?

  any idea or guideline would be greatly appreciated.

  What I have to plan the time or can I change the old IP on the existing SAN iSCSI manually cable one by one without damage/alter the existing operation of the virtual machine on SAN? or I have to stop the virtual machine and then terminate the connection manually iSCSI session and then restart the host SAN?

  Thank you

  AWT

  Standard installation on the MD3000i is for a port iSCSI on each controller on a subnet and one on each controller to be on another.

  There have been people working successfully on a subnet, reported problems too.   I wish we were longer on our Vsphere upgrade, I'm not at a point but where I test things like Vmotion.

• Video and audio problem after upgrade of Sierra.

  After that each OS upgrade that I know it's going to be a few problems, so I wasn't surprised when this happened with Sierra. Most have been quickly resolved by common sense, but I have a biggie that remains. Mainly, but not only, it occurs during playback of videos and translates into a serious attack.

  When you use: -.

  Google Chrome Version 53.0.2785.116 (64-bit);

  When you watch a video, I hear a short hissing sound with a rising intonation (or sometimes 2 these sounds) then the text is added to a search bar (sometimes this text contains the words drawn from what someone says in the video!), or the video play suddenly disappears and a new tab opens and opens a page of Google apps. By clicking on the symbol left back page Apps and re - opens the original video that starts playing from the beginning again.

  This happens also in Chrome when it suffice to read a web page.

  In Safari 10.0 (12602.1.50.0.10)

  When occurs sound even watch videos in Safari 10.0 (12602.1.50.0.10), and the small text boxes appear at the top of the screen for a few moments contains comments such as "Hide this app", or "Undo that" before disappearing again.

  and audio in iTunes 12.5.1.21

  The same thing is happening in iTunes or when playing the iStore clips or songs in my library. The same small text boxes are displayed at the top middle of the screen containing cryptic messages such as "click 308' disappearing quickly. Sometimes the ' find and Replace window appears with more cryptic phrases in ' are are are ' not found! This occurs every 3-4 minutes.

  When you use Pages 6.0, a doc Pages will disappear and will appear in the folder from which it was opened. Or Graphic Converter 8, an image suddenly disappears and will open the Finder.

  I ran Etrecheck that says everything has been "excellent". I ran disk utility: first aid, who said there is corruption, he couldn't fix it and is running in recovery mode. I did, and the glitches always come back.

  Summat is false and I am not enough techno to understand (or maybe even explain it very well).

  Anyone bed this litany has an overview of what happens with a recourse?

  Thank you very much

  Graham

  Sorry, should be added the following: -.

  MacBook Pro (retina, 13 inches, end of 2013, recently upgraded to Mac OS Sierra.

  Processor 2.4 GHz Intel 15 8 GB memory

  Grahan

• Right-click on the image with link problem after upgrade to 11.0

  After the upgrade, whenever I do a right-click on an image with a link, it opens the link rather than opening a menu drop-down. Any idea on what is causing this behavior?

  OK, think about it. Extension: Tab Utilities was the origin of the problem. Uninstall completely solved the problem, disable it does not solve it.

• I've recently upgraded to El Capitan - biggest problem is timing removed all the entries in my previous ical. Any ideas how I can track down the file containing these essential documents and install in the new program?

  I've recently upgraded to El Capitan - biggest problem is timing removed all the entries in my previous ical. Any ideas how I can track down the file containing these essential documents and install in the new program?

  All calendars are enabled in the sidebar?

• 13 - a071ng: problems with the RAM upgrade - where is the crack?

  Hey there,

  so today I got my new x 360 a071ng HP. I wanted to upgrade my RAM from the standard 4GBs to 8GBs and replace the HDD with a SSD.

  Replace the HARD drive has been frank and I have not encountered any problems. But there is a problem: I can't find the slot of the RAM.

  The HP website is not saying something about a RAM memory that can be removed and nor does the Crucial site that actually says that there are two available slots.

  -Is anyone can help me? Is it hidden somewhere? Perhaps under the motherboard or the battery? Or is the site condition information simply false and there is no way to upgrade the RAM?

  Best of the Austria,

  Jannis

  Here is the Manual:

  Manual

  See Page 49. Memory access requires the removal of the motherboard I hate to say but if you on the hard drive, you were close. Just pay attention that HP will not honor the warranty if you damage the laptop in the process. Good luck and post if you have any other questions.

  If it's 'the Answer' please click on 'Accept as Solution' to help others find it.