Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Storage vMotion fails with Error 195887107 (66850)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 36016Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Symptoms

When running a storage vMotion task on a powered on virtual machine, you experience these symptoms:

The storage vMotion task fails.

You see the error similar to:

Failed waiting for data. Error 195887107. Not found. Failed to start SvMotion. Error during disk setup. A fatal internal error occurred. See the virtual machine's log for more details.

In the vmware.log file of the affected virtual machine, you see entries similar to:

Worker#2| W115: Mirror: scsi1:0: SVMotionDiskSetup: You may not migrate a multi-writer disk

In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

2019-01-17T14:07:59.549Z cpu18:331719)Hbr: 3395: Migration start received (worldID=1347665) (migrateType=2) (event=0) (isSource=0) (sharedConfig=0)
2019-01-17T14:07:59.789Z cpu21:76251)Migrate: vm 76253: 4049: Setting FSR info: Source ts = 8819671840104550966, src ip = <127.0.0.1> dest ip = <127.0.0.1> Dest wid = 1347665 using UNSHARED swap
2019-01-17T14:07:59.789Z cpu21:76251)Hbr: 3395: Migration start received (worldID=76253) (migrateType=2) (event=0) (isSource=1) (sharedConfig=0)
2019-01-17T14:08:02.091Z cpu33:76251)WARNING: Migrate: 6279: 8819671840104550966 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.
2019-01-17T14:08:02.091Z cpu33:76251)WARNING: Migrate: 273: 8819671840104550966 S: Failed: Migration determined a failure by the VMX (0xbad0092) @0x418016717547
2019-01-17T14:08:02.091Z cpu33:76251)Hbr: 3489: Migration end received (worldID=76253) (migrateType=2) (event=1) (isSource=1) (sharedConfig=0)
2019-01-17T14:08:02.095Z cpu0:331719)WARNING: FSR: 355: 8819671840104550966 D: Could not find migrate info for remote world 76253!
2019-01-17T14:08:02.095Z cpu0:331719)WARNING: FSR: 4255: 8819671840104550966 D: Failed to find remote FSR.  Did the migration fail?
2019-01-17T14:08:02.186Z cpu26:68707)Config: 706: "SIOControlFlag2" = 1, Old Value: 2, (Status: 0x0)
2019-01-17T14:08:02.488Z cpu4:331719)WARNING: Migrate: 6279: 8819671840104550966 D: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.
2019-01-17T14:08:02.488Z cpu4:331719)WARNING: Migrate: 273: 8819671840104550966 D: Failed: Migration determined a failure by the VMX (0xbad0092) @0x418016717547

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides information to resolve an issue when a storage vMotion task failure occurs when the powered on virtual machine is using disks with the multi-writer attribute.

Cause

This issue occurs due to the virtual machine using disk(s) configured with the multi-writer attribute.

As the virtual machine is using disk(s) with the multi-writer attribute, neither shared nor non-shared disks of the VM can be migrated using storage vMotion as the virtual machine stun is required to initiate the storage migration.

Resolution

This is an expected behavior when running a storage vMotion task on powered on virtual machines that are using disks with the multi-writer attribute.
The multi-writer option allows VMFS-based disks to be shared by multiple virtual machines. For more information, see Enabling or disabling simultaneous write protection provided by VMFS using the multi-writer flag (1034165).

Workaround

To work around this issue:

Power off the affected virtual machine.

Perform the storage vMotion.

Power on the virtual machine once the storage vMotion task is completed.

Related Information

Review any backup software tools messages about disk space issues. Snapshots of the virtual machine will impact storage vMotions if space on the  LUN is less than 1.5 times the total of the VM's snapshots sizes. Confirm with your company storage team the LUN the virtual machine resides on has enough over head space to consolidate data and migrate. If not expand the current LUN where the virtual machine resides and consolidate the data. If the LUN can not expand space a clone of the Virtual Machines disk to another datastore is an option https://kb.vmware.com/s/article/1028042

The man page on the ESXI host use the command: vmkfstools -h

example syntax:
vmkfstools -i "/vmfs/volumes/currentDatastore/vm_name/vm_name.vmdk" "/vmfs/volumes/newDatastore/vm_name/vm_name.vmdk" -d thin -a buslogic

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
客户无法在 Horizon Cloud 托管环境中更新域绑定帐户详细信息 (66888)

KB
•
ローリング メンテナンス タスクが静止状態で停止している (66843)

KB
•
无法使用 Horizon Client 启动应用程序或无法启动 AppBlast 门户，用户会收到以下错误：“此桌面的显示协议当前不可用。 错误: AGENT_ERR_PROTOCOL_FAILURE” (66784)

KB
•
滚动维护任务卡在静默状态 (66843)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant