wdc/sndk plug-in not functioning as expected for SanDisk SN861.

[Sayoojntly]

Steps

1. Power on the NVME OF enclosure with SN861 drives connected to host.
2. Check the wdc/sndk plug in commands.

Observations:
WDC Plug-in not functioning as expected

nvme wdc get-drive-status /dev/nvme1
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
wdc_get_fw_cust_id: ERROR: WDC: 0xC2 Log Page entry ID 0x15 not found
wdc_get_enc_drive_capabilities: ERROR: WDC: invalid customer id
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: 0xC2 Log Page not supported

The issue seen with nvme version 2.14 with Sandisk plug in commands as well.

nvme sndk get-drive-status /dev/nvme3
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
wdc_get_fw_cust_id: ERROR: WDC: 0xC2 Log Page entry ID 0x15 not found
wdc_get_enc_drive_capabilities: ERROR: WDC: invalid customer id
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: 0xC2 Log Page not supported, uuid_index: 0

# nvme version
nvme version 2.14 (git 2.14)
libnvme version 1.14 (git 1.14)
:~#

[igaw]

Jeff, do you happen to know what's going on here? @jeff-lien-sndk

[jeff-lien-sndk]

I see 2 issues here.

1. The "wdc_get_pci_ids : Open vendor file failed" messages are caused by the drive being fabric attached. We're unable to get the the pci device id's in fabric attached drives. This issue can be ignored though. It generates noise with the several additional error messages per command but they don't appear to be causing any functional issues.
2. Using uuid_index of 0 to read the WDC C2 log page is not correct. I'm not sure why an index of 0 is being used. The code wll search the uuid list for the WDC uuid and will determine the correct index to use based on that as per how it's stated in the nvme spec. This is working as expected for me on a direct attached SN861.

@Sayoojntly I will continue to look into the wdc and sandisk plugin code but have a few questions for you.

• What's the pci device id of the SN861 drive you're using?
• What's the version of FW loaded on it?
• Could you execute the command "nvme id-uuid /dev/nvmeX" on your drive and post the output here?

@igaw Are you aware of an nvme cli command limitations or restrictions with nvme over fabric attached drives?

[Sayoojntly]

Hi @jeff-lien-sndk ,
Please find my response.

• What's the pci device id of the SN861 drive you're using?
  @Sayoojntly The drive is connected through NVMe OF enclosure.

Device           Cntlid SN                   MN                                       FR       TxPort Address        Slot   Subsystem    Namespaces
---------------- ------ -------------------- ---------------------------------------- -------- ------ -------------- ------ ------------ ----------------
nvme0    16386  240562800020         WUS5EA138ESP7E1                          RC610008 rdma   traddr=20.20.20.6,trsvcid=4420        nvme-subsys0
nvme1    16396  37241CE0000310       SDS6BA138PSP9X1                          RH110013 rdma   traddr=10.10.10.6,trsvcid=4420        nvme-subsys1 nvme1n1
nvme10   16388  372415E0006610       SDS6BA138PSP9X1                          RH110013 rdma   traddr=10.10.10.6,trsvcid=4420        nvme-subsys10 nvme10n1

• What's the version of FW loaded on it?
  @Sayoojntly The drive firmware is RH110013

nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme10n1         /dev/ng10n1           372415E0006610       SDS6BA138PSP9X1                          0x1          1.27  TB /   3.83  TB      4 KiB +  0 B   RH110013
/dev/nvme11n1         /dev/ng11n1           37241CE0000210       SDS6BA138PSP9X1                          0x1          1.25  TB /   3.83  TB      4 KiB +  0 B   RH110013

• Could you execute the command "nvme id-uuid /dev/nvmeX" on your drive and post the output here?
  @Sayoojntly The id-uuid is giving Invalid Field in Command

 nvme id-uuid /dev/nvme10
NVMe status: Invalid Field in Command: A reserved coded value or an unsupported value in a defined field(0x4002)

I am attaching id-ctrl from the drive

 nvme id-ctrl /dev/nvme10 -H
NVME Identify Controller:
vid       : 0x1b96
ssvid     : 0x1b96
sn        : 372415E0006610
mn        : SDS6BA138PSP9X1
fr        : RH110013
rab       : 2
ieee      : 0014ee
cmic      : 0x2
  [3:3] : 0     ANA not supported
  [2:2] : 0     PCI
  [1:1] : 0x1   Multi Controller
  [0:0] : 0     Single Port

mdts      : 8
cntlid    : 0x4004
ver       : 0x10400
rtd3r     : 0x1c9c380
rtd3e     : 0x4c4b40
oaes      : 0x300
  [31:31] : 0   Discovery Log Change Notice Not Supported
  [27:27] : 0   Zone Descriptor Changed Notices Not Supported
  [16:16] : 0   Temperature Threshold Hysteresis Recovery Not Supported
  [15:15] : 0   Normal NSS Shutdown Event Not Supported
  [14:14] : 0   Endurance Group Event Aggregate Log Page Change Notice Not Supported
  [13:13] : 0   LBA Status Information Notices Not Supported
  [12:12] : 0   Predictable Latency Event Aggregate Log Change Notices Not Supported
  [11:11] : 0   Asymmetric Namespace Access Change Notices Not Supported
  [9:9] : 0x1   Firmware Activation Notices Supported
  [8:8] : 0x1   Namespace Attribute Changed Event Supported

ctratt    : 0x40
  [19:19] : 0   Flexible Data Placement Not Supported
  [17:17] : 0   HMB Restrict Non-Operational Power State Access Not Supported
  [16:16] : 0   MDTS and Size Limits Exclude Metadata Not Supported
  [15:15] : 0   Extended LBA Formats Not Supported
  [14:14] : 0   Delete NVM Set Not Supported
  [13:13] : 0   Delete Endurance Group Not Supported
  [12:12] : 0   Variable Capacity Management Not Supported
  [11:11] : 0   Fixed Capacity Management Not Supported
  [10:10] : 0   Multi Domain Subsystem Not Supported
  [9:9] : 0     UUID List Not Supported
  [8:8] : 0     SQ Associations Not Supported
  [7:7] : 0     Namespace Granularity Not Supported
  [6:6] : 0x1   Traffic Based Keep Alive Supported
  [5:5] : 0     Predictable Latency Mode Not Supported
  [4:4] : 0     Endurance Groups Not Supported
  [3:3] : 0     Read Recovery Levels Not Supported
  [2:2] : 0     NVM Sets Not Supported
  [1:1] : 0     Non-Operational Power State Permissive Not Supported
  [0:0] : 0     128-bit Host Identifier Not Supported

rrls      : 0
cntrltype : 1
  [7:2] : 0     Reserved
  [1:0] : 0x1   I/O Controller
fguid     : 00000000-0000-0000-0000-000000000000
crdt1     : 0
crdt2     : 0
crdt3     : 0
nvmsr     : 1
  [1:1] : 0     NVM subsystem Not part of an Enclosure
  [0:0] : 0x1   NVM subsystem part of a Storage Device

vwci      : 255
  [7:7] : 0x1   VPD Write Cycles Remaining field is valid.
  [6:0] : 0xfe  VPD Write Cycles Remaining

mec       : 3
  [1:1] : 0x1   NVM subsystem contains a Management Endpoint on a PCIe port
  [0:0] : 0x1   NVM subsystem contains a Management Endpoint on an SMBus/I2C port

oacs      : 0x5e
  [10:10] : 0   Lockdown Command and Feature Not Supported
  [9:9] : 0     Get LBA Status Capability Not Supported
  [8:8] : 0     Doorbell Buffer Config Not Supported
  [7:7] : 0     Virtualization Management Not Supported
  [6:6] : 0x1   NVMe-MI Send and Receive Supported
  [5:5] : 0     Directives Not Supported
  [4:4] : 0x1   Device Self-test Supported
  [3:3] : 0x1   NS Management and Attachment Supported
  [2:2] : 0x1   FW Commit and Download Supported
  [1:1] : 0x1   Format NVM Supported
  [0:0] : 0     Security Send and Receive Not Supported

acl       : 3
aerl      : 3
frmw      : 0x14
  [5:5] : 0     Multiple FW or Boot Update Detection Not Supported
  [4:4] : 0x1   Firmware Activate Without Reset Supported
  [3:1] : 0x2   Number of Firmware Slots
  [0:0] : 0     Firmware Slot 1 Read/Write

lpa       : 0x1e
  [6:6] : 0     Telemetry Log Data Area 4 Not Supported
  [5:5] : 0     LID 0x0, Scope of each command in LID 0x5, 0x12, 0x13 Not Supported
  [4:4] : 0x1   Persistent Event log Supported
  [3:3] : 0x1   Telemetry host/controller initiated log page Supported
  [2:2] : 0x1   Extended data for Get Log Page Supported
  [1:1] : 0x1   Command Effects Log Page Supported
  [0:0] : 0     SMART/Health Log Page per NS Not Supported

elpe      : 63
  [7:0] : 63 (0's based)        Error Log Page Entries (ELPE)

npss      : 4
  [7:0] : 4 (0's based) Number of Power States Support (NPSS)

avscc     : 0x1
  [0:0] : 0x1   Admin Vendor Specific Commands uses NVMe Format

apsta     : 0
  [0:0] : 0     Autonomous Power State Transitions Not Supported

wctemp    : 350
 [15:0] : 77 °C (350 K) Warning Composite Temperature Threshold (WCTEMP)

cctemp    : 358
 [15:0] : 85 °C (358 K) Critical Composite Temperature Threshold (CCTEMP)

mtfa      : 30
hmpre     : 0
hmmin     : 0
tnvmcap   : 3,840,755,982,336
[127:0] : 3,840,755,982,336
        Total NVM Capacity (TNVMCAP)

unvmcap   : 10,718,896,128
[127:0] : 10,718,896,128
        Unallocated NVM Capacity (UNVMCAP)

rpmbs     : 0
 [31:24]: 0     Access Size
 [23:16]: 0     Total Size
  [5:3] : 0     Authentication Method
  [2:0] : 0     Number of RPMB Units

edstt     : 12
dsto      : 1
fwug      : 1
kas       : 10
hctma     : 0
  [0:0] : 0     Host Controlled Thermal Management Not Supported

mntmt     : 0
 [15:0] : -273 °C (0 K) Minimum Thermal Management Temperature (MNTMT)

mxtmt     : 0
 [15:0] : -273 °C (0 K) Maximum Thermal Management Temperature (MXTMT)

sanicap   : 0x40000006
  [31:30] : 0x1 Media is not additionally modified after sanitize operation completes successfully
  [29:29] : 0   No-Deallocate After Sanitize bit in Sanitize command Supported
  [3:3] : 0     Media Verification and Post-Verification Deallocation state Not Supported
  [2:2] : 0x1   Overwrite Sanitize Operation Supported
  [1:1] : 0x1   Block Erase Sanitize Operation Supported
  [0:0] : 0     Crypto Erase Sanitize Operation Not Supported

hmminds   : 0
hmmaxd    : 0
nsetidmax : 0
endgidmax : 0
anatt     : 0
anacap    : 0
  [7:7] : 0     Non-zero group ID Not Supported
  [6:6] : 0     Group ID does change
  [4:4] : 0     ANA Change state Not Supported
  [3:3] : 0     ANA Persistent Loss state Not Supported
  [2:2] : 0     ANA Inaccessible state Not Supported
  [1:1] : 0     ANA Non-optimized state Not Supported
  [0:0] : 0     ANA Optimized state Not Supported

anagrpmax : 0
nanagrpid : 0
pels      : 24
domainid  : 0
megcap    : 0
tmpthha   : 0
  [2:0] : 0     Temperature Threshold Maximum Hysteresis

sqes      : 0x66
  [7:4] : 0x6   Max SQ Entry Size (64)
  [3:0] : 0x6   Min SQ Entry Size (64)

cqes      : 0x44
  [7:4] : 0x4   Max CQ Entry Size (16)
  [3:0] : 0x4   Min CQ Entry Size (16)

maxcmd    : 16
nn        : 64
oncs      : 0x5e
  [10:10] : 0   All Fast Copy Not Supported
  [9:9] : 0     Copy Single Atomicity Not Supported
  [8:8] : 0     Copy Not Supported
  [7:7] : 0     Verify Not Supported
  [6:6] : 0x1   Timestamp Supported
  [5:5] : 0     Reservations Not Supported
  [4:4] : 0x1   Save and Select Supported
  [3:3] : 0x1   Write Zeroes Supported
  [2:2] : 0x1   Data Set Management Supported
  [1:1] : 0x1   Write Uncorrectable Supported
  [0:0] : 0     Compare Not Supported

fuses     : 0
  [0:0] : 0     Fused Compare and Write Not Supported

fna       : 0
  [3:3] : 0     Format NVM Broadcast NSID (FFFFFFFFh) Supported
  [2:2] : 0     Crypto Erase Not Supported as part of Secure Erase
  [1:1] : 0     Crypto Erase Applies to Single Namespace(s)
  [0:0] : 0     Format Applies to Single Namespace(s)

vwc       : 0x6
  [2:1] : 0x3   The Flush command supports NSID set to FFFFFFFFh
  [0:0] : 0     Volatile Write Cache Not Present

awun      : 31
awupf     : 31
icsvscc   : 1
  [0:0] : 0x1   NVM Vendor Specific Commands uses NVMe Format

nwpc      : 0
  [2:2] : 0     Permanent Write Protect Not Supported
  [1:1] : 0     Write Protect Until Power Supply Not Supported
  [0:0] : 0     No Write Protect and Write Protect Namespace Not Supported

acwu      : 31
ocfs      : 0
  [3:3] : 0     Controller Copy Format 3h Not Supported
  [2:2] : 0     Controller Copy Format 2h Not Supported
  [1:1] : 0     Controller Copy Format 1h Not Supported
  [0:0] : 0     Controller Copy Format 0h Not Supported

sgls      : 0x100005
 [21:21]: 0     Transport SGL Data Block Descriptor Not Supported
 [20:20]: 0x1   Address Offsets Supported
 [19:19]: 0     Metadata Pointer Containing SGL Descriptor is Not Supported
 [18:18]: 0     SGL Length Larger than Buffer Not Supported
 [17:17]: 0     Byte-Aligned Contig. MD Buffer Not Supported
 [16:16]: 0     SGL Bit-Bucket Not Supported
 [15:8] : 0     SGL Descriptor Threshold
  [2:2] : 0x1   Keyed SGL Data Block descriptor Supported
  [1:0] : 0x1   Scatter-Gather Lists Supported. No Dword alignment required.

mnan      : 0
maxdna    : 0
maxcna    : 0
oaqd      : 0
subnqn    : nqn.1992-05.com.wdc.ofdata24-4113-uscos01923sb003-WDC-1X4:IOM-A.nvme.10
ioccsz    : 4
iorcsz    : 1
icdoff    : 0
fcatt     : 0
  [0:0] : 0     Dynamic Controller Model

msdbd     : 1
ofcs      : 0
  [0:0] : 0     Disconnect command Not Supported

ps      0 : mp:20.00W operational enlat:100000 exlat:100000 rrt:0 rrl:0
            rwt:0 rwl:0 idle_power:5.00W active_power:0.00W
            active_power_workload:-
ps      1 : mp:18.00W operational enlat:100000 exlat:100000 rrt:1 rrl:1
            rwt:1 rwl:1 idle_power:5.00W active_power:0.00W
            active_power_workload:-
ps      2 : mp:16.00W operational enlat:100000 exlat:100000 rrt:2 rrl:2
            rwt:2 rwl:2 idle_power:5.00W active_power:0.00W
            active_power_workload:-
ps      3 : mp:14.00W operational enlat:100000 exlat:100000 rrt:3 rrl:3
            rwt:3 rwl:3 idle_power:5.00W active_power:0.00W
            active_power_workload:-
ps      4 : mp:12.00W operational enlat:100000 exlat:100000 rrt:4 rrl:4
            rwt:4 rwl:4 idle_power:5.00W active_power:0.00W
            active_power_workload:-

I am attaching the output of SN655 and nvme cli 2.11 here

nvme wdc get-drive-status /dev/nvme0
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
 Drive Status :-
 Percent Used:                         40%
 Drive Life Status:                    Normal
 Assert Dump Status:                   Not Present
 Thermal Throttling Status:            Off
 Format Corrupt Reason:                Format Not Corrupted

From SN861 and nvme cli 2.11

nvme wdc get-drive-status /dev/nvme10
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
wdc_get_fw_cust_id: ERROR: WDC: 0xC2 Log Page entry ID 0x15 not found
wdc_get_enc_drive_capabilities: ERROR: WDC: invalid customer id
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
Not found, requesting log page with uuid_index 0
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: 0xC2 Log Page not supported

@jeff-lien-sndk Please let me know anything more required from my side.

[igaw]

Some of the low level commands wont work such as accessing the PCI registers but it should be rather limited. In the end nvme-cli/libnvme just issue NVMe commands via the ioctl interface. Not sure I understand the setup correctly. Is there an external enclosure? If so what protocol is used between the host and the enclosure. I haven't seen anything else than SCSI emulation enclosures on the market.

[jeff-lien-sndk]

@Sayoojntly I see uuid lists are not supported on that version of SN861. I'll need to check into this more to determine if there's a way to fix it.

[Sayoojntly]

Hi @jeff-lien-sndk ,
The issue still persists with NVMe WDC version 2.14.4. As we are currently blocked with the SN861 drives, could you please let us know the plan for addressing this fix, specifically for the SN861 drives?

#nvme  wdc version
nvme wdc version 2.14.4 (git 2.14)
libnvme version 1.14 (git 1.14)
#nvme sndk version
nvme sndk version 3.0.0 (git 2.14)
libnvme version 1.14 (git 1.14)

nvme wdc get-drive-status /dev/nvme0
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
wdc_get_fw_cust_id: ERROR: WDC: 0xC2 Log Page entry ID 0x15 not found
wdc_get_enc_drive_capabilities: ERROR: WDC: invalid customer id
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: 0xC2 Log Page not supported, uuid_index: 0


nvme sndk get-drive-status /dev/nvme0
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x15 not found with uuid index 0
wdc_get_fw_cust_id: ERROR: WDC: 0xC2 Log Page entry ID 0x15 not found
wdc_get_enc_drive_capabilities: ERROR: WDC: invalid customer id
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_dev_mng_log_entry: Detected unaligned end of the data. Data Offset: 0x8 Entry Size: 0x0, Remaining Log Length: 0xba Entry Id: 0x0
ERROR: WDC: C2 log id 0x8 not found with uuid index 0
ERROR: WDC: 0xC2 Log Page entry ID 0x8 not found
ERROR: WDC: 0xC2 Log Page not supported, uuid_index: 0

[sarabjotsoit]

Hi, @jeff-lien-sndk

I hope this is not a firmware limitation for SN861, as uuid lists are not supported according to your last comment

[jeff-lien-sndk]

I've asked our FW team about this and am still waiting on response from them.

[jeff-lien-sndk]

The FW team responded with "The SN861 product manual states that it does not support NVMe over fabrics". If this is a new requirement, you need to work with the Customer Support Team to get it raised to the FW team.

[sarabjotsoit]

Hi, @jeff-lien-sndk

We have checked with our SanDisk POC, and according to him, the Support is the same as that of the Ultrastar DC SN650 and SN655 NVMe SSDs.

Is there anything specific we are looking for ?

[Sayoojntly]

HI @jeff-lien-sndk
We updated the firmware on our NVMe-OF enclosure, but some of the sndk/wdc plug-in commands are still not functioning as expected. Please find the latest log attached for your reference.

wdc/sndk plug in commands vs-internal-log, vs-fw-activate-history and clear-fw-activate-history are not working on SN861.

nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme10n1         /dev/ng10n1           372415E0003810       SDS6BA138PSP9X1                          0x1          3.68  TB /   3.84  TB    512   B +  0 B   RH110X13
/dev/nvme11n1         /dev/ng11n1           372415E0010710       SDS6BA138PSP9X1                          0x1          3.68  TB /   3.84  TB    512   B +  0 B   RH110X13

#################################################################################
[root@r## ~]# nvme id-uuid /dev/nvme10n1
NVME Identify UUID:
 Entry[  1]
.................
association  : 0
UUID         : c194d55b-e094-4794-a21d-29998f56be6f
.................
 Entry[  2]
.................
association  : 0
UUID         : b5495d9b-f58f-7303-46c4-bfe9c2687a9b
.................
 Entry[  3]
.................
association  : 0
UUID         : 2db98c52-0c4c-5a15-abe6-33299a70dfd0
.................

#################################################################################
[root@r## ~]# nvme id-ctrl /dev/nvme10n1 -H |grep UUID
  [9:9] : 0x1   UUID List Supported

[root@r## ~]# nvme wdc get-drive-status /dev/nvme10
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
  Drive Status :-
  Percent Used:                         0%
  Drive Life Status:                    Normal
  Assert Dump Status:                   Not Present
  Thermal Throttling Status:            Off
  Format Corrupt Reason:                Format Not Corrupted

#################################################################################
[root@r## ~]# nvme wdc vs-internal-log /dev/nvme10
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
wdc_vs_internal_fw_log: filename = 372415E0003810_internal_fw_log_20250919_092246.bin
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: reading dump length failed
NVMe status: Invalid Command Opcode: A reserved coded value or an unsupported value in the command opcode field(0x4001)
INFO: WDC: Capture Diagnostics log is empty
#################################################################################
[root@r## ~]# nvme wdc vs-fw-activate-history /dev/nvme10
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
NVMe status: Invalid Log Page: The log page indicated is invalid(0x4109)
ERROR: WDC: Unable to read FW Activate History Log Page data
ERROR: WDC: Failure reading the FW Activate History, ret = -1

#################################################################################
[root@r## ~]# nvme wdc clear-fw-activate-history /dev/nvme10
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
ERROR: WDC: wdc_get_pci_ids : Open vendor file failed
NVMe status: Invalid Command Opcode: A reserved coded value or an unsupported value in the command opcode field(0x4001)

[jeff-lien-sndk]

The vs-internal-log, vs-fw-activate-history, and clear-fw-activate-history command failures are all due to the fact that the nvme cli plugin code can't read the pci device id in the Fabric attached case. Here's the directories that are used in the direct attached case to get the device id:
cat /sys/class/nvme/nvme1/device/device
or

cat /sys/class/nvme-generic/ng1n1/device/device/device

I have not found a way to get that same info in the fabric attached case. If anyone knows of a way to do so, I could look into implementing that.

An alternative command to collect the same data returned from the vs-internal-log is:
nvme telemetry-log /dev/nvme3 -g 1 -d 3 -m 3 --output-file nvme-telemetry-log.bin

Both commands return the host telemetry log data.

[igaw]

Should be addressed by #2926.