cancel
Showing results for 
Search instead for 
Did you mean: 

P3600 can't switch LBAF after update firmware

Mac
New Contributor II

I have a P3600 SSD firmware updated from 8DV1MD32 and to 8DV1ND38. After firmware updated to this version, it can't switch LBAF by using Linux nvme format command and it stuck on LBAF4. How can I solve this problem? Thanks!

1 ACCEPTED SOLUTION

Mac
New Contributor II

Hi Santiago,

Thank you for the reply, I just ask this problem in Lenovo's forum. This thread can be closed.

View solution in original post

10 REPLIES 10

Santiago_A_Inte
Contributor III
Hello Mac, Thank you for contacting Intel® SSD Support. In order to further assist you regarding your inquiry related to your Intel® SSD DC P3600 Series. We will appreciate if you can provide us with the following information: • The SSU logs. 1- Go to https://downloadcenter.intel.com/download/26735/ and download the software. 2- When finished downloading it, open it. 3- Attach the file obtained to your reply. • The SMART logs extracted from your Intel® SSD DC P3600 Series. The Intel’s Data Center Tool (DCT) can be used to read out the SMART attributes to download this tool please follow this link: https://downloadcenter.intel.com/download/28594/Intel-SSD-Data-Center-Tool-Intel-SSD-DCT-?v=t For further information on how to use this tool, in order to extract the SMART logs, please visit the Intel® Solid State Drive Data Center Tool User guide (https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/Intel_SSD_DCT_3_0_x_Use... ) page 25 section 2.1.3. We will be looking forward to your reply. Have a nice day. Best regards, Santiago A. Intel® Customer Support Technician Under Contract to Intel Corporation

Mac
New Contributor II

SSU logs

Mac
New Contributor II

SMART logs P3600

Mac
New Contributor II

I can use nvme-cli switch lbaf without problem before update firmware.

Now I get error return code below.

# nvme format -n 1 -l 0 /dev/nvme0

NVME Admin command error:INTERNAL: The command was not completed successfully due to an internal error(6)