topic Re: P4510 bricked after upgrade to firmware VDV10194 in Solid State Drives (NAND)

P4510 bricked after upgrade to firmware VDV10194

mrps01 — Mon, 15 Sep 2025 06:58:47 GMT

Hello,

I have a system with (4) 2TB Intel SSDPE2KX020T8

I used the Solidigm Storage Tool to upgrade them to the latest firmware version VDV10194 and now 3 of the 4 drives are missing their namespace.

One drive works fine and shows a 2TB namespace, the other 3 drives now show no namespace with 100% reserved space and the drive is not enabled to create namespaces meaning I am now stuck with a drive with 0 namespaces.

All drives showed up and had namespace before the firmware update.

Any help is appreciated.

Thank you

Re: P4510 bricked after upgrade to firmware VDV10194

SolidigmGleb — Mon, 15 Sep 2025 08:45:55 GMT

Dear mrps01,

Thank you for sharing the details of your issue. In some cases, after a firmware update, namespaces may not be properly initialised. To help troubleshoot, could you please try the following:

Use the Solidigm Storage Tool (SST) to check if the drives are detected and attempt to create or restore namespaces.
If namespaces cannot be created, please try the Solidigm Bootable Firmware Update Tool, which may reinitialise the drives correctly.
Make sure you are on the latest SST version before retrying.

If the problem continues, please contact Solidigm Customer Support directly with the affected drives’ serial numbers so we can investigate further.

If you need further assistance or have additional questions, please

Best regards,

Gleb
Solidigm Customer Support

Re: P4510 bricked after upgrade to firmware VDV10194

mrps01 — Mon, 15 Sep 2025 12:46:16 GMT

Hello,

I have boot the Bootable Firmware Update Tool however, after accepting the terms I am immediately given a screen saying all drives are up to date and it wants to shutdown. There is no option to manually re-initialize the firmware. Am I missing something?

Thanks

Re: P4510 bricked after upgrade to firmware VDV10194

mrps01 — Mon, 15 Sep 2025 13:51:28 GMT

Here are some command outputs from SST:
root@debian:~# nvme id-ctrl /dev/nvme0 | grep -i tnvmcap
tnvmcap : 1,920,383,410,176
root@debian:~# nvme id-ctrl /dev/nvme0 | grep -i unvmcap
unvmcap : 0
root@debian:~# nvme format /dev/nvme0
get-namespace-id: Inappropriate ioctl for device
root@debian:~# nvme create-ns /dev/nvme0 -s 10000 -c 10000 -f 0
NVMe status: Namespace Insufficient Capacity: Creating the namespace requires more free space than is currently available(0x4115)
root@debian:~# nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x8086
ssvid : 0x8086
sn : XXXXXXXXXXXXXXXXXXX
mn : INTEL SSDPE2KX020T8
fr : VDV10194
rab : 0
ieee : 5cd2e4
cmic : 0
mdts : 5
cntlid : 0
ver : 0x10200
rtd3r : 0x1e8480
rtd3e : 0x2dc6c0
oaes : 0x200
ctratt : 0
rrls : 0
cntrltype : 0
fguid : 00000000-0000-0000-0000-000000000000
crdt1 : 0
crdt2 : 0
crdt3 : 0
nvmsr : 0
vwci : 0
mec : 1
oacs : 0x6
acl : 3
aerl : 3
frmw : 0x18
lpa : 0xe
elpe : 63
npss : 0
avscc : 0
apsta : 0
wctemp : 343
cctemp : 353
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 1,920,383,410,176
unvmcap : 0
rpmbs : 0
edstt : 0
dsto : 0
fwug : 0
kas : 0
hctma : 0
mntmt : 0
mxtmt : 0
sanicap : 0
hmminds : 0
hmmaxd : 0
nsetidmax : 0
endgidmax : 0
anatt : 0
anacap : 0
anagrpmax : 0
nanagrpid : 0
pels : 0
domainid : 0
megcap : 0
sqes : 0x66
cqes : 0x44
maxcmd : 0
nn : 128
oncs : 0x6
fuses : 0
fna : 0x4
vwc : 0
awun : 0
awupf : 0
icsvscc : 0
nwpc : 0
acwu : 0
ocfs : 0
sgls : 0
mnan : 0
maxdna : 0
maxcna : 0
subnqn :
ioccsz : 0
iorcsz : 0
icdoff : 0
fcatt : 0
msdbd : 0
ofcs : 0
ps 0 : mp:14.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
active_power_workload:-
root@debian:~#

nvme0 appears in /dev but not in nvme list

Re: P4510 bricked after upgrade to firmware VDV10194

mrps01 — Mon, 15 Sep 2025 15:05:33 GMT

Hello,

I was able to retrieve and attach the namespace for nvme0, nvme1 and nvme3. Now I have a new problem. All drives used to show as 2TB now nvme0/1/3 are showing 1.92TB, nvme2 which flashed correctly shows the correct size of 2TB. I am unable to add these back to my raid now as they are not the correct 2TB size. smartctl does not show any unallocated space. Is there any way to retrieve the lost space? The drives are all identical model and all functioned at 2tb size before the firmware update.

Below is the output of nvme0 (incorrect size) and then nvme2 (correct size):

debian# nvme attach-ns /dev/nvme0 -n 1 -c 0
attach-ns: Success, nsid:1

root@debian:~# nvme ns-rescan /dev/nvme3
root@debian:~# nvme list
Node Generic SN Model Namespace Usage Format FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme3n1 /dev/ng3n1 BTLJ9XXXXXP0BGN INTEL SSDPE2KX020T8 1 1.92 TB / 1.92 TB 512 B + 0 B VDV10194
/dev/nvme2n1 /dev/ng2n1 BTLJ9XXXXXP0BGN INTEL SSDPE2KX020T8 1 2.00 TB / 2.00 TB 512 B + 0 B VDV10194
/dev/nvme1n1 /dev/ng1n1 BTLJ9XXXXXP0BGN INTEL SSDPE2KX020T8 1 1.92 TB / 1.92 TB 512 B + 0 B VDV10194
/dev/nvme0n1 /dev/ng0n1 BTLJ9XXXXXP0BGN INTEL SSDPE2KX020T8 1 1.92 TB / 1.92 TB 512 B + 0 B VDV10194
root@debian:~#
root@debian:~# nvme list-ns /dev/nvme0
[ 0]:0x1
root@debian:~# nvme id-ns -H /dev/nvme0n1
NVME Identify Namespace 1:
nsze : 0xdf8fe2b0
ncap : 0xdf8fe2b0
nuse : 0xdf8fe2b0
nsfeat : 0
[4:4] : 0 NPWG, NPWA, NPDG, NPDA, and NOWS are Not Supported
[3:3] : 0 NGUID and EUI64 fields if non-zero, Reused
[2:2] : 0 Deallocated or Unwritten Logical Block error Not Supported
[1:1] : 0 Namespace uses AWUN, AWUPF, and ACWU
[0:0] : 0 Thin Provisioning Not Supported

nlbaf : 1
flbas : 0
[6:5] : 0 Most significant 2 bits of Current LBA Format Selected
[4:4] : 0 Metadata Transferred in Separate Contiguous Buffer
[3:0] : 0 Least significant 4 bits of Current LBA Format Selected

mc : 0
[1:1] : 0 Metadata Pointer Not Supported
[0:0] : 0 Metadata as Part of Extended Data LBA Not Supported

dpc : 0
[4:4] : 0 Protection Information Transferred as Last 8 Bytes of Metadata Not Supported
[3:3] : 0 Protection Information Transferred as First 8 Bytes of Metadata Not Supported
[2:2] : 0 Protection Information Type 3 Not Supported
[1:1] : 0 Protection Information Type 2 Not Supported
[0:0] : 0 Protection Information Type 1 Not Supported

dps : 0
[3:3] : 0 Protection Information is Transferred as Last 8 Bytes of Metadata
[2:0] : 0 Protection Information Disabled

nmic : 0
[0:0] : 0 Namespace Multipath Not Capable

rescap : 0
[7:7] : 0 Ignore Existing Key - Used as defined in revision 1.2.1 or earlier
[6:6] : 0 Exclusive Access - All Registrants Not Supported
[5:5] : 0 Write Exclusive - All Registrants Not Supported
[4:4] : 0 Exclusive Access - Registrants Only Not Supported
[3:3] : 0 Write Exclusive - Registrants Only Not Supported
[2:2] : 0 Exclusive Access Not Supported
[1:1] : 0 Write Exclusive Not Supported
[0:0] : 0 Persist Through Power Loss Not Supported

fpi : 0
[7:7] : 0 Format Progress Indicator Not Supported

dlfeat : 0
[4:4] : 0 Guard Field of Deallocated Logical Blocks is set to 0xFFFF
[3:3] : 0 Deallocate Bit in the Write Zeroes Command is Not Supported
[2:0] : 0 Bytes Read From a Deallocated Logical Block and its Metadata are Not Reported

nawun : 0
nawupf : 0
nacwu : 0
nabsn : 0
nabo : 0
nabspf : 0
noiob : 0
nvmcap : 1,920,383,410,176
mssrl : 0
mcl : 0
msrc : 0
nulbaf : 0
anagrpid: 0
nsattr : 0
nvmsetid: 0
endgid : 0
nguid : 01000000010000005cd2e437fd3f5051
eui64 : 5cd2e437fd3f0100
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0x2 Good (in use)
LBA Format 1 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best
root@debian:~#
root@debian:~# smartctl -a /dev/nvme0
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-39-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: INTEL SSDPE2KX020T8
Serial Number: BTLJ9XXXXXP0BGN
Firmware Version: VDV10194
PCI Vendor/Subsystem ID: 0x8086
IEEE OUI Identifier: 0x5cd2e4
Total NVM Capacity: 1,920,383,410,176 [1.92 TB]
Unallocated NVM Capacity: 0
Controller ID: 0
NVMe Version: 1.2
Number of Namespaces: 128
Local Time is: Mon Sep 15 08:01:25 2025 PDT
Firmware Updates (0x18): 4 Slots, no Reset required
Optional Admin Commands (0x0006): Format Frmw_DL
Optional NVM Commands (0x0006): Wr_Unc DS_Mngmt
Log Page Attributes (0x0e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 70 Celsius
Critical Comp. Temp. Threshold: 80 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 14.00W - - 0 0 0 0 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 25 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 937,036 [479 GB]
Data Units Written: 8,674,810 [4.44 TB]
Host Read Commands: 11,134,691
Host Write Commands: 420,128,424
Controller Busy Time: 15
Power Cycles: 103
Power On Hours: 3,722
Unsafe Shutdowns: 96
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

root@debian:~#

root@debian:~# smartctl -a /dev/nvme2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-39-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: INTEL SSDPE2KX020T8
Serial Number: BTLJ9XXXXXP0BGN
Firmware Version: VDV10194
PCI Vendor/Subsystem ID: 0x8086
IEEE OUI Identifier: 0x5cd2e4
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 0
NVMe Version: 1.2
Number of Namespaces: 128
Local Time is: Mon Sep 15 08:01:47 2025 PDT
Firmware Updates (0x18): 4 Slots, no Reset required
Optional Admin Commands (0x000e): Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x0006): Wr_Unc DS_Mngmt
Log Page Attributes (0x0e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 70 Celsius
Critical Comp. Temp. Threshold: 80 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 14.00W - - 0 0 0 0 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 23 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 1,843,689 [943 GB]
Data Units Written: 6,466,647 [3.31 TB]
Host Read Commands: 13,268,824
Host Write Commands: 220,049,759
Controller Busy Time: 20
Power Cycles: 103
Power On Hours: 3,722
Unsafe Shutdowns: 96
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

root@debian:~#

Re: P4510 bricked after upgrade to firmware VDV10194

SolidigmGleb — Tue, 16 Sep 2025 09:59:26 GMT

Hello,

Thank you for the detailed information and logs. Based on your output, the drives that now show 1.92 TB instead of 2.00 TB appear to have undergone a namespace/format capacity change during the firmware update. This behavior can happen when the namespace is recreated with slightly different LBA settings.

A few steps you can try:

Use the nvme format command to reinitialize the namespace and restore full capacity.
Alternatively, delete and recreate the namespace with the maximum size available (nvme delete-ns followed by nvme create-ns).
Please make sure you have backups of any data before attempting these steps, as they will erase all contents.

If these actions don’t restore the full 2.00 TB, we recommend opening a support case with us directly at Solidigm Support so we can review in detail.

Kind regards,

Gleb
Solidigm Customer Support