PM863 FW File

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

jei

Active Member
Aug 8, 2021
174
90
28
Finland
Cannot say for certain but it seems that the "sub 1048576" 512 bytes contains a new firmware version string in DarkServant's fw files. What is the source for these? In the Dell fw files there is no such version string.
 

mustamyy

New Member
Dec 3, 2022
1
1
1
Thanks for the instructions.
I was able to resurrect a PM863 (MZ7LM960HCHP-0E003) in ERRMOD state with fohdeesha's instructions and Dell GA3B firmware (here).

Trimmed 448 bytes from the beginning, to get file to 1048576 bytes.
The drive was in 'not locked' and 'not frozen' state according to hdparm before applying. There was some sense error at the end of the flash.
Did the set password and secure erase steps.
After connecting the drive again, it was recognized normally. Many smart values were reset in the process, but firmware version is still reported as the original GXT3003Q.

Now I'm wondering if I should update other drives I have, which are working normally. This latest firmware comes seven years after the product was released!
 
  • Like
Reactions: fohdeesha

zac1

Well-Known Member
Oct 1, 2022
432
358
63
1048576 bytes doesn't work on the SM863, it popped an I/O error. I had to trim another 512 bytes (resulting in 1048064 bytes) for the fw flash to be successful.

The stated firmware version in smartctl still didn't update though, so I'm not sure if the fw flash is even successful. o_O
1048576 worked for me. Firmware string updated to GB57. However, Reallocated Sectors went from 0 to... 256! Currently running "Surface Test/Reinitialize disk surface" on one in HD Sentinel and `badblocks -wsv` on another in a different machine.

Any ideas? Some kind of overflow/software artifact? Recoverable maybe?

Edit: HD Sentinel finished Surface Test/reinitialization. No bad sectors found. No changes in reallocated sector count. badblocks looks like it will run all night.

Edit2: badblocks completed, 0 bad blocks found. I wonder if the alleged bad sectors are being mapped to reallocated sectors during one or both of these scans?
 
Last edited:

DarkServant

Member
Apr 5, 2022
53
55
18
1048576 worked for me. Firmware string updated to GB57. However, Reallocated Sectors went from 0 to... 256! Currently running "Surface Test/Reinitialize disk surface" on one in HD Sentinel and `badblocks -wsv` on another in a different machine.

Any ideas? Some kind of overflow/software artifact? Recoverable maybe?

Edit: HD Sentinel finished Surface Test/reinitialization. No bad sectors found. No changes in reallocated sector count. badblocks looks like it will run all night.

Edit2: badblocks completed, 0 bad blocks found. I wonder if the alleged bad sectors are being mapped to reallocated sectors during one or both of these scans?
I have no idea, but the exact number of 256 in an instant indicates that it can be a "false alarm" or a complete page/block had failed. There should be SMART values which indicate used and remaining spare blocks.
If the reallocated value increases steadily over time, get rid of the drive asap.
With those firmware updates it's always a risk which should be weighted out.

The tools are made for spinning disks and don't do anything good because they only see the logical sectors and not the physical pages, blocks and planes. One thing you can do is running a drive self-test (short/long), or you have a specific tool from the vendor for the SSD.
Even reading the SSD causes some wear (read-disturb which requires cell refresh at a certain threshold -we hope...).
 

Attachments

Jonis Demamann

New Member
Oct 4, 2017
11
2
3
39
I made the mistake of buying the SM863 with GXM1003Q firmware.
It is showing extremely low read speeds (10mb/s to 60mb/s at most).

Is there any firmware that solves this problem? Any solution for this?

Thanks again.
 

pimposh

hardware pimp
Nov 19, 2022
145
81
28
I don't think you can tie this issue to FW version. Got couple of SM863 with this FW and they're all good.
 

mach3.2

Active Member
Feb 7, 2022
143
97
28
I made the mistake of buying the SM863 with GXM1003Q firmware.
It is showing extremely low read speeds (10mb/s to 60mb/s at most).

Is there any firmware that solves this problem? Any solution for this?

Thanks again.
My understanding is once it's hosed, a FW upgrade won't save it. You can trim and flash the dell GB57 firmware (refer back to first page) and report back with your findings.

I don't think you can tie this issue to FW version. Got couple of SM863 with this FW and they're all good.
It's apparently a thing.
 
Last edited:

Jonis Demamann

New Member
Oct 4, 2017
11
2
3
39
1048576 worked for me. Firmware string updated to GB57. However, Reallocated Sectors went from 0 to... 256! Currently running "Surface Test/Reinitialize disk surface" on one in HD Sentinel and `badblocks -wsv` on another in a different machine.

Any ideas? Some kind of overflow/software artifact? Recoverable maybe?

Edit: HD Sentinel finished Surface Test/reinitialization. No bad sectors found. No changes in reallocated sector count. badblocks looks like it will run all night.

Edit2: badblocks completed, 0 bad blocks found. I wonder if the alleged bad sectors are being mapped to reallocated sectors during one or both of these scans?
I downloaded the GB57 firmware, I did the procedure to make it 1048576 bytes as demonstrated, but at the end of the procedure with hdparm I received an I/O error. I then removed 512 more bytes from the file, and this time hdparm executed without errors.
According to smartctl, there was no change in the firmware version or SMART data, however I noticed that the R/W speed was normalized.
 

zac1

Well-Known Member
Oct 1, 2022
432
358
63
I downloaded the GB57 firmware, I did the procedure to make it 1048576 bytes as demonstrated, but at the end of the procedure with hdparm I received an I/O error. I then removed 512 more bytes from the file, and this time hdparm executed without errors.
According to smartctl, there was no change in the firmware version or SMART data, however I noticed that the R/W speed was normalized.
What's your specific drive model? I also found that doing a secure erase fixed R/W, but I heard that is only temporary which makes sense given the root issue is the endurance management "feature" in the firmware.
 

Jonis Demamann

New Member
Oct 4, 2017
11
2
3
39
What's your specific drive model? I also found that doing a secure erase fixed R/W, but I heard that is only temporary which makes sense given the root issue is the endurance management "feature" in the firmware.
My driver model: MZ7KM1T9HAJM-0E005

But if the SSD accepted the new firmware (GB57 with endurance management 'bug' fixed), maybe its solved wile the drive has a good wear level indicator, right?

All my drivers have wear level indicator above 93, they are in good shape.
 

paradoXXX

New Member
Apr 21, 2023
2
1
3
HI!
I have some trouble.

I notice that the firmware version does not match the disk model version.
Model : SM883
P/N : MZ7KH1T9HAJR-00005.
But FW is GXT3003Q ( Although the label says it must be HXM7904Q, but don't)

GXT3003Q is used for PM863 models
Also, I looked inside the disk and saw there a chip S4LP052X01-8030 (is used for PM863 models)

For SM883 must be controller S4LR030.


i think maybe i have a fake samsung disk
 

mach3.2

Active Member
Feb 7, 2022
143
97
28
HI!
I have some trouble.

I notice that the firmware version does not match the disk model version.
Model : SM883
P/N : MZ7KH1T9HAJR-00005.
But FW is GXT3003Q ( Although the label says it must be HXM7904Q, but don't)

GXT3003Q is used for PM863 models
Also, I looked inside the disk and saw there a chip S4LP052X01-8030 (is used for PM863 models)

For SM883 must be controller S4LR030.


i think maybe i have a fake samsung disk
Care to post the model number from the SMART read out?

But sounds like you have a SM863 PCB in an SM883 case.