LUN ESXi 5.1/store data not visible in trying to 'add storage '.

I just added two 300 GB hard drives in my RAID, reconstructed and checked that the size has increased in OpenManage, but I am unable to actually increase the size of the data store residing on the RAID from the vSphere client. See photos attached. In photo 1, you can see the new size in OpenManage. In photo 2, you can see the data store I want to enlarge. Refresh or rescan everything has no effect. When I click Add storage, you can see in Picture 3 that there is no warehouses to choose. It's the same thing in November when I added a drive, but it was under warranty and a remote Dell technician in and did some fancy table/file system partitions while SSHed in to solve the problem. What I have to do the same thing or there at - it another way? If the former, how?

I solved this through the command line. I followed the instructions at more a local data store from the command-line in vSphere, ESXi 4.x and 5.x.

If you were stuck in the GUI as I was and you will find the daunting command line, just pay attention to what each step says you and document what you do as you do, so you don't get lost. If you learn what you are doing as you do, it just makes sense.

Tags: VMware

Similar Questions

  • my browser cannot open google and facebook and other https sites that it does not open even the app store does not work, I tried to change my DNS google DNS and disable IPv6 but still no use, help PLZ!

    my browser cannot open google and facebook and other https sites that it does not open even the app store does not work, I tried to change my DNS google DNS and disable IPv6 but still no use, help PLZ!

    You may have installed one or more variants of the malware "VSearch' ad-injection. Please back up all data, and then take the steps below to disable it.

    Do not use any type of product, "anti-virus" or "anti-malware" on a Mac. It is never necessary for her, and relying on it for protection makes you more vulnerable to attacks, not less.

    Malware is constantly evolving to work around defenses against it. This procedure works now, I know. It will not work in the future. Anyone finding this comment a couple of days or more after it was published should look for a more recent discussion, or start a new one.

    Step 1

    VSearch malware tries to hide by varying names of the files it installs. It regenerates itself also if you try to remove it when it is run. To remove it, you must first start in safe mode temporarily disable the malware.

    Note: If FileVault is enabled in OS X 10.9 or an earlier version, or if a firmware password is defined, or if the boot volume is a software RAID, you can not do this. Ask for other instructions.

    Step 2

    When running in safe mode, load the web page and then triple - click on the line below to select. Copy the text to the Clipboard by pressing Control-C key combination:

    /Library/LaunchDaemons

    In the Finder, select

    Go ▹ go to the folder...

    from the menu bar and paste it into the box that opens by pressing command + V. You won't see what you pasted a newline being included. Press return.

    A folder named "LaunchDaemons" can open. If this is the case, press the combination of keys command-2 to select the display of the list, if it is not already selected.

    There should be a column in the update Finder window. Click this title two times to sort the content by date with the most recent at the top. Please don't skip this step. Files that belong to an instance of VSearch will have the same date of change for a few minutes, then they will be grouped together when you sort the folder this way, which makes them easy to identify.

    Step 3

    In the LaunchDaemons folder, there may be one or more files with the name of this form:

    com Apple.something.plist

    When something is a random string, without the letters, different in each case.

    Note that the name consists of four words separated by dots. Typical examples are:

    com Apple.builins.plist

    com Apple.cereng.plist

    com Apple.nysgar.plist

    There may be one or more items with a name of the form:

    com.something.plist

    Yet once something is a random string, without meaning - not necessarily the same as that which appears in one of the other file names.

    These names consist of three words separated by dots. Typical examples are:

    com.semifasciaUpd.plist

    com.ubuiling.plist

    Sometimes there are items (usually not more than one) with the name of this form:

    com.something .net - preferences.plist

    This name consists of four words (the third hyphen) separated by periods. Typical example:

    com.jangly .net - preferences.plist

    Drag all items in the basket. You may be prompted for administrator login password.

    Restart the computer and empty the trash.

    Examples of legitimate files located in the same folder:

    com.apple.FinalCutServer.fcsvr_ldsd.plist

    com Apple.Installer.osmessagetracing.plist

    com Apple.Qmaster.qmasterd.plist

    com Apple.aelwriter.plist

    com Apple.SERVERD.plist

    com Tether.plist

    The first three are clearly not VSearch files because the names do not match the above models. The last three are not easy to distinguish by the name alone, but the modification date will be earlier than the date at which VSearch has been installed, perhaps several years. None of these files will be present in most installations of Mac OS X.

    Do not delete the folder 'LaunchDaemons' or anything else inside, unless you know you have another type of unwanted software and more VSearch. The file is a normal part of Mac OS X. The "demon" refers to a program that starts automatically. This is not inherently bad, but the mechanism is sometimes exploited by hackers for malicious software.

    If you are not sure whether a file is part of the malware, order the contents of the folder by date modified I wrote in step 2, no name. Malicious files will be grouped together. There could be more than one such group, if you attacked more than once. A file dated far in the past is not part of the malware. A folder in date dated Middle an obviously malicious cluster is almost certainly too malicious.

    If the files come back after you remove the, they are replaced by others with similar names, then either you didn't start in safe mode or you do not have all the. Return to step 1 and try again.

    Step 4

    Reset the home page in each of your browsers, if it has been modified. In Safari, first load the desired home page, then select

    ▹ Safari preferences... ▹ General

    and click on

    Set on the current Page

    If you use Firefox or Chrome web browser, remove the extensions or add-ons that you don't know that you need. When in doubt, remove all of them.

    The malware is now permanently inactivated, as long as you reinstall it never. A few small files will be left behind, but they have no effect, and trying to find all them is more trouble that it's worth.

    Step 5

    The malware lets the web proxy discovery in the network settings. If you know that the setting was already enabled for a reason, skip this step. Otherwise, you should undo the change.

    Open the network pane in system preferences. If there is a padlock icon in the lower left corner of the window, click it and authenticate to unlock the settings. Click the Advanced button, and then select Proxies in the sheet that drops down. Uncheck that Auto Discovery Proxy if it is checked. Click OK, and then apply.

    Step 6

    This step is optional. Open the users and groups in the system preferences and click on the lock icon to unlock the settings. In the list of users, there may be some with random names that have been added by the malware. You can remove these users. If you are not sure whether a user is legitimate, do not delete it.

  • Visible data VMFS store on 3 of the 6 armies. 3 the remaining hosts see LUNS, status is mounted, but the data store is not visible.

    As the title suggests, all hosts see LUNS... can't understand the question. Here is a shot of the vmkernel.log captured from the server, as it was a new analysis (which translates into a loop of activity in the log file and hard + 10 minutes without change for storage).

    The SAN is preesnting LUN and successfully... so it must be on the host side. In an act of desperation, yesterday I reinstalled ESXi on a troubled host. He was able to see the data stores. Today, they were more visible.

    Thanks in advance for any help.

    VMkernel.log:

    (2013 06-26 T 13: 07:56.778Z cpu1:15038) score: 558: entered reading of TPG (hdrlba = 1) doesn't have the 'naa.600144f0f9e18d0000005160917e0001': i/o error

    (2013 06-26 T 13: 07:56.778Z cpu1:15038) Partition: 661: primary gpt table read failed on 'naa.600144f0f9e18d0000005160917e0001 '.

    (2013 06-26 T 13: 07:56.778Z cpu1:15038) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabd of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x 2 D:0 x 0 x 0 possible P:0-data: 0 x 6 0 29 x 0 x 0.

    (2013 06-26 T 13: 07:56.863Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.005Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.063Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410022110b10 network netsched.pools.persist.iscsi associated pool resource

    (2013 06-26 T 13: 07:57.063Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: 0x410022110b10 network Tracker id 1 tracker.iSCSI.192.168.70.10 associated with socket

    (2013 06-26 T 13: 07:57.091Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.234Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.378Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.520Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 07:57.563Z cpu1:8193) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

    (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is marked as "ONLINE."

    (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

    (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 192.168.70.50:49286 r L: 0: 192.168.70.10:3260]

    (2013 06-26 T 13: 07:57.578Z cpu8:8603) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' on the way 'vmhba38:C0:T0:L0' failed: H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 6 0 29 x 0 x 0. Bill: NO

    (2013 06-26 T 13: 07:57.578Z cpu8:8603) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabd of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 6 0 29 x 0 x 0.

    (2013 06-26 T 13: 07:57.578Z cpu8:8603) ScsiCore: 1483: power - on delivery took place the naa.600144f0f9e18d0000005160917e0001

    (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 4)

    (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

    (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 192.168.70.50:49286 r L: 0: 192.168.70.10:3260]

    (2013 06-26 T 13: 08:07.901Z cpu10:8778) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

    (2013 06-26 T 13: 08:07.901Z cpu10:8778) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabe of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x 2 D:0 x 0 x 0 possible P:0-data: 0 x 6 0 29 x 0 x 0.

    (2013 06-26 T 13: 08:07.988Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.130Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.273Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.415Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.558Z cpu10:8805) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.558Z cpu10:8805) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

    (2013 06-26 T 13: 08:08.696Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.837Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:08.980Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.265Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.409Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.551Z cpu10:8671) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.565Z cpu10:8202) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

    (2013 06-26 T 13: 08:09.694Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.838Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:09.980Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.265Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.409Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.551Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.551Z cpu10:8202) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

    (2013 06-26 T 13: 08:10.673Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410022110b10 network netsched.pools.persist.iscsi associated pool resource

    (2013 06-26 T 13: 08:10.673Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: 0x410022110b10 network Tracker id 1 tracker.iSCSI.192.168.70.10 associated with socket

    (2013 06-26 T 13: 08:10.694Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.838Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:10.979Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:11.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

    (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is marked as "ONLINE."

    (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

    (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 192.168.70.50:59905 r L: 0: 192.168.70.10:3260]

    (2013 06-26 T 13: 08:11.191Z cpu12:8204) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' on the way 'vmhba38:C0:T0:L0' failed: H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 6 0 29 x 0 x 0. Bill: NO

    (2013 06-26 T 13: 08:11.191Z cpu12:8204) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabe of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 6 0 29 x 0 x 0.

    (2013 06-26 T 13: 08:11.191Z cpu12:8204) ScsiCore: 1483: power - on delivery took place the naa.600144f0f9e18d0000005160917e0001

    volumes/vmfs / #.

    Finally I thought of her. The switches have been on a MTU of 9000. I ran each port to the max 9216 and everything works perfectly. A little shocked by him but I'm just glad it is resolved.

  • DBMS - data not visible for read only account users.

    I created below to know the status of my lots which run on server every Sunday.

    CREATE OR REPLACE VIEW CAFDB_REFRESH AS
    SELECT
    log_id,
    owner,
    TO_CHAR (log_date, ' ' DD-MON-YY HH24:MI:SS) TIMESTAMP.
    job_name,
    status,
    ERROR #.
    run_duration,
    INSTANCE_ID,
    additional_info
    Of user_scheduler_job_run_details;

    It works fine and I am able to get the information.
    now, to make it visible for read only account users - using «grant select» I gave access and created also means public.

    but it shows only the names of columns in read only account data.

    How to make this visible to read only account?

    Please guide.

    Views USER_ will have only the objects owned by the user executing the query... In your case, it will be only schedules made by the user.

    You will need EU ALL_ or view s/n (all_scheduler_job_run_details)

  • How Windows App Store does not start (I tried "everything")

    It's just my story. The OP may be completely different.

    The research on the net I saw that many people suffer the problem described, that is to say the App Store apps and win 8 crashing. So I was hoping that a solution could be found.

    That's all just amazing! I have the same problem with exactly the same results. It doesn't seem to be a solution without refreshing. I can't access the Windows store, I'm stuck with Windows 8 and cannot move to 8.1. I tried several times to pass to 8.1 when I could go to the store, but it failed every time with an error code OxC1900101-Ox20017. Any suggestions as to what this error is and how to fix it. So, I seem to be stuck with Windows 8 until Windows 9 comes out. I am not convinced that this will present all kinds of new questions. I can't understand why Microsoft cannot fix this easily because he seems to have been going on for at least a year. I hate the idea of how much time I wasted on this. My only saving grace is that I can return to my laptop with Windows 7... happiness!

  • ButtonField is not visible in the Simulator after adding to the HorizontalFieldManager?

    Hi iam trying to view an EditField and and a 'go' button beside it in the same line.  So I added them to horizontal FieldManager but in sumulatro only the search is coming and button is not visible.  If I add the button to directly _mainscreen that it is displayed in the following line. So, how do I make visible button after adding to the HorizontalFieldManager?

    Please give your support. Thanks in advance.

    private BrowserFieldDemo()
{
EditField edit = new EditField("", "search",10, EditField.FILTER_DEFAULT);
HorizontalFieldManager searchBar = new HorizontalFieldManager();
searchBar.add(edit);
searchBar.add(buttonField);
_mainScreen.add(searchBar);
pushScreen(_mainScreen);
}

    You can also limit the size of your EditField to leave room for your BitmapField.  In theory, you need only substitute getPreferredWidth() for your EditField, but you may have to substitute layout() as well.

    You can see an example of the fact of a ButtonField in this thread.

    http://supportforums.BlackBerry.com/Rim/Board/message?board.ID=java_dev&message.ID=7430

    You can also find this useful Thread If you want to go in the direction of Manager:

    http://supportforums.BlackBerry.com/Rim/Board/message?board.ID=java_dev&message.ID=3745

    I found the code snippet according to who uses the layout to make sure you have 20 pixels to the right of the field:

    Protected Sub layout (int maxWidth, maxHeight int) {}
    Super.Layout (Display.getWidth () - 20, this.getHeight ());
    setExtent (Display.getWidth () - 20, this.getHeight ());
    }

  • Windows 7 - wireless adapter or network is not visible

    Hello
    Recently I've updated from windows xp to Windows 7. When you use windows xp, I have access to my router wirelessly from my laptop. But in windows 7, the wireless network and the adapter itself is not visible (I tried in the taskbar, Panel-> Network and sharing Center). My laptop Dell Inspiron 1520 and wireless (earlier) is Intel 4965AGN. I tried to install a few drivers, but no permits. I don't know what the problem is? There is a problem with the driver / card wifi / Windows 7. Kindly help.
    Thank you
    Prabhu.M...

    Hi Prabhu,

    Welcome to the community Microsoft and thanks for posting the question.

    According to the description, you are having problems with the wireless network not available.

    Perform the steps suggested by Kevin Hau from the link below and see if it helps.

    http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-networking/Windows-7-wireless-connection-problem-no-wireless/43f61a9c-069b-49AB-9F5B-f52ec2b1ef7e

    Meet us if you experience problems with the wireless network connection or any other problem of Windows, and we would be happy to help you.

    Good day!

    Hope this information helps.

  • Target iscsi ESXI 5.0, active path connected, mounted, are not not in the data store data store

    HI -.

    I am looking for help to point me in the right direction.  This problem occurred after a reboot of the system.

    I'm in vmware esxi essentials 5.0.0 821926

    I use the starwind software as my iSCSI target

    I use ISCSI to connect to my server from storage to the esxi hosts.

    I have 2 warehouses of data showing inactive under clusters of data storage and the data store.  I have a third-party data store on the same server that is loading properly.

    I currently have the same behavior on three esxi hosts:

    under configuration - storage adapters is the ISCSI path is active. Data warehouses appear under devices and mounted.  In data warehouses, they are inactive. On the same storage server

    on the starwind Server - I have

    built a new target

    removed and added the databases to the new target

    Changed the IP address of the target.

    On Esxi hosts, I removed the ISCSI server, discover places BOF dynamic and static and added under the same or IPs news discovery

    I can restart esxi hosts & storage servers and get to that same point.

    Whenever I find myself in the same place - course assets, devices mounted, inactive in data warehouses

    I don't know what else to share, let me know what you need to know to help out me.

    Thank you

    Dylan

    OK, incase someone crosses my ramblings, it may help.  My original question was warehouses of data that would not rise.  They were visible as devices in the area of storage under devices and as devices in the scsi adapter.

    When I would try to force mount them, add storage, keep the signature, mount they wouldn't mount.  I did some research and my question was after a failed mount attempt strength as got data attached as snapshots warehouses.  I then mounted force them and he tells will data warehouses and I got them back.

    I followed this KB to identify and resolve the problem

    manipulation of vSphere detected as snapshot LUN LUN (1011387)

    When it was over, I tried to add vms back and found a new show.  Power of vms would expire.  the vmkernel.log showed;

    2014 05-27 T 07: 20:40.010Z [verbose 'Vmsvc' 564D7B90] Vmsvc: filtering Vms: ignored not ready to request power state vm vim. VirtualMachine:75

    AND

    (2014 05-27 T 03: 45:47.821Z cpu4:2052) NMP: nmp_PathDetermineFailure:2084: SCSI cmd RESERVE failed on the vmhba35:C0:T1:L0 path, booking on eui.cff548d1952b1e4c of device status is unknown.

    I had latency huge read write showing upwards, 3K and more

    After several searches, I had in the ESXShell and found that there is no conflict of booking.

    On a whim, I took inventory all virtual machines that are now inaccessible.  I then added a DOS virtual machine. Alto! the latency down to version 1.2 a.7 ms for all data warehouses.

    ultimately the instructions said you may need to add virtual machines in the inventory, but does not remove all virtual machines first.  I was grabbing vms that were not in stock, so I didn't remove the old virtual machines in the inventory.

    A recruit Mennonites, Yes.

  • Disk groups are not visible cluster. vSAN datastore exists. 2 guests (on 8) cluster do not see the vSAN data store. Their storage is not recognized.

    http://i.imgur.com/pqAXtFl.PNG

    http://i.imgur.com/BnztaDD.PNG

    Do not know how even tear it down and rebuild it if the disk groups are not visible. The discs are in good health on each host storage adapters.

    Currently the latest version of vCenter 5.5. Hosts running 5.5 build 2068190

    Just built. Happy to demolish and rebuild. Just do not know why it is not visible on the two hosts and the disk groups are only recognized 3 guests when more are contributing. Also strange that I can't get the disk groups to fill in vCenter. I tried two different browsers (chrome and IE).

    I have now works.

    All the identical 5.5 relies on ESXi hosts. All hosts are homogeneous CPU/sum of the prospects for disk controller / installed RAM/storage.

    I have work. I had to manually destroy all traces of the vSAN on each single to help host node:

    (1) put the hosts in maintenance mode and remove the cluster. I was unable to disable vSAN in the cluster, I made on each node host (manually via the CLI below) then disconnected web client vCenter and return to finally refresh the ability to disable on the cluster.

    esxcli vsan cluster get - to check the status of each host.

    esxcli vsan cluster drop - the vSAN cluster host.

    storage of vsan esxcli list - view records in the individual host group

    esxcli vsan storage remove-d naa.id_of_magnetic_disks_here - to remove each of the disks in the disk group (you can ignore this using the following command to remove the SSD only falling each disc in this host group).

    esxcli vsan storage remove s naa.id_of_solid_state_disks_here - this is the SSD and all the magnetic disks in a given disk group.

    After that, I was able to manually add hosts to the cluster, leave maintenance mode and configure the disk groups. Aggregated data of the vSAN data store is correct now, and everything is functional.

    Another question for those of you who still read... How to configure such as the VM storage strategy that migrates towards (or inspired) the vSAN data store will immediately resume the default storage policy, I built for VSANs?

    Thanks for anyone who has followed.

  • How to span multiple LUNS on one (or less) data store (s) in Vmware ESXi 4.1 vSphere environment?

    Hey guys -.

    I currently have 2 hosts ESXi (version 4.1u3), 1 vCenter Server and 1 EMC VNXe3300 SAN (20 to via iSCSI) that make my virtual environment.

    On the EMC is, you create VMware Datastores (which have a limit of 2 TB) then connect these data storage to VMware ESXi hosts.  Once logged in, would continue it the process through the Add Storage Wizard via VMware to connect the disk/LUN storage via iSCSI.  Ultimately, the Lun (s) would then be accessed through the virtual environment (in the Configuration > storage > data warehouses) as generally expected.

    Due to the limit of 2 TB (both on the CEM, Version of VMware and VMFS3) on data warehouses, I find myself with having several data warehouses being created on the side of the EMC and VMware (see photo) appearance.  I know that's not rectifiable via CEM level, but I was wondering if there was any way for me to bring together all these data stores on the side of things VMware.  This way rather than navigate to Configuration > storage > data warehouses and separate iSCSI indicator 6 data warehouses, it would just be a (or more, but less than the existing) data store; It would then extend in all actual data stores that I would.

    I don't know what the appropriate terminology is used to describe it, but I hope someone can help me to what I want to achieve.  Or at the very least, can you please steer me in the right direction.  If this isn't something that can be achieved or it is discouraged, what are the other options which would be recommended?

    Thanks for the help.

    Have a look here: VMFS extended - are they bad, or simply misunderstood? VMware vSphere Blog - VMware Blogs

  • not visible on the ESXi LUN iSCSI hosts

    So I have a bit of a strange and hoping the community can help me to understand. In my lab at the House, I have 3 x ESXi 5.1 Build 799733 hosts x 2 guests are the same hardware (BUD Intel) and the other host an old HP flat desk. I am running CE Nexenta 3.1.3.5 on a Microserver HP which provided the iSCSI storage to HP desktop computer. The 2 new Intel NUC VMware hosts however, I am unable to get any iSCSI storage visible to them. Software iSCSI adapter is enabled, peut vmkping storage to the host and the target will appear on the static discovery tab. The configuration appears to be identical between the 2 However, the hardware is different... I have a new analysis on the host and no devices appear. Now the obvious answer is there must be a security issue on the side of Nexenta... but the 3 hosts are all part of the same group initiator. Confirmed and copied the IQN name over and over again. I still think that this is maybe a matter of Nexenta, but maybe it's something else.

    Check the vmkernel.log file contains the following information after a new analysis...

    (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1547: device rescan time 17 msec (total number of 5 devices)

    (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1550: Filesystem probe time 85 msec (4 of 5 surveyed devices)

    (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

    (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

    (2013 06-09 T 23: 49:06.412Z cpu3:2931) SFS: 4972: pilot no. FS claimed "on the remote control": unsupported

    Anyone got any ideas?

    Problem solved.

    Appears that it was a problem of connection iSCSI ports. There is only a single teddy bear in each of these hosts and allowing the port bindings vmkernel on initiator iSCSI under 'Network Configuration' result not being iSCSI target devices is not visible. Removed the vmkernel port binding and made a new analysis. Cameras then showed upward.

  • 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

  • Store data and LUN id

    Hello

    I have a strange problem with my storage.

    I don't see the data store which is mounted on my ESXi. esxcfg-scsidevs - m also doest show LUN/store data.

    but when I see with esxcfg-mpath - l. I can see that lun. In addition, San, I see that it is mounted.

    If I see on VC under devices I can find the logical unit number id, but I do not see this LUN in the data store.

    can someone guide me here, how I can find this data store.

    The following KBs will help you

    VMware KB: Recovery of a lost on a VMFS volume partition table

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

    Delete/recreate the partition tables does not affect the data but at any time if you feel that you need help to recover the lost partition table, connect a business with VMware Support and request their assistance.

    All the best!

    -f10

  • data store is not big as the player

    Hello

    I just install ESXi 4.1 update 3 on my fujitsu rx300 S3 with 6x500GB ground mounted in a RAID5 configuration, 2 x 1.6 Ghz XEON 5110 and 8 GB of memory.

    The ESX has been successfully installed except the data store: space it is not as big as the player: capacity data store 274 GB then as drive capacity 2, 5 TB.

    The VMWARE KB to extend the data store does not work: it did not drive LUN.

    I don't know how to extend the data store OR create a second, which will be accessible to another ESX.

    Thank you

    Limit is 2 TB less 512 bytes for ESXi 4.1, trying to remove a 500 GB drive in RAID 5 configuration and try to create the data store.

  • 2 ESXi hosts... Nor can see each stores data to other hosts

    All, morning

    I have a little problem with a cluster of 2 servers ESXi 4.1.  They are connected to a VC and Enterprise Plus license.

    We have about 15 stores of data, called san01, san02,... san15.  ESXi hosts, we'll call it ESXi-01 an ESXi-02.  As I said - they are in an active HA with DRS cluster.  They are part of a disaster recovery test, we are performing.  For some reason, only the host on which each data store has been added (add storage, select LUNS, use the existing signature) can use this store.  It does not appear when a new analysis VMFS on another host (or automatically as it should).  If you try to import the same LUN to host opposed when it is already mapped to the one, the only available option is to reformat the partition, which is not good as there are a several machines on each Lun.

    So now I have a host with san2, 3, 5, 7 & 9 and all the others are on the other host.  Of course, they are unable to balance the load using vMotion & DRS.  It makes me crazy - any suggestions please?

    Just FYI, the hosts are the IBM HS22 blade, cards QLogic FC and the SAN is a unit of IBM XIV.  In our main site (live), we have a XIV with all LUNS alive and running on a cluster of 12 ESX4 host.  The data is replicated on the XIV in our disaster recovery site using the iSCSI Protocol and the links were broken between the 2 sites at the beginning of the excersise, allowing data replicated to our Dr site must be set to read/write and connected to hosts via FC.  Both hosts use the same configuration as the other and have the same drive mappings to the SAN.

    Look forward to hearing your ideas!

    Dave.

    As I understand it, the issue could be caused by the LUNS being recognized as LUN snapshot (see the ESXi host logs)

    In this case, you could try to force mount the LUNS. See http://kb.vmware.com/kb/1011387

    André

Maybe you are looking for