uploading file to SR. service ID is cesm-20171219.
↧
Re: could not power on VM
↧
Re: Unable to delete or unmount a datastore because file system is busy
Hi Sam,
I've came across similar incident few days back,but the only way is rebooting the host.
↧
↧
Re: Resetting vCenter Server Appliance password
↧
Re: I Could one path to LUN
iSCSI or Fibre Channel SAN ? Ours is FC storage
What type of SAN storage ? IBM SVC
All ports are 'up' ? Yes... host can all the paths for other LUN's.
If iSCSi - use VMKPING to test communication. : NA
If FC - all ESXi initiator WWPNs have been configured in the SAN storage host definition ? Yes
↧
Re: I Could one path to LUN
Have you tried to restart the host?
How many LUNs do you have connected to that affected host? Can you be sure that you didn't hit configuration maximums for your host - number of connected storage devices and number of connected paths?
↧
↧
Re: Error loading /vmware_f.v00 - Fatal error: 8 (Device error)
I checked the compatibility matrix and turns out my IBM server is not compatible with vSphere 6.5
Thank you for your answer!
↧
stateless error: lost connectivity backing the boot filesystem
Hello,
I have had this error on one of our servers that states "Lost connectivity to the device mpx.vmhba:32:C0:T0:L0 backing the boot filesystem /vmfs/devices/disks/mpx.vmhba:32:C0:T0:L0. As a result, host configuration changes will not be saved to persistent storage.
All VM's have been running without an issue. My concern is if I would reboot the host, will it boot?
I went into the Dell R620 iDrac and under Removeable flash media it shows IDSDM SD1 and IDSDM SD2 are both Good and redundancy status is full. How is it possible that the cards are good but VMWare is not seeing it?
Do you think its just a glitch?
↧
Re: stateless error: lost connectivity backing the boot filesystem
I've seen that happen with HPE Blade Servers a lot. Usually there a iLO firmware upgrade helps since there the SD card somehow is managed via iLO (the HPE iDrac equivalent).
I don't have experience with that problem on Dell servers.
So far I had these situations:
SD card comes back after reboot
SD card comes back after power off / power on
SD card comes back after iLO reset / firmware update
SD card has to be removed + reinserted (happend just a week ago)
SD card needs to be replaced + ESXi needs to be reinstalled
When the SD card comes back it contains old config data so depending on what happened in the mean time some config may have to be updated manaually.
Good luck !
↧
How to Enable ESXi 6.5 passthrough using Asus UEFI Bios Utility?
Recently I installed ESXi 6.5 (free license) in home-lab PC.
I also have installed a quadr 4000 nvidia GPU in one of my PCI ports for extra GPU use.
Note: my monitor VGA is directly connected to my new nvidia port.
Through a little googling I found that in order to give access the new GPU card to a VM you should add the new PCI port to that VM using "Configuration PassThrough" Button. But in my case the button is disabled (Not clickable). I found this tutorial Pass-Through a NVIDIA GRID K1 to VM on ESXi 6.0 - 414 - YouTube which had the same issue but he fixed it by a little changes on his bios but the bios mode that he is using is different than mine, as you might know I am using Asus UEFI Bios Utility which I couldn't find some of the options that shows in the video.
All replies are much appreciated:
↧
↧
Re: stateless error: lost connectivity backing the boot filesystem
I have seen this error in HP rack mount servers as well. Updating iLO/iDRAC firmware may resolve the issue. If you have redundancy in your cluster (which you should), then evacuate all VMs from this host and reboot. If it doesn't come up, perform a cold boot. Or open the covers, remove the SD card controller and plug it back in. This was what HP support told us. Updating firmware fixed one of our servers but had to re-seat the controller on another. Open a ticket with Dell. Good luck.
↧
Cannot Install ASync Driver
Hello,
I am trying to install an ASync Intel driver downloaded directly from the VMWare Website. Unfortunately, after downloading the file, and transferring the offline bundle zip, I cannot install it.
I use the following command on the ESXI 6.5 server itself.
esxcli software vib install -d /tmp/VMW-ESX-6.5.0-igbn-1.2.0-offline_bundle-4646458.zip
I get this error:
[root@localhost:/etc] esxcli software vib install -d ~/etc/VMW-ESX-6.5.0-igbn-1.2.0-offline_bundle-4646
458.zip
Installation Result
Message: Host is not changed.
Reboot Required: false
VIBs Installed:
VIBs Removed:
VIBs Skipped: INT_bootbank_igbn_1.2.0-1OEM.650.0.0.4240417
I have also tried to put the server into maintenance mode using the following command:
esxcli system maintenanceMode set -e true
And then running the esxcli command again.
↧
Re: Vsphere 6.5 U1 update on Windows fails
This worked for me as far as getting the upgrade to complete.
VCenter was still acting goofy so I did a reboot.
I'll see how that works out.
ETA... It didn't. I ended up stepping back, stopping all VM services and deleting the bin and conf folders. We'll see how that works.
ETAA...
Stopping the VM services AND deleting the bin and conf folders allowed the upgrade to proceed. It came up and all ran well.
↧
Re: could not power on VM
Can you check this KB as it is same as this error " The specified device is not a valid physical disk device"
This issue occurs when you have configured the ScratchConfig.ConfiguredScratchLocation setting to point to the base of your ESXi host's local storage and you have virtual machines running on the same local storage. This also occurs when you have the scratch partition on the base of the local storage and have put virtual machines in a sub-directory under the configured scratch partition. This is not supported with ESXi and any such virtual machine vmdk's are marked as insecure.
Note: This issue can occur on NFS storage where the scratch directory is the base directory of the datastore, and in the same directory as virtual machines directories, or virtual machine directories are in a subdirectory of the directory containing the scratch directory.
Thanks,
MS
↧
↧
MSP - Applying ESXi and VCenter Updates
I am working with a Managed Services IT Provider, and we are trying to determine the most efficient method of applying patches and updates to VMWare ESXi servers, and VCenter servers and appliances. As of now, we manually apply updates to each server, but with hundreds and possibly thousands of servers at our various customers throughout the world, doing so in a timely manner is nearly impossible.
Does VMWare have a solution for managed service providers to allow this to happen in an efficient manner? What is the best way for us to go about this, for all of our customers, without taking up a tremendous amount of time, and also allowing for this to happen on a routine basis, so our customer's VMWare servers are regularly patched?
↧
Re: MSP - Applying ESXi and VCenter Updates
I dont think there is a one fits all. Each environment can and will be unique. You will need to check what hardware they are running on, it is compatible with the version you are trying to update to, what other solutions have been implemented and their interoperability. Does the hardware require a firmware upgrade to support the new vSphere updates. What drivers do I need to include in the patches, etc. etc. This can become a long list and if you are not careful, you can cause issues if not outages.
↧
Re: could not power on VM
Compress vmware.log (located in the home directory of the VM) and attach it here.
↧
Re: could not power on VM
sorry, how can i put attachment? see screenshot below.
↧
↧
Re: could not power on VM
Open the full thread (not the quick reply) and find the attach button in the lower left-hand corner.
↧
Re: could not power on VM
I just add one VM. attached is log.
I could not deploy VSA any longer. It sounds data store error.
at very beginning. when i add host 2 to VC. VC give warning: System logs on non-persistent storage
i change path as /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c and warning disappeared.
There is not any other error and warning coming until VSA deploy failure.
thanks!
Liu Wei
↧
Re: could not power on VM
No, could not solved.
when i try change directory /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c to /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/scratch. system give alert: wrong parameter.
thanks!
Liu Wei
↧