Why is ESXi 6.7 failing registration of NVMe SSD drive?
0
We have developed a NVMe SSD PCIe drive that works on Linux and Windows. The card has a minimum block size of 4K. I tested the card on ESXI 6.7. The card shows up as vmhba2 but does not appear in the storage->devices list. I can see that ESXi creates all the queues and reads a block of data from our SSD drive. I can also use esxcli to query the drive, read controller ID and log pages. All that works fine. In the vmkernel.log I see the following:
2018-12-05T12:35:56.616Z cpu23:2098770)VMWARE SCSI Id: Id for vmhba2:C0:T0:L0
0x31 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x31 0x41 0x4c 0x32 0x30 0x31 0x36
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device t10.NVMe____AL2016............................AL20161..................100000001.
2018-12-05T12:35:56.616Z cpu28:2097231)ScsiDeviceIO: 3015: Cmd(0x45a240548b40) 0x1a, CmdSN 0x372 from world 0 to dev "t10.NVMe____AL2016............................AL20161..................100000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5
2018-12-05T12:35:56.616Z cpu28:2097231)0x24 0x0.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device t10.NVMe____AL2016............................AL20161..................100000001. Error Not supported.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 3636: Failing registration of device 't10.NVMe____AL2016............................AL20161..................100000001': Unsupported device attributes isLocal:1, isSSD:1, isNmpPlugin:1
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5224: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5234: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5244: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5254: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5264: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-12-05T12:35:56.616Z cpu23:2098770)WARNING: NMP: nmp_RegisterDevice:851: Registration of NMP device with primary uid 't10.NVMe____AL2016............................AL20161..................100000001' failed. Not supported
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1063: Freeing APD handle 0x4303b5b6b160
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1147: APD Handle freed!
It's not clear why ESXi is deliberately failing the registration. Any ideas on how I can proceed with this issue? I'm new to ESXi.
ssd esxi pci nvme
edited Dec 7 at 18:53
K7AAY
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
add a comment |
0
We have developed a NVMe SSD PCIe drive that works on Linux and Windows. The card has a minimum block size of 4K. I tested the card on ESXI 6.7. The card shows up as vmhba2 but does not appear in the storage->devices list. I can see that ESXi creates all the queues and reads a block of data from our SSD drive. I can also use esxcli to query the drive, read controller ID and log pages. All that works fine. In the vmkernel.log I see the following:
2018-12-05T12:35:56.616Z cpu23:2098770)VMWARE SCSI Id: Id for vmhba2:C0:T0:L0
0x31 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x31 0x41 0x4c 0x32 0x30 0x31 0x36
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device t10.NVMe____AL2016............................AL20161..................100000001.
2018-12-05T12:35:56.616Z cpu28:2097231)ScsiDeviceIO: 3015: Cmd(0x45a240548b40) 0x1a, CmdSN 0x372 from world 0 to dev "t10.NVMe____AL2016............................AL20161..................100000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5
2018-12-05T12:35:56.616Z cpu28:2097231)0x24 0x0.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device t10.NVMe____AL2016............................AL20161..................100000001. Error Not supported.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 3636: Failing registration of device 't10.NVMe____AL2016............................AL20161..................100000001': Unsupported device attributes isLocal:1, isSSD:1, isNmpPlugin:1
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5224: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5234: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5244: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5254: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5264: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-12-05T12:35:56.616Z cpu23:2098770)WARNING: NMP: nmp_RegisterDevice:851: Registration of NMP device with primary uid 't10.NVMe____AL2016............................AL20161..................100000001' failed. Not supported
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1063: Freeing APD handle 0x4303b5b6b160
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1147: APD Handle freed!
It's not clear why ESXi is deliberately failing the registration. Any ideas on how I can proceed with this issue? I'm new to ESXi.
ssd esxi pci nvme
edited Dec 7 at 18:53
K7AAY
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55
add a comment |
0
0
0
We have developed a NVMe SSD PCIe drive that works on Linux and Windows. The card has a minimum block size of 4K. I tested the card on ESXI 6.7. The card shows up as vmhba2 but does not appear in the storage->devices list. I can see that ESXi creates all the queues and reads a block of data from our SSD drive. I can also use esxcli to query the drive, read controller ID and log pages. All that works fine. In the vmkernel.log I see the following:
2018-12-05T12:35:56.616Z cpu23:2098770)VMWARE SCSI Id: Id for vmhba2:C0:T0:L0
0x31 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x31 0x41 0x4c 0x32 0x30 0x31 0x36
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device t10.NVMe____AL2016............................AL20161..................100000001.
2018-12-05T12:35:56.616Z cpu28:2097231)ScsiDeviceIO: 3015: Cmd(0x45a240548b40) 0x1a, CmdSN 0x372 from world 0 to dev "t10.NVMe____AL2016............................AL20161..................100000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5
2018-12-05T12:35:56.616Z cpu28:2097231)0x24 0x0.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device t10.NVMe____AL2016............................AL20161..................100000001. Error Not supported.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 3636: Failing registration of device 't10.NVMe____AL2016............................AL20161..................100000001': Unsupported device attributes isLocal:1, isSSD:1, isNmpPlugin:1
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5224: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5234: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5244: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5254: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5264: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-12-05T12:35:56.616Z cpu23:2098770)WARNING: NMP: nmp_RegisterDevice:851: Registration of NMP device with primary uid 't10.NVMe____AL2016............................AL20161..................100000001' failed. Not supported
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1063: Freeing APD handle 0x4303b5b6b160
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1147: APD Handle freed!
It's not clear why ESXi is deliberately failing the registration. Any ideas on how I can proceed with this issue? I'm new to ESXi.
ssd esxi pci nvme
edited Dec 7 at 18:53
K7AAY
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
We have developed a NVMe SSD PCIe drive that works on Linux and Windows. The card has a minimum block size of 4K. I tested the card on ESXI 6.7. The card shows up as vmhba2 but does not appear in the storage->devices list. I can see that ESXi creates all the queues and reads a block of data from our SSD drive. I can also use esxcli to query the drive, read controller ID and log pages. All that works fine. In the vmkernel.log I see the following:
2018-12-05T12:35:56.616Z cpu23:2098770)VMWARE SCSI Id: Id for vmhba2:C0:T0:L0
0x31 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x2e 0x31 0x41 0x4c 0x32 0x30 0x31 0x36
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 7998: QErr is correctly set to 0x0 for device t10.NVMe____AL2016............................AL20161..................100000001.
2018-12-05T12:35:56.616Z cpu28:2097231)ScsiDeviceIO: 3015: Cmd(0x45a240548b40) 0x1a, CmdSN 0x372 from world 0 to dev "t10.NVMe____AL2016............................AL20161..................100000001" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5
2018-12-05T12:35:56.616Z cpu28:2097231)0x24 0x0.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDeviceIO: 8495: Could not detect setting of sitpua for device t10.NVMe____AL2016............................AL20161..................100000001. Error Not supported.
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 3636: Failing registration of device 't10.NVMe____AL2016............................AL20161..................100000001': Unsupported device attributes isLocal:1, isSSD:1, isNmpPlugin:1
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5224: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5234: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5244: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5254: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiDevice: 5264: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:t10.NVMe____AL2016............................AL20161..................100000001. Reason: Not found
2018-12-05T12:35:56.616Z cpu23:2098770)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-12-05T12:35:56.616Z cpu23:2098770)WARNING: NMP: nmp_RegisterDevice:851: Registration of NMP device with primary uid 't10.NVMe____AL2016............................AL20161..................100000001' failed. Not supported
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1063: Freeing APD handle 0x4303b5b6b160
2018-12-05T12:35:56.616Z cpu23:2098770)StorageApdHandler: 1147: APD Handle freed!
It's not clear why ESXi is deliberately failing the registration. Any ideas on how I can proceed with this issue? I'm new to ESXi.
ssd esxi pci nvme
ssd esxi pci nvme
edited Dec 7 at 18:53
K7AAY
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
edited Dec 7 at 18:53
K7AAY
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
edited Dec 7 at 18:53
K7AAY
3,38321437
edited Dec 7 at 18:53
K7AAY
3,38321437
edited Dec 7 at 18:53
K7AAY
3,38321437
3,38321437
asked Dec 6 at 0:55
Mia Dawson
62
asked Dec 6 at 0:55
Mia Dawson
62
asked Dec 6 at 0:55
Mia Dawson
62
62
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55
add a comment |
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1381195%2fwhy-is-esxi-6-7-failing-registration-of-nvme-ssd-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1381195%2fwhy-is-esxi-6-7-failing-registration-of-nvme-ssd-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you find any registration issues for NVMe devices and your motherboard at vmware.com/support/vsphere.html ? What is your motherboard? Please reply by refining and expanding your original question by clicking edit.
– K7AAY
Dec 7 at 18:55