Intel SSD DC P4500 15.3TB - "Disable Logical State" "NVMe Status 0x4006"- anything to do ?

[netswitch]

Yes. Well the seller seems to be a ltd company but the drives came from China.

 

[Mithril]

Necro bump but, I have a P4600 I've been using for years that seems to have entered this state. Working fine, then:

kernel: nvme nvme1: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x10
kernel: nvme nvme1: I/O 24 QID 0 timeout, disable controller
kernel: nvme nvme1: Identify Controller failed (-4)
kernel: nvme nvme1: Disabling device after reset failure: -5
kernel: I/O error, dev nvme1n1, sector 5254207024 op 0x1WRITE) flags 0x0 phys_seg 1 prio class 2
kernel: I/O error, dev nvme1n1, sector 5254207032 op 0x1WRITE) flags 0x0 phys_seg 1 prio class 2
kernel: zio pool=SSD vdev=/dev/disk/by-partuuid/087b72fe-bd75-477a-9219-80adb09f58b1 error=5 type=2 offset=2688006447104 size=4096 flags=1589376
kernel: zio pool=SSD vdev=/dev/disk/by-partuuid/087b72fe-bd75-477a-9219-80adb09f58b1 error=5 type=2 offset=2688006451200 size=4096 flags=1589376
[...]

After a reboot it shows in lspci but not lsblk. It shows up in smartctl, with 0 namespaces and:

=== START OF SMART DATA SECTION ===
Read NVMe SMART/Health Information failed: Internal Error (0x4006)



size is listed as

Total NVM Capacity: 69,793,218,560 [69.7 GB]


despite being a 3.2TB drive.

Checked the serial (in case I got my drivehistory mixed up), its a valid serial but warrenty expired start of the year.


isdct show -a -intelssd has a lot of "Selected drive is in a disable logical state"

 

[netswitch]

I guess that unless we have access to the rom of the drive to reflash it is dead..

 

[pimposh]

All of Intel drives i've had with Disabled logical state ended up being rma’ed. Not a single revival was successful.

 

[jhartbarger]

Tested both solidigm and intel firmware update iso but they don' want to perform the update, I also tested with the SST tool and same issue.
The " Selected drive is in a disable logical state " status seems to prevent the software to work on the drive.

I read that these drives had a huge failure rate, I am convinced this is software related as two drives failing "at the same" time is very unlikely.
I ll keep digging but beside RMA which I won't qualify for, I guess there is no clear solution.

Based on what you have said it sure sounds like the drives experienced a firmware panic, Usually when this error occurs the drive suffered a major circuit failure but since both drives are doing the exact same thing and failed at the same time that's the logical conclusion.

Pretty much the only thing you can try is to run command intelmas load -f -intelssd 0 from the Intel MAS Toolkit and if that fails the drives are junk.

 

[netswitch]

Thanks for chiming in, never knew about the Intel MAS Toolkit, I will give it a try

 

[jhartbarger]

Give it a whirl, refer to the documentation for any syntax issues.

 

[jhartbarger]

Any luck?

 

[netswitch]

Unfortunately not, tryed various approaches in between with the help of gtp and claude but it seems that when the firmwares decides to put the drive in "disabled logical state" it is bricked. (Or it requires some proprietary intel/solidigm tools that are not published.)
I could get the logs after some poking around but nothing really interesting there.

 

[jhartbarger]

That sucks but we win some and we loose some.