Quantcast
Channel: VMware Communities: Message List
Viewing all 251579 articles
Browse latest View live
↧

Single node vSAN cluster boot error after upgrade from 6.5 to 6.7

September 4, 2018, 1:34 pm
$
0
0

Hi,

 

I have single node vSAN cluster used as a homelab for many nested environments. I upgraded ESXi 6.5 to 6.7 without any issues. I noticed that during boot there is error recovery progress - see attached photo.

 

2018-09-04 22_07_19-Resolution_1024x768 FPS _10.png

I found as well something related in logs

 

2018-09-04T20:07:53.291Z cpu0:2097506)WARNING: Local node faultDomain ID is changed from 00000000-0000-0000-0000-000000000000 to 59b83712-415a-dc44-993d-0025905e041e

2018-09-04T20:07:54.305Z cpu5:2097506)WARNING: LSOMCommon: LSOM_DiskGroupCreate:1481: Disk group already created uuid: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-04T20:07:54.313Z cpu5:2097316)WARNING: NFS: 1227: Invalid volume UUID t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2

2018-09-04T20:07:54.396Z cpu0:2097506)WARNING: NFS: 1227: Invalid volume UUID 59b837bc-f856ecbc-0c43-0025905e041e

2018-09-04T20:08:07.381Z cpu0:2099225)WARNING: NTPClock: 1561: system clock synchronized to upstream time servers

2018-09-04T20:08:08.281Z cpu1:2099253)WARNING: LSOMCommon: LSOM_DiskGroupCreate:1481: Disk group already created uuid: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-04T20:08:08.289Z cpu4:2097312)WARNING: NFS: 1227: Invalid volume UUID t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2

2018-09-04T20:08:08.510Z cpu4:2099257)WARNING: LSOMCommon: LSOM_DiskGroupCreate:1481: Disk group already created uuid: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-04T20:08:08.519Z cpu1:2097312)WARNING: NFS: 1227: Invalid volume UUID t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2

2018-09-04T20:08:09.711Z cpu2:2099345)WARNING: LSOMCommon: LSOM_DiskGroupCreate:1481: Disk group already created uuid: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-04T20:08:09.719Z cpu0:2097310)WARNING: NFS: 1227: Invalid volume UUID t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2

After boot ESXi is ok, vSAN status looks good.

 

[root@ESXi:/vsantraces] esxcli vsan storage list

t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00

   Device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00

   Display Name: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00

   Is SSD: true

   VSAN UUID: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

   VSAN Disk Group UUID: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

   VSAN Disk Group Name: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00

   Used by this host: true

   In CMMDS: true

   On-disk format version: 5

   Deduplication: false

   Compression: false

   Checksum: 3722446061210474928

   Checksum OK: true

   Is Capacity Tier: false

   Encryption: false

   DiskKeyLoaded: false

   Is Mounted: true

 

 

t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144

   Device: t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144

   Display Name: t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144

   Is SSD: true

   VSAN UUID: 52c93db2-c879-ce09-ea2a-664a0ae10485

   VSAN Disk Group UUID: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

   VSAN Disk Group Name: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00

   Used by this host: true

   In CMMDS: true

   On-disk format version: 5

   Deduplication: false

   Compression: false

   Checksum: 12121898985191738183

   Checksum OK: true

   Is Capacity Tier: true

   Encryption: false

   DiskKeyLoaded: false

   Is Mounted: true

[root@ESXi:~] esxcli vsan cluster get

Cluster Information

   Enabled: true

   Current Local Time: 2018-09-04T20:11:10Z

   Local Node UUID: 59b83712-415a-dc44-993d-0025905e041e

   Local Node Type: NORMAL

   Local Node State: MASTER

   Local Node Health State: HEALTHY

   Sub-Cluster Master UUID: 59b83712-415a-dc44-993d-0025905e041e

   Sub-Cluster Backup UUID:

   Sub-Cluster UUID: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

   Sub-Cluster Membership Entry Revision: 0

   Sub-Cluster Member Count: 1

   Sub-Cluster Member UUIDs: 59b83712-415a-dc44-993d-0025905e041e

   Sub-Cluster Membership UUID: 22e58e5b-16de-fb32-0412-0025905e04e4

   Unicast Mode Enabled: true

   Maintenance Mode State: OFF

   Config Generation: None 0 0.0

Any idea how to troubleshoot?

 

Cheers
Wojciech

↧
Search

Disk Consolidation Fails with File Too Large

September 4, 2018, 1:34 pm
$
0
0

We are running ESXi 6.0.0 7967664 and our backup solution is Avamar. Recently during backups we started getting the error "....disk consolidation failed..." on one VM. If I try to manually consolidate the snapshots (all created by the backup solution) the error is "Consolidation failed for disk node 'scsi0:5': 27 (File Too Large)".

 

The relevant VMDK is 400 GB and there is over 1 TB of free space on the data store. There are several xxxxx-00000x.vmdk and respective ctk.vmdk files totaling about 200 GB in that disk's folder in the data store. (I assume new ones get created with each backup attempt.)

 

When I try to research the issue I getting a lot of stuff regarding locked files. I'm not actually seeing anything about locked files in the vCenter Tasks log.

 

Any ideas for resolving this? Do I need to look at other logs to get a better idea? Is the "file too large" error misleading?

 

Thanks.

↧
↧

Re: Disk Consolidation Fails with File Too Large

September 4, 2018, 1:49 pm
$
0
0

it would be useful to see the latest vmware.log
preferably from a run when you received the error you mentioned.
Ulli

↧

Windows 10 activation issue after backup restoration

September 4, 2018, 2:03 pm
$
0
0

Due to the hardware change on a Mac (HD replacement for a SSD) and backup restoration, Windows 10 does not recognize the digital license obtained during a Windows 8.1 free upgrade. Does anyone had the same or similar problem and can please help me?

 

I thank you in advance.

↧

Re: Windows 10 activation issue after backup restoration

September 4, 2018, 2:08 pm
$
0
0

This would seem to be a question better asked on a Windows 10/Microsoft forum and not a VMware one.

↧
↧

power off / on on reboot

September 4, 2018, 2:09 pm
$
0
0
If you are doing a hardware update from the GUI you have the option to select to upgrade on reboot.  What this is doing is looking for a reboot to exectute and then instead it powers it down, upgrades, and powers it up.  Is there a way to tie into this so I can use this process for something else.  Basically I want it to monitor for a reboot, then power off, run my custom instance, then power back on.  This way I can tie an update to a scheduled reboot for patches.
↧

power off / on on reboot

September 4, 2018, 2:10 pm
$
0
0
If you are doing a hardware update from the GUI you have the option to select to upgrade on reboot.  What this is doing is looking for a reboot to exectute and then instead it powers it down, upgrades, and powers it up.  Is there a way to tie into this so I can use this process for something else.  Basically I want it to monitor for a reboot, then power off, run my custom instance, then power back on.  This way I can tie an update to a scheduled reboot for patches.
↧

Re: vcsa lost connectivity to all esxi hosts

September 4, 2018, 2:10 pm
$
0
0

esxi = 6.5.0 (Build 5310538)

vcsa = 6.5 build 5973321

vcsa is timing out trying to access license

↧
Search

Re: Determining the VMtools version the ESXi publishes?

September 4, 2018, 2:11 pm
$
0
0

So knowing the ESXi build is only good to determine the minimum version of the VMTools, no?

Say I have a ESXi version 6.5, according to the list, the minimum version of VMTools would be 10252 (10.0.12 ), correct?

 

However, what if some other person from my company comes and put a 10272 (10.1.0) ISO there instead, how will I know that this is the version he put?

↧
↧

Re: vcsa lost connectivity to all esxi hosts

September 4, 2018, 2:16 pm
$
0
0

Look at your ESXi hosts directly. What license is applied?

↧

Re: Single node vSAN cluster boot error after upgrade from 6.5 to 6.7

September 4, 2018, 2:17 pm
$
0
0

Any resyncing components? My guess is that there may be a rebalance operation going on.

↧

Re: Determining the VMtools version the ESXi publishes?

September 4, 2018, 2:18 pm
$
0
0

So knowing the ESXi build is only good to determine the minimum version of the VMTools, no?

There's not really such thing as a "minimum version" only "this is the version that ships with that build".

 

Say I have a ESXi version 6.5, according to the list, the minimum version of VMTools would be 10252 (10.0.12 ), correct?

See answer to above question. You'd need to look at the build of that version to determine what's the closest earlier build that has a corresponding VMware tools version.

 

However, what if some other person from my company comes and put a 10272 (10.1.0) ISO there instead, how will I know that this is the version he put?

You'd need to look at the ISO to see that version as far as I know. Why is this a chief concern of yours?

↧

Re: vcsa lost connectivity to all esxi hosts

September 4, 2018, 2:23 pm
↧
↧

Re: vcsa lost connectivity to all esxi hosts

September 4, 2018, 2:23 pm
$
0
0

not sure if that is what you are asking for but that is an example from one of the esxi hosts

↧

migrate a server between two esxi hosts without shutdown of the server?

September 4, 2018, 2:26 pm
$
0
0

Is there any way to migrate a server between two host without shutdown of the server? The two esxi hosts have no shared storage and they run version 6u2. Any advice on this?

Thank you very much,

↧
Search

Re: vcsa lost connectivity to all esxi hosts

September 4, 2018, 2:28 pm
$
0
0

I should have specified that vcsa vm is on one esxi host and pfsense is on a different esxi host

↧

Re: migrate a server between two esxi hosts without shutdown of the server?

September 4, 2018, 2:30 pm
$
0
0

What's required to do this, is at least Essentials Plus licensing. This will allow to "Change both, host and storage", i.e. allow live migration without shared storage.


André

↧
↧

Re: Disk Consolidation Fails with File Too Large

September 4, 2018, 2:41 pm
$
0
0

Thanks for the reply. I've attached a snip of the log from the relevant time period.

↧

QueryNetConfig bug?

September 4, 2018, 2:41 pm
$
0
0

Hey guys,

 

I am calling the QueryNetConfig method on a HostSystem object to determine which vNic is assigned to the mgmt. network. If I connect with my account to vCenter and run the command it works fine. If I connect with a different account (service account in my testing with the exact same privileges and access) I get an error "Permission to perform this operation was denied."

 

Here is the sample of code I am executing:

 

(Get-View-Id$VMHost.ConfigManager.VirtualNicManager).QueryNetConfig('management').SelectedVnic

 

Response: management.key-vim.host.VirtualNic-vmk0

 

Here are the error details when running the code with different account.

 

PSMessageDetails :

Exception : System.Management.Automation.MethodInvocationException: Exception calling "QueryNetConfig" with "1" argument(s): "Permission

to perform this operation was denied." ---> VMware.Vim.VimException: Permission to perform this operation was denied. --->

System.ServiceModel.FaultException: Permission to perform this operation was denied.

 

Server stack trace:

at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation,

Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime

operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

 

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at VimApi_65.VimPortType.QueryNetConfig(QueryNetConfigRequest request)

at VMware.Vim.HostVirtualNicManager.QueryNetConfig(String nicType)

--- End of inner exception stack trace ---

at VMware.Vim.HostVirtualNicManager.QueryNetConfig(String nicType)

at CallSite.Target(Closure , CallSite , Object , String )

--- End of inner exception stack trace ---

at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type

typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo)

at CallSite.Target(Closure , CallSite , Object , String )

at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)

at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)

at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

TargetObject :

CategoryInfo : NotSpecified: (:) [], MethodInvocationException

FullyQualifiedErrorId : VimException

ErrorDetails :

InvocationInfo : System.Management.Automation.InvocationInfo

ScriptStackTrace : at <ScriptBlock>, <No file>: line 1

PipelineIterationInfo : {}

 

 

Here are the version details.

C:\temp> get-module vmware* | Select Name, Version

Name Version

---- -------

  1. VMware.VimAutomation.Cis.Core 10.0.0.7893915
  2. VMware.VimAutomation.Common 10.0.0.7893906
  3. VMware.VimAutomation.Core 10.0.0.7893909
  4. VMware.VimAutomation.Sdk 10.0.0.7893910

 

C:\temp> $host

Name : ConsoleHost

Version : 5.1.16299.611

 

It is occurring on both ESXi 5.5 and 6.0 hosts.

 

Thanks for any help with this issue.

↧

Re: Is it possible to utilize more than 16 threads in VM workstation?

September 4, 2018, 2:54 pm
$
0
0

Hi,

 

Not the answer you are looking for but VMware does have other products where you can utilize higher core counts.

 

In vSphere 6.0 the maximum limit of vCPUs in a VM is 128.

 

https://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdf

 

The problem with workstation is that it runs on a host OS and uses the CPU scheduler of that host OS, so it is not as ideal an environment for using a high number of CPUs for a single VM as with vSphere.

--

Wil

↧
Viewing all 251579 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>