6.4TB Samsung PM1725a 5DWPD Enterprise TLC V-NAND PCIe 3.0 x8 NVMe HHHL AIC SSD NEW $999

AskFor

New Member
Mar 23, 2019
9
0
1
Well I have some good news!!!

We were lucky enough to get SuperMicro to give us a copy of the firmware for the generic/non-OEM pm1725a card.

Firmware is version GPNABB3Q.BIN This is even newer than the version they mentioned in the FAQ referenced above.

I've tested it and it flashes properly, now allows all 32 namespaces, and formatting the namespace (as well as who knows what other bug fixes).

Does anyone have a place where I can upload this for it to be hosted (it's 3.14MB unzipped)?

You will need to use nvme-cli to flash it.

Thanks to everyone above in giving me the hint to look there!
Christine
Dear HecatesChild, can you get PM1725b firmware from Supermicro?
 

ViciousXUSMC

Active Member
Nov 27, 2016
200
96
28
37
Waiting for end of year for a new PC build on a 4900x, 2x 2TB M2 NVMe SSD, etc.
Was looking at those PCIe 4.0 SSD's like the Sabrient Rocket, how would this compare you think as the main disk for a Windows 10 OS productivity/gaming computer?
 

rfs830

New Member
May 16, 2017
20
3
3
37
Waiting for end of year for a new PC build on a 4900x, 2x 2TB M2 NVMe SSD, etc.
Was looking at those PCIe 4.0 SSD's like the Sabrient Rocket, how would this compare you think as the main disk for a Windows 10 OS productivity/gaming computer?
I currently have a the a samsung 3.2tb U2 nvme drive in my windows 10 machines now and it has been working great. It is not my boot drive though as my board can not boot to it but I install all my games, vms and programs to that drive and I have no slowdowns.
 

HecatesChild

New Member
Jul 8, 2020
17
14
3
Dear HecatesChild, can you get PM1725b firmware from Supermicro?
Unfortunately, the only reason I had luck was because I had purchased a 10 pack of the PM1725a drives :(

It appears SuperMicro sold the PM1725b, so you might have some luck asking them yourself.
 

Mistruster

New Member
Jul 13, 2020
5
0
1
nvme_error.jpg


I am not sure what is the reason.
The hard drive always freezes before upgrading the firmware, and problems will occur after upgrading.


dmesg

blk_update_request: critical medium error, dev nvme0c0n1, sector 5291758864 op 0x0:(READ) flags 0x4000000 phys_seg 1 prio class 0
Buffer I/O error on dev nvme0n1p1, logical block 661469602, async page read
blk_update_request: critical medium error, dev nvme0c0n1, sector 5291758864 op 0x0:(READ) flags 0x4000000 phys_seg 1 prio class 0
Buffer I/O error on dev nvme0n1p1, logical block 661469602, async page read

smartctl -x /dev/nvme0

=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZPLL6T4HMLS-000MV
Serial Number: S459NA0K104233
Firmware Version: GPNABB3Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 6,401,252,745,216 [6.40 TB]
Unallocated NVM Capacity: 0
Controller ID: 33
Number of Namespaces: 32
Local Time is: Thu Jul 16 10:33:55 2020 CST
Firmware Updates (0x17): 3 Slots, Slot 1 R/O, no Reset required
Optional Admin Commands (0x000e): Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x003e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Resv
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 80 Celsius
Critical Comp. Temp. Threshold: 87 Celsius

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

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

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 48 Celsius
Available Spare: 56%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 8,209,981 [4.20 TB]
Data Units Written: 46,147,626 [23.6 TB]
Host Read Commands: 340,326,021
Host Write Commands: 737,463,326
Controller Busy Time: 986
Power Cycles: 238
Power On Hours: 123
Unsafe Shutdowns: 115
Media and Data Integrity Errors: 86,404
Error Information Log Entries: 79,990
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 48 Celsius
Temperature Sensor 2: 46 Celsius
Temperature Sensor 3: 46 Celsius

Error Information (NVMe Log 0x01, max 256 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 79990 8 0x034d 0xc502 0x000 8416478096 0 -
1 79989 8 0x036c 0xc502 0x000 8416478096 0 -
2 79988 8 0x036b 0xc502 0x000 8416478096 0 -
3 79987 8 0x036a 0xc502 0x000 8416478096 0 -
4 79986 4 0x03a6 0xc502 0x000 6129791512 0 -
5 79985 8 0x0365 0xc502 0x000 6129791512 0 -
6 79984 7 0x02cd 0xc502 0x000 6129791512 0 -
7 79983 7 0x0202 0xc502 0x000 6129791512 0 -
8 79982 3 0x01a1 0xc502 0x000 6129791504 0 -
9 79981 7 0x022b 0xc502 0x000 6129791504 0 -
10 79980 7 0x00d5 0xc502 0x000 6129791504 0 -
11 79979 7 0x03c9 0xc502 0x000 6129791504 0 -
12 79978 2 0x02b0 0xc502 0x000 6198808016 0 -
13 79977 2 0x02af 0xc502 0x000 6198808016 0 -
14 79976 2 0x02ae 0xc502 0x000 6198808016 0 -
15 79975 1 0x014c 0xc502 0x000 6219331032 0 -
... (240 entries not shown)
 

HecatesChild

New Member
Jul 8, 2020
17
14
3
Not sure what to tell you on this, but darn, looking at those stats the drive is throwing tons of errors... Any way you can try it in another machine just to see if it's a PCIe bus issue on the current machine it lives in?

Past that, from the logs you have posted (look at the sums), I suspect your card/drive is having issues... :(

I have 10 of them I've done this FW upgrade to, and all seemed happy, showed the proper firmware afterwards, Allowed namespacing afterwards (though won't show results if you didn't reboot between FW update and # of namespace adjustments)

Sorry I can't be of more help
 

StevenDTX

Active Member
Aug 17, 2016
407
137
43
To use it, you will issue the following nvme-cli commands (sudo'd obviously) replace # in nvme# with the number shown on your linux boot when you type nvme list. (these instructions are massaged from IBM's update instructions.)

**READ THIS WHOLE THING BEFORE STARTING** if I typo'd I apologize.

# This puts the firmware into slot 2 normally. (the -s 2 below) You can confirm via nvme fw-log /dev/nvme# if that is the slot it gets loaded into, in step 1 below

# step 1 - load the firmware into adapter
nvme fw-download /dev/nvme# --fw=firmwarefilename.bin

# step 2 - Confirms/validates the firmware in slot 2 is valid
nvme fw-activate /dev/nvme# -a 0 -s 2

# step 3 - Applies firmware in slot 2
nvme fw-activate /dev/nvme# -a 3 -s 2

# At this point you are done. If you change any namespaces before rebooting, you will only see the changes to namespace 1 until you reboot (however they were all be there after reboot)

# Confirm the new firmware is the current and to be loaded upon boot firmware
nvme list

# You will also notice if you do an nvme id-ctl -H that now the supported features are different than they were before (namespaces are supported, formatting is supported, etc)
Thank you for this!! I was able to update the firmware on the ones I bought today.
 
  • Like
Reactions: HecatesChild

Mistruster

New Member
Jul 13, 2020
5
0
1
How to initialize the disk, including the others namespace, opcode ?

critical medium error, dev nvme0c0n1, sector 5391725392

It's dev nvme0c0n1, NOT nvme0n1

Am I doing something wrong.
 

redeamon

Active Member
Jun 10, 2018
155
58
28
How to initialize the disk, including the others namespace, opcode ?

critical medium error, dev nvme0c0n1, sector 5391725392

It's dev nvme0c0n1, NOT nvme0n1

Am I doing something wrong.
Try formatting the namespace.

nvme format /dev/nvme#
 

Garlaen

New Member
Aug 3, 2020
1
5
3
Thanks for posting the firmware!!

I made an account to post the instructions on how to flash the drive in Windows 10/Server 2016/19.

Run PowerShell as an Administrator

Get the info on your Samsung NVME - verify it looks correct.

> Get-PhysicalDisk -FriendlyName "SAMSUNG MZPLL6T4HMLS-000MV" | Get-StorageFirmwareInformation

Object : MSFT_PhysicalDisk (ObjectId = "{1}\\<MACHINE_NAME>\root/Microsoft/Window...)
SupportsUpdate : True
NumberOfSlots : 3
ActiveSlotNumber : 1
SlotNumber : {1, 2, 3}
IsSlotWritable : {False, True, True}
FirmwareVersionInSlot : {<ORIGINAL_FIRMWARE>, , }


Update the firmware.

> Get-PhysicalDisk -FriendlyName "SAMSUNG MZPLL6T4HMLS-000MV" | Update-StorageFirmware -ImagePath "<PATH_TO_NEW_FIRMWARE>" -SlotNumber 2

Then you can run the first command again to verify that it contains two firmware versions and that the active firmware slot is now 2.

Object : MSFT_PhysicalDisk (ObjectId = "{1}\\<MACHINE_NAME>\root/Microsoft/Window...)
SupportsUpdate : True
NumberOfSlots : 3
ActiveSlotNumber : 2
SlotNumber : {1, 2, 3}
IsSlotWritable : {False, True, True}
FirmwareVersionInSlot : {<ORIGINAL_FIRMWARE>, <NEW_FIRMWARE>, }
 

HecatesChild

New Member
Jul 8, 2020
17
14
3
Very nice! Thanks for the update. Now if we could just change namespaces from with windows/powershell... :)