hi, all!

Several days ago one of the my host periodically crashed into Purple screen.
Host - Supermicro SERVER SYS-6017R-N3RF4+: 2 x Intel Xeon E5-2630
ESXi 5.5

Error codes:

cpu15:33988)Warning:Unable to remove deleted USB storage adapters.
cpu21:33436) SCU 0SSL: esx_sci_driver_oem_parms_set: failed set OEM params 0x22

This host never had a USB devices!!
Whats going on?

Help plzzz

Hoping someone can help here as we haven't had much luck with HP support so far.

We have a C7000 chassis that has 2 HP VC FlexFabric 10Gb/24-Port Modules. We have 4 blades in the chassis running ESXi 5.5 Update 1.

On occassion we will lose pings to/from some of the VM guests running on the chassis. This does not happen to all VMs only some VMs some of the time. I am unable to reproduce the problem, I can only troubleshoot it as it happens.

We have narrowed down the problem to only the ESXi hosts on the chassis. I can migrate the VM amongst the chassis hosts and the problem persists, I migrate the VM to a host not inside the chassis and all is fine.

Right now my goto fix for the problem is to migrate the problem VM off the chassis.

We have done the following things to try and resolve this issue.

1. Upgraded all firmware for VC, OA and the Blades to the recommended firmware specs provided by HP. http://vibsdepot.hp.com/hpq/recipes/HP-VMware-Recipe.pdf

2. Re-Installed the VMWare hosts using HP's Custom ISO

3. Validated that all drivers conform to HP's recommendations http://vibsdepot.hp.com/hpq/recipes/HP-VMware-Recipe.pdf

4. We noticed that the Bay 1 flexfabric card is showing as subordinate/invalid. So we replaced the card in Bay 1 and it is still showing as insubordinate/invalid.

5. Validated that the network configuration in the chassis is accurate.

This is getting very frustrating to troubleshoot with HP support. They are convinced it's not a hardware problem even though the FlexFabric card in Bay 1 still shows insubordinate/invalid and the problem still persists.

Does anyone have any ideas on what else to try here?

Hi!

I started working on this preconfigured vmware esxi 5 with iscsi  Recently the iscsi failed and then 2 of my virtual machine went dead (one being a primary domain controller )..

One shows as invalid

and

when i try to start another it shows me the error: "Cannot open the disk '/vmfs/volumes/4f9bfdc3-4d04a919-b204-d4ae5288b40e/....../.....-000003.vmdk' or one of the snapshot disks it depends on.   " I logged in through ssh and couldn't find the /vmfs/volumes at all. Can anyone shed lights on what's happening?

Thanks in advance.

Rajan

When I restart the hosts, I have several network adapters that come up DISCONNECTED. Is there any way to force them to connect at start up?

After rebooting my PC, I try to connect to the IP address fro my Vsphere client and it says could not connect. I can ping all of the virutal servers successfully so I know they are all up and running. I just can't access my vsphere server. Anyone know what's going on, and how to fix this?

Hi All,

Has anyone seen this behavior before or could you help explain why this happening so that I can take the appropriate remedial action.

Basic summary of Infrastructure;

• vSphere 5.0 U2 with Ent Plus licences
• 30x ESXi 5.0 hosts - build 1254542
• HDS SAN - FC block storage (multiple 2TB LUNs) - SDRS cluster
• NetApp MetroCluster - NFS storage (multiple 5TB volumes) - SDRS cluster

We are currently tight on block storage capacity and are in the process of provisioning additional NFS storage - thin provisioning is widely use on both. On the HDS datastores I have the "Thin-provisioned LUN capacity Exceeded" alarm triggered, but there is still free space available on the datastore.

Yesterday I had the situation where I was unable to add any additional disks (even a small 10GB disk) or storage vMotion VM's between HDS datastores (except for 1 or 2 datastores out of 14) - NFS was unaffected. The error that I got in both cases was "The operation is not allowed in the current state of the datastore." The only way that I could resolve this was to restart the vCenter services. The first time everything worked for a few hours, and the the second time I restarted vCenter server completely.

Since then I have added an additional 2TB LUN to the SDRS cluster, and still have the "Thin-provisioned LUN capacity Exceeded" alarm triggered - but am able to storage vMotion to all HDS datastores. Capacity is currently as follows;

Name               FreeSpaceMB    CapacityMB

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

xxxxxxxxxxxxx      411980         2047744

xxxxxxxxxxxxx      391602         2047744

xxxxxxxxxxxxx      402413         2047744

xxxxxxxxxxxxx      427012         2047744

xxxxxxxxxxxxx      501918         2047744

xxxxxxxxxxxxx      394800         2047744

xxxxxxxxxxxxx      397538         2047744

xxxxxxxxxxxxx      398614         2047744

xxxxxxxxxxxxx      459313         2047744

xxxxxxxxxxxxx      306059         2047744

xxxxxxxxxxxxx      378631         2047744

xxxxxxxxxxxxx      392283         2047744

xxxxxxxxxxxxx      382561         2047744

xxxxxxxxxxxxx      396588         2047744

xxxxxxxxxxxxx      302924         2047744

So the questions are;

1. Has anyone seen this before or did vCenter just get into a wobble?
2. Do I need to be concerned about anything major?
3. Are there any other areas that I should check?

Thanks,

Jon

Hi All,

I'm facing same issue for Windows Virtual Machine. Recently I increased disk size from 1.8 TB to 2 TB (As per user request) and later snapshot backup failing with maximum file size exceeded error.

VM is running with Windows 2008 R2 - If i shrink disk size from OS level - how it will be recognized at vSphere? (I mean vmdk size will be still 2 TB right)

Thin disks - Let us say I converted this disk as thin and there is 1.7 TB data inside of the disk - will the snapshot successful? - if yes then it is not looking for vmdk size and limits given in KB-1012384 are not significant.

Apart of moving to vSphere 5.5 and V2V converter, do we have any other solutions or suggestions?

Changing snapshot directory to 4 TB data store - will it beat the snapshot limitations of 2032 GB?

Need your thoughts and inputs to provide POA to customer.

Message was edited by: a.p. - branched to a new discussion

Trying to upload vmdk files to detester from external hard drive.  Eventually the server locks up and we can no longer access it and have to force the server to shut off and then turn it back on again.

Hi,

I need a Linux VM with NVIDIA OpenGL 4.x support, so after having read about vDGA I have purchased an NVIDIA K600 and put it in our Dell PowerEdge r720, configured it for passthrough and assigned it to a VM running Red Hat Enterprise Linux 6. I have also configured the VM with pciHole.start=2048, without really knowing why, other than documentation states that I should do this, if the VM has more than 2GiB, which it does - it has 8GiB. After rebooting the VM I can see the card with lspci:

[root ~]# lspci |grep NVIDIA

13:00.0 VGA compatible controller: NVIDIA Corporation GK107GL [Quadro K600] (rev a1)

13:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)

I have installed the NVIDIA recommended driver 340.24 for the NVIDIA Quadro K600 and the driver installation proceeds without any incidents. After this I can also see the driver is loaded:

[root ~]# lsmod |grep -i nvidia

nvidia              10533126  0

i2c_core               31084  6 nvidia,i2c_piix4,nouveau,drm_kms_helper,drm,i2c_algo_bit

However, when I try to start X at first it fails to find the device, after helping it by setting the BusID in /etc/X11/xorg.conf I get the following error when starting X:

After this I found the following in the dmesg log:

[root ~]# dmesg | tail -4

nvidia 0000:13:00.0: irq 68 for MSI/MSI-X

NVRM: RmInitAdapter failed! (0x23:0x2f:566)

NVRM: rm_init_adapter failed for device bearing minor number 0

NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5

So, the GPU is there, the driver can load, but things don't quite work.

I have attached the vmx file for my VM.

I desperately need your help to get this working :-)

Best regards,

Thomas

I've searched, googled, tried everything I can find online and you simply cannot install Update Manager on Server 2012R2.

Yes, .NET 3.5 and 4.5 are installed. Am I missing something here?

For some reason I can't paste anything in the text box, so please bear with me...

I moved 3 physical HDD's from an ESXi 4.1 to an ESXi 5.5 server. The first 2 160GB disks went fine, but than I switched one of the 160GB disks with a 1TB disk (also containing an existing datastor) but I aacidently made a mistake in the RAID controller, so it removed the partition table of this 1TB disk. If read KB2046610 of the VMware Knowledge Base, and I managed to get a partition on the disk, I can also see the original datastore label while running the script in the CLI, it's called "datastore3", and it is present. But I can't get it to show in vSphere, refreshing or rescanning won't work... Adding new storage doesn't work because it doesn't ask me for the 3 options "keep signature, resignature or format" it goes straight to the "VMFS5 or VMFS3" choice. If I choose one of these it goes toe the next step and shows that there is a VMFS partition present using the entire disk, but if I go on from this step it will format the disk (I didn't do that of course).

Once again I'm sorry that I can't paste anything, it makes it very hard for me to explain the issue and the steps that I've already taken in attempt to solve this issue :S But I hope it's clear so that someone might be able point me in the right direction...

ESXi5.5 update 1 (1623387) licensed

Dell PowerEdge R710 with the latest firmware/BIOS updates

We've been having a lot of issues with the Broadcom NetXtreme II BCM5709 vmnics.  They have the latest firmware and driver.  Instead of upgrading our 4.1 environment, we decided to migrate to 5.5.  So the ESXi 5.5 on the servers is a clean install.

~# ethtool -i vmnic4

driver: bnx2

version: 2.2.5d.v55.2

firmware-version: 5.0.9 bc 5.0.6

The LEDs on the bad vminics are on and blinking.  We swapped the physical NICs to different sockets without success.  We even called Dell and had them replace the motherboard, raiser card and nics but still the links are down.  The odd thing is we also have two other R710/ESXi 5.5 servers with the same BCM5709 nics and don't see this problem at all.   In fact, there is a working dual port 5709 in the same server but not the nic in slot 2.  We also swapped the physical switch and cables but no avail.  So I am convinced the issue is with ESXi.  I googled and checked the vmnic related KB articles but none of them has helped us so far.   I would appreciate it you can give us any guidance on this issue.

Thanks  

Hello, I've seen this a few times in my environment and I'm wondering why.

When looking to extend a VMDK on a VM, whether thin or thick provisioned, the VMDK shows that I am able to grow the disk larger than the free space available on the LUN/Datastore. After investigation I have determined the VMDK is showing free space available on the SAN as well as free space on the LUN. If I create a LUN and do not map it to a host, the available space to expand the disk drops by the size of the LUN I created.

The free space on the SAN is not allocated to any ESX host. I have a 5 TB datastore with 1 TB free space. When attempting to grow the VMDK, it is showing that I have 11 TB available. When I look at the free space on the SAN, I have 10 TB free. So, even though the free space is not mapped as a LUN to this ESX host, the host is still seeing that there is free space. As a result, when trying to grow the VMDK it obviously errors out with insufficient space. I should only be able to grow the extra 500 GB and that's it.

Why is this host even seeing that free space is there at all? When growing the VMDK, it should only see the space that is available to the LUN the VMDK resides on.

I'm running ESXi 5.5 Dell Customized A01 on this particular host, however on another host I am running ESXi 5.1 1064591, which is a VMware build no Dell customization. The SAN I have is a Dell MD3620i, which is similar to an IBM DS series from what I've read. It's some variant of an LSI controller.

I'm wondering if anyone can shed some light on what I'm seeing here before I check with support.

Thanks in advance.

I have a situation where someone had an older vSphere 4.x cluster. The VMs were hosted off of a iSCSI SAN controller to the nodes in the cluster.  The volume was 260GB originally when I made it a few years back.   Subsequently they have added enough VMs that they needed to expand.  They expanded the LUN capacity to 3TB, but was never able to expand the partition.   With VMFS3 this is an issue.

Seems if you epand the LUN, EVEN IF you NEVER expand the partition, your systems, if they unmount the volume can never mount it again.

This apparently went on for some time where over time more systems would not "access" the LUN.... and after a power outage, no system could then access the dozens of VMs.

Now I need to find a way to mount that 3TB iSCSI LUN, even if read only, long enough to mount the 260 of VMs off of it to NFS share i have ready.

Goal: map iSCSI LUN to Windows / Linux system.  Mount the volume RO.  Copy data to NFS export. Destroy and rebuild the data on new iSCI VMFS5 lun.

I can mount the LUN to CENTOS system and parted shows the 3TB LUN but primary partition only 260GB.  So I see the data as expected.   Now I tried to compile 'vmfs-tools-0.2.5"  but get compiler errors.  Nothing of any help or note. I tried ubuntu and CENTOS48 also and errors not much help.

Is their another, more simplistic way to get this accomplished?

Thanks,

what is the process to upgrade the hba bios on these ibm x3850 servers? Is it a vib install without reboot/pends reboot or does it need to be shutdown and updated via dos?

Board: Supermicro X9SRi

CPU: Intel E5-2650v2

LSI SAS 9271-8i   (tried Adaptec before, had the same error)

ESXi 5.5.0 Up 1

HELP, can't get rid of this error (see Screen attached). Sometimes the host hangs up, so i must reboot. The error and hangup even occurs when no vm is running...

Is there some BIOS setting i must adjust? or some special configuration for this board? I'm out of ideas :-(

I'm about 90% done with a new vSphere deployment, and we've just noticed that our IIS web application that we have is having extreme slowness, even some timeouts.  Our QA team says that a particular process they run typically completes in 1-5s on our previous, aging, physical servers and now are doing 45s-1m on the vm's.

Everything else seems fine. Normal server operations seem to be performing fine.  CPU, Mem, Disk performance are all on the low side, even during the QA process.

The servers in question have 10vcpu, 16gb mem, NetApp 10g iSCSI SAN.  Physical servers are Cisco UCS B200M3 Servers, and are ridiculously under utilized.

Running with a vDS but also has same problem with Standard switch.

Development is of course saying its infrastructure/networking.

The only indication of an issue that I can actually replicate is that if I ping one vm to another, the first few pings drop, and then it will eventually start a solid continuous ping.

If anyone has seen anything like this, please let me know.

Thanks!

Hi Guys

So we have an issue with the error "Unable to add extent to filesystem : VMFS volume missing physical extents" when we try and extent a VMFS 5.6 datastore using ESXi 5.5 directly on the host as well as through VCS.

The environment:

EMC VNXe 3100 (ISCSi)

3 hosts

Currently the Datastore comprises of about 10 LUNs with a total capacity of about 11TB.

There are running VMs on it, and since the space required is as much as it is, we cannot just move it off and redo the LUNs.

I have read the links on previous posts regarding ATS, and it is supported on the DS as well as the SAN.

Not sure what I am missing.

Here is the full error:

Call "HostDatastoreSystem.ExtendVmfsDatastore" for object "datastoreSystem-29" on vCenter Server "***************" failed.

Operation failed, diagnostics report: Unable to add extent to filesystem : VMFS volume missing physical extents

haii everyone, this is johnwoods, this forums are excellent and they give huge knowledge and i would like to start a discussion on how to install and upgrade VMware sever 2 and some commons issues or errors.

If any of you guys have sound knowledge about that, kindly share

worldaroundu

Hey there,

I have a small problem. I deleted a datastore(LUN) and then detached it. I know I should have unmount it first but I didn't.

When I see esxtop u I can see the device but when I esxcli storage filesystem list I don't see it.

It bothers me because storagerm.log gets spamed with the naa.xxxx devices I deleted and detached:

2014-08-29T12:01:42.673Z: Skipping device naa.6005076300810119b80000000000002d either due to VSI read error or abnormal state

2014-08-29T12:01:42.673Z: Skipping device naa.6005076300810119b800000000000030 either due to VSI read error or abnormal state

2014-08-29T12:01:42.673Z: Skipping device naa.6005076300810119b800000000000031 either due to VSI read error or abnormal state

2014-08-29T12:01:42.674Z: Skipping device naa.6005076300810119b800000000000032 either due to VSI read error or abnormal state

2014-08-29T12:01:42.674Z: Skipping device naa.6005076300810119b80000000000003b either due to VSI read error or abnormal state

Is there a way to remove the devices permanently without rebooting the host?

I'm using vCenter Server 5.1.

Thanks in advance.

Oliver