Community
cancel
Showing results for 
Search instead for 
Did you mean: 
NQuig
Beginner
1,594 Views

Intel P3600 can't format between LBAFs

I have an Intel P3600 drive formatted to LBAF=2 (lbaf 2 : ms:16 ds:9 rp:0x2 (in use)). I can no longer format to different LBAFs. Drive FW is 8DV101F0, which I believe is the latest. This persists across reboots, power cycles, etc.

[root@VLUNnvme ~]# nvme id-ns /dev/nvme2n1 -n 1

NVME Identify Namespace 1:

nsze : 0x2e9390b0

ncap : 0x2e9390b0

nuse : 0x2e9390b0

nsfeat : 0

nlbaf : 6

flbas : 0x12

mc : 0x1

dpc : 0x11

dps : 0

nmic : 0

rescap : 0

fpi : 0

nawun : 0

nawupf : 0

nacwu : 0

nabsn : 0

nabo : 0

nabspf : 0

nvmcap : 0

nguid : 00000000000000000000000000000000

eui64 : 0000000000000000

lbaf 0 : ms:0 ds:9 rp:0x2

lbaf 1 : ms:8 ds:9 rp:0x2

lbaf 2 : ms:16 ds:9 rp:0x2 (in use)

lbaf 3 : ms:0 ds:12 rp:0

lbaf 4 : ms:8 ds:12 rp:0

lbaf 5 : ms:64 ds:12 rp:0

lbaf 6 : ms:128 ds:12 rp:0

[root@VLUNnvme ~]# nvme format /dev/nvme2n1 -lbaf 1

Success formatting namespace:1

[root@VLUNnvme ~]# nvme id-ns /dev/nvme2n1 -n 1

NVME Identify Namespace 1:

nsze : 0x2e9390b0

ncap : 0x2e9390b0

nuse : 0x2e9390b0

nsfeat : 0

nlbaf : 6

flbas : 0x12

mc : 0x1

dpc : 0x11

dps : 0

nmic : 0

rescap : 0

fpi : 0

nawun : 0

nawupf : 0

nacwu : 0

nabsn : 0

nabo : 0

nabspf : 0

nvmcap : 0

nguid : 00000000000000000000000000000000

eui64 : 0000000000000000

lbaf 0 : ms:0 ds:9 rp:0x2

lbaf 1 : ms:8 ds:9 rp:0x2

lbaf 2 : ms:16 ds:9 rp:0x2 (in use)

lbaf 3 : ms:0 ds:12 rp:0

lbaf 4 : ms:8 ds:12 rp:0

lbaf 5 : ms:64 ds:12 rp:0

lbaf 6 : ms:128 ds:12 rp:0

0 Kudos
9 Replies
idata
Community Manager
175 Views

NickQuigley,

 

 

Considering the information you have sent us, could you please try to format it by using the following tool:https://downloadcenter.intel.com/download/26221/Intel-SSD-Data-Center-Tool?product=87278 Intel® SSD Data Center Tool and execute the NVMe* format stating on page # 39 through # 42 of this guide: http://www.intel.com/content/dam/support/us/en/documents/solid-state-drives/ssd-software/Intel_SSD_D... Intel® Solid State Drive Data Center Tool - User Guide

 

 

Let us know if this helped you.

 

 

Best regards,

 

Aleki
NQuig
Beginner
175 Views

Hi Aleki,

This didn't address the issue. Here is the identify namespace info showing that we are using LBAF=2

[root@vlun200 ~]# isdct show -identify -namespace 1 -intelssd 0

- Identify Namespace CVMD449200B7400FGN -

- Byte 0-7 -

Namespace Size : 781422768

- Byte 8-15 -

Namespace Capacity : 781422768

- Byte 16-23 -

Namespace Utilization : 781422768

- Byte 24 -

Namespace Features : 0

Bit 7:1 - Reserved : 0

Bit 0 - Thin Provisioning Support : 0

- Byte 25 -

Number of LBA Formats : 6

- Byte 26 -

Formatted LBA Size : 12

Bit 7:5 - Reserved : 0

Bit 4 - Metadata transfer bit : 1

Bit 0:3 - LBA Format Support : 2

I then do the format to LBAF=0

[root@vlun200 ~]# isdct start -intelssd 0 -nvmeformat LBAFormat=0 ProtectionInformation=0

WARNING! You have selected to format the drive!

Proceed with the format? (Y|N): y

Formatting...

- Intel SSD DC P3600 Series CVMD449200B7400FGN -

Status : NVMeFormat successful.

But after the format, the namespace still uses LBAF=2

[root@vlun200 ~]# isdct show -identify -namespace 1 -intelssd 0

- Identify Namespace CVMD449200B7400FGN -

- Byte 0-7 -

Namespace Size : 781422768

- Byte 8-15 -

Namespace Capacity : 781422768

- Byte 16-23 -

Namespace Utilization : 781422768

- Byte 24 -

Namespace Features : 0

Bit 7:1 - Reserved : 0

Bit 0 - Thin Provisioning Support : 0

- Byte 25 -

Number of LBA Formats : 6

- Byte 26 -

Formatted LBA Size : 12

Bit 7:5 - Reserved : 0

Bit 4 - Metadata transfer bit : 1

Bit 0:3 - LBA Format Support : 2

idata
Community Manager
175 Views

NickQugley,

 

 

Thank you for the clarification. In this particular case we are going to engage additional resources to address this situation. In the mean time, please let us know if there any other piece of relevant information you would like to share.

 

 

Best regards,

 

Aleki
idata
Community Manager
175 Views

NickQuigley,

 

 

Thank you for your time. Could you please confirm that this drive is attached to the board or are you using something else such as a RAID controller? If so, could you please be so kind and use it directly on the board and trey a secure erase?

 

 

Please let us know the results as soon as you can.

 

 

Best regards,

 

Aleki
NQuig
Beginner
175 Views

Aleki,

Yes, this drive is directly attached to the board. Secure Erase didn't help:

Before Secure Erase:

[root@VLUN127 Drive FW]# isdct show -identify -namespace 1 -intelssd 0

- Identify Namespace CVMD449200B7400FGN -

- Byte 0-7 -

Namespace Size : 781422768

- Byte 8-15 -

Namespace Capacity : 781422768

- Byte 16-23 -

Namespace Utilization : 781422768

- Byte 24 -

Namespace Features : 0

Bit 7:1 - Reserved : 0

Bit 0 - Thin Provisioning Support : 0

- Byte 25 -

Number of LBA Formats : 6

- Byte 26 -

Formatted LBA Size : 12

Bit 7:5 - Reserved : 0

Bit 4 - Metadata transfer bit : 1

Bit 0:3 - LBA Format Support : 2

Secure Erase:

[root@VLUN127 Drive FW]# isdct start -intelssd 0 -nvmeformat SecureEraseSetting=1

WARNING! You have selected to format the drive!

Proceed with the format? (Y|N): y

Formatting...

- Intel SSD DC P3600 Series CVMD449200B7400FGN -

Status : NVMeFormat successful.

Format to LBAF=0:

[root@VLUN127 Drive FW]# isdct start -intelssd 0 -nvmeformat LBAFormat=0 ProtectionInformation=0

WARNING! You have selected to format the drive!

Proceed with the format? (Y|N): y

Formatting...

- Intel SSD DC P3600 Series CVMD449200B7400FGN -

Status : NVMeFormat successful.

Check again, and we are still at LBAF=2

[root@VLUN127 Drive FW]# isdct show -identify -namespace 1 -intelssd 0

- Identify Namespace CVMD449200B7400FGN -

- Byte 0-7 -

Namespace Size : 781422768

- Byte 8-15 -

Namespace Capacity : 781422768

- Byte 16-23 -

Namespace Utilization : 781422768

- Byte 24 -

Namespace Features : 0

Bit 7:1 - Reserved : 0

Bit 0 - Thin Provisioning Support : 0

- Byte 25 -

Number of LBA Formats : 6

- Byte 26 -

Formatted LBA Size : 12

Bit 7:5 - Reserved : 0

Bit 4 - Metadata transfer bit : 1

Bit 0:3 - LBA Format Support : 2

-Nick

idata
Community Manager
175 Views

NickQuigley,

 

 

Thank for the report, based on this, could you please be so kind run the tool found in this link: https://github.com/linux-nvme/nvme-cli

 

 

Follow the steps found in this very website so you can use it to install the source for the distribution you intend to use. Use the command to format found in this link: https://github.com/linux-nvme/nvme-cli/blob/master/Documentation/nvme-format.txt

 

 

Here is an example nvme format /dev/nvme0n1 and check the LBAF is set to 0.

 

Let us know if this helped you,

 

 

Best regards,

 

Aleki

 

NQuig
Beginner
175 Views

Aleki,

This did not help either:

[root@vlun118 ~]# nvme id-ns /dev/nvme1n1 -n 1 | grep lbaf

nlbaf : 6

lbaf 0 : ms:0 ds:9 rp:0x2

lbaf 1 : ms:8 ds:9 rp:0x2

lbaf 2 : ms:16 ds:9 rp:0x2 (in use)

lbaf 3 : ms:0 ds:12 rp:0

lbaf 4 : ms:8 ds:12 rp:0

lbaf 5 : ms:64 ds:12 rp:0

lbaf 6 : ms:128 ds:12 rp:0

[root@vlun118 ~]# nvme format /dev/nvme1n1 -n 1 -l 0 -i 0

Success formatting namespace:1

[root@vlun118 ~]# nvme id-ns /dev/nvme1n1 -n 1 | grep lbaf

nlbaf : 6

lbaf 0 : ms:0 ds:9 rp:0x2

lbaf 1 : ms:8 ds:9 rp:0x2

lbaf 2 : ms:16 ds:9 rp:0x2 (in use)

lbaf 3 : ms:0 ds:12 rp:0

lbaf 4 : ms:8 ds:12 rp:0

lbaf 5 : ms:64 ds:12 rp:0

lbaf 6 : ms:128 ds:12 rp:0

Would it be helpful to RMA one of the drives exhibiting this behavior? This is being done in an engineering/QA environment so we would be open to returning a drive on an RMA if it helps root cause the issue.

-Nick

idata
Community Manager
175 Views

NickQuigley,

 

 

Thank you for taking the time and trying the steps suggested. We are going to inform your results to our engineering department and will get back to you as soon as possible.

 

 

Best regards,

 

Aleki
idata
Community Manager
175 Views

NickQuigley,

 

 

Thank you for your time. In order for us to move into the next step, there is some information we need in order to provide all the support you need. Could you please be so kind and look at the private message we have sent you?

 

 

Best regards,

 

Aleki
Reply