PM863 FW File

jei

Member
Aug 8, 2021
35
28
18
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

Active Member
Oct 1, 2022
213
163
43
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

New Member
Apr 5, 2022
17
15
3
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
7
2
3
38
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.
 

mach3.2

Member
Feb 7, 2022
45
28
18
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: