I grabbed them from Dell, and cut out the stuff to 1MiB with wxHexEditor.What is the source for these?
Thanks! Where's it from?Stock for PM863a attached. Tested, flash and work okay.
Works with SM863a too?Stock for PM863a attached. Tested, flash and work okay.
no very different drives/firmwareWorks with SM863a too?
I have bought 8x SM863a and 8x PM863a and I want to update it all before send to production.
Thanks!
Latest firmware for the sm863a series seems to be GXM5304Q.Works with SM863a too?
I have bought 8x SM863a and 8x PM863a and I want to update it all before send to production.
Thanks!
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.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.
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.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?
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 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.
It's apparently a thing.I don't think you can tie this issue to FW version. Got couple of SM863 with this FW and they're all good.
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.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?
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.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.
My driver model: MZ7KM1T9HAJM-0E005What'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.
Care to post the model number from the SMART read out?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