You need to specify partition name for "vmkfstools -growfs" command, which has a form <drive name>:<partition number>. To view your disks and partitions, do "ls -l /dev/disks" and locate the correct partition. In my case partition number was 1, so I had to append ":1" to disk name, your value may differ.
↧
Re: vmkfstools --growfs returning Error: No such file or directory
↧
Re: Problem with ESXI 6.7 Update 3 (Build 14320388) and hostd.log
Anyone an idea?
The second IPMI error i found is saying me that the Intel NUC don't have an IPMI sensor. So thats error is ok.
Only the other error is very strange. i cannot place the error message. They still there every 5 minutes and 5 times. Also when all VM's powered off.
Any idea? Any suggestions?
↧
↧
Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem
Hi all-
We have 4 hosts running vSphere 6.5 on Cisco UCS-C240-M4's. They have a vSAN configuration. I started to get the 'Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem'
for no apparent reason. This is happening on only one host. I am not sure what logs I need to start checking or where to start. One thing I am interested in is seeing if there is a disk error (I know this looks like network issues, but I am curious). These machines are not UCS managed. And we are all working remotely so no physical access.
Where to start?
...Alan
↧
Re: Adaptec 6805 + ESXi 6 + Maxview
I managed to use Adaptec RAID 71605 on ESXi 6.7U3 build-15160138, including arcconf and maxView Storage Manager.
My 71605 is flashed to the latest firmware build 32118.
The driver, arcconf and msm is downloaded from the Adaptec RAID 81605ZQ support page, all of them are the latest one. Though all of them claim not to support Series 7, all of them works perfectly.
At the time I posted this reply, the driver version is v1.2.1-58012 and the storage manager version is v3.04.23699.
Hope this will offer some help.
-------- Updated 2020-04-21 --------
If you download the latest driver for Windows and open the .ini file, you will found it do support older cards like Series 5, 6, 7, even Series 2. So I think using the latest driver is totally ok.
↧
Re: vmkfstools --growfs returning Error: No such file or directory
VadimYakovlev Thank you so much for responding.
Here's what I'm trying now.
[root@server:~] ls -l /dev/disks
total 1953525053
-rw------- 1 root root 1000204886016 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________
-rw------- 1 root root 4161536 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:1
-rw------- 1 root root 4293918720 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:2
-rw------- 1 root root 992282874368 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3
-rw------- 1 root root 262127616 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:5
-rw------- 1 root root 262127616 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:6
-rw------- 1 root root 115326976 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:7
-rw------- 1 root root 299876352 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:8
-rw------- 1 root root 2684354560 Feb 11 01:21 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:9
lrwxrwxrwx 1 root root 72 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:1 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:1
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:2 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:2
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:3 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:5 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:5
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:6 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:6
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:7 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:7
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:8 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:8
lrwxrwxrwx 1 root root 74 Feb 11 01:21 vml.01000000003139313445314637423044322020202020202020435431303030:9 -> t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:9
Tried this:
[root@server:/dev/disks] vmkfstools --growfs vml.01000000003139313445314637423044322020202020202020435431303030:3 vml.01000000003139313445314637423044322020202020202020435431303030:3
Not found
Error: No such file or directory
Tried this:
[root@server:/dev/disks] vmkfstools --growfs "vml.01000000003139313445314637423044322020202020202020435431303030:3" "vml.01000000003139313445314637423044322020202020202020435431303030:3"
Not found
Error: No such file or directory
Tried this:
[root@server:/dev/disks] vmkfstools --growfs t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3
Not found
Error: No such file or directory
Then I also tried what I thought you were suggesting:
[root@server:/dev/disks] vmkfstools --growfs vml..:3 vml..:3
Device path name "vml..:3" is not a valid absolute or relative path
Failed to resolve volume device path vml..:3.
Error: No such file or directory
[root@server:/dev/disks] vmkfstools --growfs vml...:3 vml...:3
Device path name "vml...:3" is not a valid absolute or relative path
Failed to resolve volume device path vml...:3.
Error: No such file or directory
Any idea what I can try next? Thanks so much for your help, my server has been down for a week.
↧
↧
Re: Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem
These warnings are usually caused by firmware. Are the physical servers you use compatible with vsan? See a warning when you look at VSAN health?
ESXi hosts are not installed on SD card etc. right? If it is installed on SD card, SD card can give such warnings even though there is no malfunction.
↧
Re: Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem
Thank you for the reply.
These servers have been running vSAN for quite a while now, this error occurred out of the blue it seems. Not installed on an SD card as far as I know, I just inherited management
of these systems a few months ago. The disk drives are Samsung 3.8TB Enterprise SSD's. Was curious if a drive failure could cause this. Are there any logs I can check?
...Alan
↧
How to have the vmware box automatically boot up ?
I am just a beginner user to the VMWARE, and here is my question.
I have a vmware box in my lab, where the esxi 6.7 is installed. And on top of that, there are a bunch of VM servers running. Last time, there was a power outage in the lab, and I just realized that this vmware box was not able to be booted up itself. And I have to use the USB driver to bring it up. Is there some settings i need to do so that if such happens again, the box can boot up itself ?
Thanks,
Jack
↧
Re: Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem
↧
↧
Re: Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem
More information:
Been digging and it looks like this problem machine boots off of USB Direct-ACCESS off mbxa32. In vCenter this device is in italics. I tried
using vmkfstools to list the /bootbank directory and this volume shows up red and it said it cannot open that volume. On another machine this
works just fine.
I am not familiar with USB Direct-Access. Is this an actual USB drive?
...Alan
↧
How to restore ESXi backup to different hardware
Hello community,
I did a ESXi configuration backup from CLI using the following command:
vim-cmd hostsvc/firmware/backup_config
Now I would like to test the backup, so I installed the same ESXi version on VMWare workstation. Same version and same build: VMware ESXi 6.7.0 build-8169922
But when I try to restore I got:
vim-cmd hostsvc/maintenance_mode_enter
vim-cmd hostsvc/firmware/restore_config /tmp/configBundle.tgz
(vim.fault.InvalidBundle) {
faultCause = (vmodl.MethodFault) null,
faultMessage = <unset>,
text = "Missing Manifest File"
msg = "Received SOAP response fault from [<cs p:00000039b9877570, TCP:localhost:8307>]: restoreConfiguration
fault.InvalidBundle.summary"
}
Is there a way to restore that configuration so I can test it in another machine?
Thank you
↧
Re: How to restore ESXi backup to different hardware
No, that won't work. ESXi isn't designed to work like this. You can restore VMs and some of ESXi's settings, but not the entire identity of the host itself.
↧
Re: How to restore ESXi backup to different hardware
Not sure whether this will work, but you may give it a try:
from https://kb.vmware.com/s/article/2042141?lang=en_us
Note: When restoring configuration data, the build number of the host must match the build number of the host on backup file and UUID (can be obtained using the command "esxcfg-info -u") of the host should match the UUID of the host on backup file.
Use numeric 1 as force option to override the UUID mismatch. For example, vim-cmd hostsvc/firmware/restore_config 1 /tmp/configBundle.tgz
André
↧
↧
Re: vmkfstools --growfs returning Error: No such file or directory
Using names starting from "vml" is not likely to succeed, these are just links to real device names which vmkfstools probably needs.
Also literally typing "vmkfstools --growfs vml..:3 vml..:3" will not work of course - in my first comment I was using ellipsis just to strip down lengthy device name.
In your case the correct command would be this one:
vmkfstools --growfs t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3 t10.ATA_____CT1000MX500SSD1_________________________1914E1F7B0D2________:3
But if you say it also doesn't work, then I'm afraid I don't know why and don't have other ideas
↧
Re: How to restore ESXi backup to different hardware
Thank you both for reply.
↧
Re: How to restore ESXi backup to different hardware
You could script the network config process, there's a dedicated PowerCLI forum where you could get help with how to do that: VMware PowerCLI
Or if using vCenter Server with vSphere Enterprise Plus, use the Host Profiles feature: About vSphere Host Profiles
↧
hyperthreadingMitigation setting lost on ISO upgrade of 6.5 -> 7.0
Upgraded the host using ISO attach and then boot into installer and selected upgrade. The hyperthreadingMitigation setting went from true/SCAv1 to FALSE.
It did alert in vSphere, but seems odd that it would go to the default.
↧
↧
ESXi 6.7 fails to list Intel X540 (ixgben) Network Ports via a Thunderbolt3 to Thunderbolt2 Apple Adapter (On Windows 10 it works)
Environment
- Intel Hades Canyon
- 64GB (2 x 32GB DDR4 2400 MHz)
- (1) 1TB NVMe PCIe M.2 2280
- ESXi 6.7 (15820472)
- Boot Drive = 16GB USB 3.1 Flash Drive
- Promise SANLink2 10GbE (Thunderbolt2)
- Uses the Intel X540 AT2 Ethernet Controller
- Connected to the Intel NUC via an Apple Thunderbolt3 to Thunderbolt2 Adapter
Problem Statement
ESXi fails to list the Intel X540 (ixgben) as configurable network ports via a Thunderbolt3 to Thunderbolt2 Apple Adapter; however, on the same machine + HW configuration with Windows 10 being the underlying OS, the ports get detected just fine.
- On ESXi, the Intel X540 PCI card does get detected and is properly listed under Hardware -> PCI Devices:
![Hardware_PCI_1.png]()
- [root@esxinuc:~] lspci | grep X540 0000:40:00.0 Ethernet controller: Intel(R) Ethernet Controller 10 Gigabit X540-AT2 0000:40:00.1 Ethernet controller: Intel(R) Ethernet Controller 10 Gigabit X540-AT2
- You can clearly see that the ESXi detects the PCI card; however, there seems to be some addressing issue on the PCI side of things; as it fails to list the (2) available network ports.
- In addition, I have an Apple Thunderbolt to Gigabit Ethernet Adapter (Broadcom Corporation NetXtreme BCM57762) connected via the same Thunderbolt chain and the network port get detected with the tg3 inbox driver. It appears that ESXi doesn't know how to address the Intel X540 with the ixgben driver when the TB3 to TB2 adapter is the intermediary between the host and card.
[root@esxinuc:~] esxcli network nic list Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description ------ ------------ ------ ------------ ----------- ----- ------ ----------------- ---- -------------------------------------------------------- vmnic0 0000:00:1f.6 ne1000 Up Down 0 Half d4:5d:df:07:4f:59 1500 Intel Corporation Ethernet Connection (2) I219-V vmnic1 0000:05:00.0 igbn Up Up 1000 Full d4:5d:df:07:4f:5a 1500 Intel Corporation I210 Gigabit Network Connection vmnic2 0000:44:00.0 tg3 Up Down 0 Half 38:c9:86:22:e4:b0 1500 Broadcom Corporation NetXtreme BCM57762 Gigabit Ethernet
- Why does ESXi fail to list the network ports via the ixgben driver for the Intel X540 through the TB3 to TB2 adapter while still detecting the Intel X540 PCI card?
- The problem would have made more sense if the PCI card didn't get detected by ESXi; however, the fact that it is detected, ESXi should be able to assign the ixgben driver.
- The problem isn't the SANLink2 10GbE (Intel X540) but some odd issue amongst the Thunderbolt bus translation to ESXi when using a TB3 to TB2 adapter; hence, the ixgben driver never gets assigned.
- I updated the TB FW on the NUC to version 33.00 to see if it had anything to do with it; however, the update had no effect on ESXi assigning the driver.
![Screen Shot 2020-04-18 at 5.37.39 PM.png]()
- Disclaimer– I understand that:
(A) the Intel NUC is not officially part of the HCL (many people in the community use NUCs for home labs)
(B) an Apple Thunderbolt3 to Thunderbolt2 adapter is not officially part of the HCL - Please note that if I boot in Windows 10 with the same HW (Intel NUC) and physical configuration (SL2 via TB3 to TB2), the Intel X540 contained in the Promise SANLink2 10GbE via the Thunderbolt bus works perfectly fine:
![Screen Shot 2020-04-21 at 6.01.44 PM.png]()
![Screen Shot 2020-04-21 at 6.07.12 PM.png]()
- For those wondering if the Promise SANLink2 10GbE works natively using the ixgbe (ESXi 6.0) or the newer driver ixgben (ESXi 6.5, 6.7), when connecting the Promise SANLink2 10GbE to a Thunderbolt2 or Thunderbolt1 host running on ESXi, it works perfectly fine. ESXi automatically assigns the driver to the Intel Ethernet Controller X540.
ESXi 6.7 with SL2 connected to a TB1 MacBook Pro![Screen Shot 2020-04-16 at 9.49.07 PM copy.png]()
- I've used the SL2 with multiple Thunderbolt1/2 based Macs that are running ESXi and they work great.
- Since I had (1) laying around, I thought I would test using the TB3 to TB2 adapter before looking for TB3 based 10GbE adapters; as the ones listed in Virtually Ghetto.
- Anyone have an idea why ESXi fails to assign the ixgben driver to the Intel X540 Ethernet Controller when using the TB3 to TB2 adapter?
- Is there anything that I can attempt to invoke? (It would save me from purchasing a TB3 10GbE adapter).
↧
Re: vmkfstools --growfs returning Error: No such file or directory
Now I'm getting this error https://prnt.sc/s2wg40 when trying to unmount the volume to attempt to reregister.
↧
not enough bandwidth
hi all,
i have 5 hosts in cluster with separate managent DvS and Guest traffic DvS.
currently in Guest DvS have one physical uplink of 25 G
i have two VMs and with VMXNET3 adapter, and checking bandwidth using iperf.
i found i am getting only average 1.74Gbits/Sec. how can i improve this speed.
↧