Users Guide
Linux messages log may report the following entries on a write attempt to an NVMe PCIe SSD:
• Buffer I/O error on device nvmeXn1, logical block Y (where X is the number
corresponding to the device and Y is the logical block)
• nvmeXn1: unable to read partition table (where X is the number corresponding
to the device)
Cause NVMe PCIe SSDs have a nite number of write cycles. When an NVMe PCIe SSD exhausts the number of writes,
it goes into Write Protect (Read Only) mode.
Solution By using system management applications, you may check the NVMe PCIe SSD state to conrm if the NVMe PCIe
SSD is in Read-Only Mode. For further instructions, contact a Dell Technical Service representative.
NVMe PCIe SSD performance measurement not optimal
Description There are a number of factors that may alter the performance of an NVMe PCIe SSD. Dell recommends to take
basic setup measures to ensure performance optimization of these devices.
Cause NVMe PCIe SSD has not been preconditioned and/or BIOS settings are not optimal.
Solution
• Without preconditioning the NVMe PCIe SSD, performance measurements can be misleading as they may not
reect long-term performance of the device. Preconditioning enables ash management, which stabilizes data
throughput over a period. For the Solid-State Storage Performance Test Specication, see snia.org.
• Congure the server for low latency performance. To achieve maximum performance with NVMe PCIe SSDs,
change the server performance prole in the BIOS settings to Performance.
In Windows Server, OpenManage Server Administrator does
not detect PCIe NVMe devices
In Windows Server 2012 R2
Description
Windows Server 2012 R2 contains an in-box NVMe driver that is not supported by OpenManage Server
Administrator.
Cause The operating system is using the in-box NVMe driver.
Solution Install the latest NVMe driver available on Dell.com/support.
In Windows Server 2016
Description
Windows Server 2016 contains an in-box NVMe driver that is supported by OpenManage Server Administrator.
Cause The operating system is not using the in-box or required NVMe driver.
Solution Remove any NVMe drivers that is not specically released for the Windows Server 2016.
Troubleshooting 23