When i was refering to bridge chips i was refering to Jmicron JMS578 Bridge Chip, sorry i was too tired to remember the model. I know that others generaly fail at that and shouldn't be attemptesld at all to not destroy the ssd. I saw people use that one to flash firmware on ssds.
Firmware package for Samsung SM883/MZ7KH3T8HALS
- Thread starter oh2ftu
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
From Windows it's normal that it opens a Windows and the closes immediately.
You need to first open a Command Prompt (or possibly Powershell ?) and THEN
cd C:\my\path\to\the\program and <program>.exe --option1 --option2 ....As an alternative (which I tried before I realized that my Samsung PM983 M.2 NVMe Drive required the 2.1 Version, while the 3.0 Version caused a Segmentation Fault under Debian 12 AMD64), you might do what I did, assuming you can pass the SATA Controller through (or install a temporary LSI HBA which you might need ANYWAYS):
a. Get a Debian / Ubuntu / Fedora ISO
b. Create a LiveUSB. 32GB minimum, 64GB recommended
c. Install
cockpit and cockpit-machines (for Fedora it is probably already installed)d. For Debian and Ubuntu you might need to add
systemd on the Lines of /etc/nsswitch.conf for passwd, group, shadow, see Failed to resolve group cockpit-wsinstance-socket: No such process · Issue #21986 · cockpit-project/cockpit for the Detailse. Suggest you also install the
virtiofs Driver / virtiofsd Daemon, so you can setup a Shared Folder between Host and Gueste. Probably easiest is to restart/reboot the System
f. Download Hiren's Boot CD PE from Hiren's BootCD PE:
mkdir /var/lib/libvirt/isos; cd /var/lib/libvirt/isos; wget <download link> -O hirens-boot-cd-pe.isoe. Login into Cockpit at
https://<ip>:9090f. Create a new VM, Set OS to Windows 11, select ISO from previous Path, Probably no Hard Drive Storage required
g. Verify that Intel VT-x & VT-d / AMD IOMMU / SVM are enabled in the BIOS and also in the OS (typically this is configured in
/etc/default/grub or /etc/default/grub.d/<whatever>.cfg)g. Select your SAS/SATA Controller and pass it through to the VM. This Part requires that your USB and SATA Controllers are in different IOMMU Groups which is usually NOT the case. You could try to split the IOMMU Groups (NOT reccomended) or you can install a PCIe LSI HBA in a PCIe Slot
h. Boot the VM. You will be greeted in a Windows Environment
i. (I didn't get to this Part yet so not sure how it works from Windows PE) Setup the VirtioFS Share between Host and Guest so you can share the Firmware and DC Toolkit that Way
j. Run the DC Toolkit as you are running basically
I did NOT flash from Windows PE since by the Time I realized I needed v2.1 (v3.0 would cause a Segmentation Fault in Windows), I was in the Middle of a Upgrade (trying to install latest QEMU & Cockpit from Debian Backports) so I did NOT want to risk it having the PCIe Device passed through the VM at that critical Point.
But, if you want, you can also do the same with another Version of Linux (pretty much same Procedure).
For VirtioFS in that Case assuming from your Host you mount Source Path
/home/<user>/Shared/<myvm> to Target Path /Shared, then from the Guest it's as simple as putting this in /etc/fstab:
Code:
# Shared Files via VirtioFS Driver
/Shared /home/<user>/Shared/ virtiofs rw,auto,nofail,x-systemd.automount 0 0
Last edited:
Hello everyone, I have 2 PM863 SSD and was facing the ERRORMOD issue. I used secure erase to take them back and want to update their firmware. But I found my SSDs are Amazon OEM:
Has anyone found the firmware of PM863 Amazon OEM, or succesfully flashed other firmware on it?
Thanks!
Code:
================================================================================================
Samsung DC Toolkit Version 2.1.L.Q.0
Copyright (C) 2017 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------------------------------------------
| Disk | Path | Model | Serial | Firmware | Optionrom | Capacity | Drive | Total Bytes | NVMe Driver |
| Number | | | Number | | Version | | Health | Written | |
----------------------------------------------------------------------------------------------------------------------------------------
| 3 | /dev/sdd | SAMSUNG MZ7LM1T9HCJM-000AZ | S1ZCNYAFB00888 | GXT01W3Q | N/A | 1788 GB | GOOD | 0.00 TB | N/A |Thanks!
Tried it again for three hours and it started giving me invalid fw image no matter what I tried, it is cancer. Going to give it to someone to do it.
That's a bad Combination, you should really change that PSU ...
USB <--> SATA Adapters are usually NOT a great Idea and I personally would NOT do it.
I'm not saying they will not work, but it's a huge Risk IMHO to use them especially for Firmware Flashing. It would actually be better if it does NOT work at all, that Way you will NOT be tempted to attempt a Flashing from such a IMHO Risky Procedure.
If it does not work with a truncated Dell FW and a forced flash via hdparm, i have no idea, probably with some debugging hardware connected directly to the PCB (JTAG Header), but this is something i am not able to help.
Can be that a newer Amazon FW doesn't even exist, and they simply changed the drives.
Many many years ago, some of the "IT-Support" had an 24V or 48V PSU with "Molex" connectors fitted, and if a drive worked only partially and it had warranty... *frrrzzzzzt* Warranty Case: No Function at all.
Can be that a newer Amazon FW doesn't even exist, and they simply changed the drives.
Many many years ago, some of the "IT-Support" had an 24V or 48V PSU with "Molex" connectors fitted, and if a drive worked only partially and it had warranty... *frrrzzzzzt* Warranty Case: No Function at all.
I have been nicknamed that and I'm an IT guy that tries helping people with a wide range of problems. Decided to go with that because thinking of a new username was taking too long.
I'm in college and I do IT support as my second job. It gives me satisfaction to see smiles on my client's faces, try my best to go far beyond. Still learning new things daily to improve my knowledge and capabilities but have to give it to the old guard of technicians for jobs that are too complicated or simply alien to me. Short time off doesn't allow me to focus on very complex/monumental jobs and I don't do soldering because of health problems.
I think there is no strict definition where IT-Support begins and where it ends, there are many thousands with way less skill, who call themselves IT-Supporters.
If it helps others and yourself, you are on the right path. Knowing your limits is important, taking too much on you, can easily lead to frustration on both sides. I still got my problems with "never touch a running system"....
PS: there should be a FW version GXT03W3Q, but i have no idea where to get this file. ( picture from serversupply )
This dive is taking the p!$$ out of my elder tech. It's causing him a headache, he thought I was pranking him. It's been in the shop for a while now and hopefully he will be done by the end of the month. Wish me luck.
P.S. That is amazing advice. We always think we can improve a system without breaking it in some way or completely taking it offline. Only smart people always think of how they could improve something even though it could be a negligible improvement. Keep it up!
P.S. 2. Would you buy an ssd that is a good deal or not, to only get that specific mythical firmware that is once in a blue moon?
I don't think you can download a firmware from a drive, and then put it onto another one... the digital signature will probably not be included and the drive will reject it, but i never tried it.
If this works, the hunt for firmwares would be much easier...
Since we are here, I decided to try getting a purestorage array to work, however mine came without drives, So in other words i am in the oppisite boat, I might have to put the original firmware back on.
I have heard conflicting information, some people saying that it will work with generic drives, some saying that I do need the purestorage custom ones..
It seems that the original drives were toshiba, and it uses some weird lsi ssd to sas converter
My array is X50R2
I have checked both repositories and I dod not see purestorage specific formwares there (I did notice netapp)
Is there a place I could start digging?
Thank you
I have heard conflicting information, some people saying that it will work with generic drives, some saying that I do need the purestorage custom ones..
It seems that the original drives were toshiba, and it uses some weird lsi ssd to sas converter
My array is X50R2
I have checked both repositories and I dod not see purestorage specific formwares there (I did notice netapp)
Is there a place I could start digging?
Thank you
@DarkServant I just got 2 x 960GB Samsung PM883's from reddit and they have these info:
Device Model: Samsung MZ7LH960HAJR-00005
Firmware Version: HXT7B04Q
In your repo, I see that the HXT7B04Q_NF.bin is the latest firmware there. Does this mean I already have the latest and that I have a Samsung SSD (not an OEM-rebadged one)?
Device Model: Samsung MZ7LH960HAJR-00005
Firmware Version: HXT7B04Q
In your repo, I see that the HXT7B04Q_NF.bin is the latest firmware there. Does this mean I already have the latest and that I have a Samsung SSD (not an OEM-rebadged one)?
yep looks like latest firmware is already on it
So the HXT7B04Q is the latest? The drives I have here have HXT7904Q and 2021.20 printed on them, so just one version "behind"?
Also, is it normal that the Samsung DC toolkit cannot see a SSD connected via one of those USB adapters?
Also, is it normal that the Samsung DC toolkit cannot see a SSD connected via one of those USB adapters?
Last edited:
Yes, avoid completely. And IF drive is seen by flash tool, chances are much higher of hard bricked drive.
Doesn't work that way. If you can pass security checks aka "vendor commands" you can sometimes download only parts of the mostly over 100 snippets/modules (yes, a 2MB firmware looks innocent, but it's complex af) but you won't get the drive to spit out a binary ready to flash another disk and also it is intended from the vendors.
This is kind of offtopic, but perhaps someone knows.
I tried plugging the PM883 into my PC (directly) and it's not showing up in disk management at all. It seems like it's not even being powered on, judging by a power meter I put in the outlet. It's connected to normal SATA port on the motherboard. I don't get it.
I tried plugging the PM883 into my PC (directly) and it's not showing up in disk management at all. It seems like it's not even being powered on, judging by a power meter I put in the outlet. It's connected to normal SATA port on the motherboard. I don't get it.
New Firmware for the SSD's pm893 (JXTC904Q) and pm897 (JXTE704Q) available.
Samsung Datacenter/Enterprise-SSD Firmware Repository
Samsung Datacenter/Enterprise-SSD Firmware Repository
One option is to look with linux at the drive, another is to power it on without data cable and wait about an hour or a little more (aka powercycling), last, if the drive is an 7.68TB model with low usage, you have to go to someone with very good soldering equipment and a deep knowledge at electronics plus a lot of experience... can be a dead PMIC or defective controller (which is the same MJX Maru "S4LR030" as in 860 consumer drives) or it's only a blown fuse. But prepare for the worst... you can open it with a Pentalobe "5PL" screwdriver, if it smells burnt or has some black spots on the PCBA = Bad News
I've been having random errors roughly once a week on eight different SM883's. This thread might have given me the solution!
According to the stickers the firmware is supposedly HXM7304Q but when flashing them they were actually being reported as having HXM7104Q.
Not sure why the Ebay seller would've gone a few versions back with them. Maybe accidentally used the wrong .bin file?
Just flashed them from HXM7104Q to HXM7A04Q. No problems so far. Hopefully this'll solve my random error issues.
According to the stickers the firmware is supposedly HXM7304Q but when flashing them they were actually being reported as having HXM7104Q.
Not sure why the Ebay seller would've gone a few versions back with them. Maybe accidentally used the wrong .bin file?
Just flashed them from HXM7104Q to HXM7A04Q. No problems so far. Hopefully this'll solve my random error issues.
That would explain a lot, the first two to three versions are not quite free from bugs. Just do a long drive self-test on each drive to be sure.I've been having random errors roughly once a week on eight different SM883's. This thread might have given me the solution!
According to the stickers the firmware is supposedly HXM7304Q but when flashing them they were actually being reported as having HXM7104Q.
Not sure why the Ebay seller would've gone a few versions back with them. Maybe accidentally used the wrong .bin file?
Just flashed them from HXM7104Q to HXM7A04Q. No problems so far. Hopefully this'll solve my random error issues.
The other reason (but i don't know if that would work) could be the trigger of a SMART reset, that would be the worst.
Still one of the best SATA SSD's ever the sm883, and the last with really durable MLC V-NAND -> the successor pm897 (3,84TB) needs 6TB of raw NAND to reach the same TBW.
OT: I do not think the so called AI-bubble will go away... there are bad times ahead with some "elements" who have nearly unlimited funds and have dried the lake of "affordable" new enterprise hardware.
A new NVMe based all-flash-NAS (with ECC-DRAM and a pair of enterprise 12,8TB drives) is off the table indefinitely.
It looks like even the gaming industry adopts to AI, and i think the R&D of real GPU's has halted quite some time ago, and the AI-logic will only be repurposed in the future. But the bright days of gaming are over anyway.
Or it's only me who is slowly fading into dust...