Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Device cancels reported after hot-inserted into vSAN (74838)

Last Updated: 6/7/2021Categories: TroubleshootingTotal Views: 8575Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

In the /var/log/vmware/vmkernel log file, you see entries similar to:

019-09-04T19:40:23.746Z cpu41:2097989)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x4305cbb3d620]
2019-09-04T19:40:23.746Z cpu41:2097989)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2019-09-04T19:40:23.746Z cpu41:2097989)VMWARE SCSI Id: Id for vmhba0:C2:T2:L0
0x50 0x00 0x0f 0x0b 0x49 0x10 0x60 0x30 0x56 0x4b 0x30 0x30 0x33 0x38
2019-09-04T19:40:23.747Z cpu41:2097989)ScsiDeviceIO: 8478: QErr is correctly set to 0x0 for device naa.50000f0b49106030.
2019-09-04T19:40:23.747Z cpu41:2097989)ScsiDeviceIO: 8975: Could not detect setting of sitpua for device naa.50000f0b49106030. Error Not supported.
2019-09-04T19:40:23.751Z cpu41:2097989)PLOG: PLOG_InitDevice:278: Initialized device M naa.50000f0b49106030:1 0x43138ddf8930 quiesceTask 0x45a32fcc3940 on SSD 52881967-a4c0-107f-82ff-c7dab1a047bfdeviceUUID 00000000-0000-0000-0000-000000000000
2019-09-04T19:40:23.751Z cpu41:2097989)PLOG: PLOGProbeDevice:6391: Probed partition naa.50000f0b49106030:1 of disk naa.50000f0b49106030 hot added
2019-09-04T19:40:23.752Z cpu41:2097989)PLOG: PLOG_InitDevice:278: Initialized device D naa.50000f0b49106030:2 0x43138ddf9c20 quiesceTask 0x45a32fcb3d40 on SSD 52881967-a4c0-107f-82ff-c7dab1a047bfdeviceUUID 00000000-0000-0000-0000-000000000000
2019-09-04T19:40:23.752Z cpu41:2097989)LSOMCommon: LSOMVA_OpenDiskGroup:868: Initiating VA space for disk group 52881967-a4c0-107f-82ff-c7dab1a047bf
2019-09-04T19:40:23.752Z cpu41:2097989)LSOMCommon: LSOMVA_OpenDiskGroup:974: VA space handle 0 to be used for disk group 52881967-a4c0-107f-82ff-c7dab1a047bf

In the vSAN log files you see:

2019-09-03T16:00:59.995Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x4395418feac0) 0x25, CmdSN 0x11e58 from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x4395503fd800) 0x2a, CmdSN 0x47e13 from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:66033)WARNING: ScsiCore: 1806: Invalid sense buffer: error=0x0, valid=0x0
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x439d413546c0) 0x2a, CmdSN 0x47e0b from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x439d484071c0) 0x2a, CmdSN 0x47e0d from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x439d413386c0) 0x2a, CmdSN 0x47e11 from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:66033)WARNING: ScsiCore: 1806: Invalid sense buffer: error=0x0, valid=0x0
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x43954f7d97c0) 0x2a, CmdSN 0x47e14 from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:66033)WARNING: ScsiCore: 1806: Invalid sense buffer: error=0x0, valid=0x0
2019-09-03T16:01:12.049Z cpu0:65617)ScsiDeviceIO: 3015: Cmd(0x43954f7023c0) 0x2a, CmdSN 0x47e15 from world 0 to dev "naa.50000f0b49106030" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
2019-09-03T16:01:12.049Z cpu0:66033)WARNING: ScsiCore: 1806: Invalid sense buffer: error=0x0, valid=0x0

Cause

When a device is registered with the ESXi storage stack, it is possible that vSAN can generate more I/Os than usual before the device registration is complete, in such cases I/O can get blocked leading to I/O cancels until the time the device registration is completed, leading to failed disks at vSAN.

The issue may be triggered after a unplanned disk remove and reinsert operation. On rare occasions, a host reboot may trigger this issue.

Resolution

To resolve this issue, reboot the host reporting the errors.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi ホストにパッチを適用して 7.0 Update 2 にアップグレードすると、crypto64.efi のロードに失敗し、「致命的エラー: 15（見つかりません）(Fatal error: 15 (Not found))」というエラーが発生する (83063)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 7.0.x

Take Our Survey

Support Assistant