I tried Toshiba couple months ago, they asked for proof of purchase. I expect Kioxia will ask the same, but I should give it a shot.
Toshiba PX05SRB SSD Failures
- Thread starter nmap
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
you can always fabricate it...
Just print amazon or some other site purchase recipient with dates that are believable - not too old but not to young either. *Old enough that the company would not keep the order id; but enough that it didn't sit on shelf for 2-4 years before being sold. *ensure its been sold around 6m-1 year after manufactured date. (just make sure they were selling them back then)
Just print amazon or some other site purchase recipient with dates that are believable - not too old but not to young either. *Old enough that the company would not keep the order id; but enough that it didn't sit on shelf for 2-4 years before being sold. *ensure its been sold around 6m-1 year after manufactured date. (just make sure they were selling them back then)
I have 20 pcs PX05SRB384 model by IBM\Lenovo with 6402 firmware. Could anybody help with 6406 firmware update file?
Very sad to see that many paperweights. Let's rush firmware without testing it, what a great idea and sureley nothing bad will happen. Companies never learn. At this point go with hdds lol(might be a stupid sugestion).
Hi, it would be nice to create a repository for Toshiba/Kioxia SSD's. They are too on the list for do not buy because of that, but they have a solid quality hardware.
PS: An FL6 with 3,2TB sounds really nice.
PS: An FL6 with 3,2TB sounds really nice.
Why not add to the
UploadYourFWStuff that was started on GMX by a Member (initially focused on Samsung, but there is at least ONE Kioxia Firmware for a CM6) ?Heya guys,
Recently I've got my hands on PX05SRB series from Fujitsu, specifically PX05SRQ192. It also has the firmware bug (6807). I was unable to flash Fujitsu's own firmware using sg_write_buffer, the latest firmware (680A) got sense key error ( Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode ). I did some hex edit on the firmware header after comparing it to a dell PX05SVB firmware, and I've successfully flashed it to 680A.
I think it's possible to flash other OEM firmware to the same disk series, unfortunately I don't have another OEM disk to try it out.
At least I saved my own disk from future paperweight.
Recently I've got my hands on PX05SRB series from Fujitsu, specifically PX05SRQ192. It also has the firmware bug (6807). I was unable to flash Fujitsu's own firmware using sg_write_buffer, the latest firmware (680A) got sense key error ( Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode ). I did some hex edit on the firmware header after comparing it to a dell PX05SVB firmware, and I've successfully flashed it to 680A.
I think it's possible to flash other OEM firmware to the same disk series, unfortunately I don't have another OEM disk to try it out.
At least I saved my own disk from future paperweight.
I've got about 24 paperweights (PX05SRB192), if you could tell me what you did or help me out in some way I'd be willing to give it a a shot! Or do you need an OEM disk to PULL firmware from?
Not sure if I can help you but do you have the firmware you want to update to and your current firmware? What’s your disk brand, is it the original toshiba or other rebranded stuff?
These are the ones I have, I know it is 6402 firmware but other than that, nothing. Sense key error when i try to use them.
Attachments
That is wild. I have some old PX02 paperweights right now.
What... what did you do to hex edit it? Is there a followable guide somewhere I could try to follow on another drive?
Tried to ask Kioxia about firmware update for a few PX02 I have with just 10k hours. Their reply was that these were old and that I should just get new ones 
Nice Move to make sure that People buy ... OTHER Brands.Tried to ask Kioxia about firmware update for a few PX02 I have with just 10k hours. Their reply was that these were old and that I should just get new ones
I'd like to ask if there was any malfunction with your SSDs after this time?Tried to ask Kioxia about firmware update for a few PX02 I have with just 10k hours. Their reply was that these were old and that I should just get new ones
I think it has the 70k hours death bug. So they will still last a few more years. But they have 10 DWPD, it will be impossible to kill them within that timeframe
Sounds like "Planned Obsolescence" to me
. Might be a "Feature" and not so much of a BUG.
just had a PX02 die in my music studio PC, showing 0 bytes and sense key errors. What a pain in the ass. I have a backup of this system but it's ~ 2 years old because I'm lazy and I didn't consider this pc "important" like the rest of my gear. I've got $100 for anyone who can get me firmware for this to hopefully revive it in the next ~48 hours, I can't find shit on the internet, just a ton of people saying toshiba / Kioxia told them to **** off when they asked. From what I've read this is even more of a pain in the ass if you have the SMQ encryption supporting model, which I do
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-15-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: PX02SMQ160
Revision: MS02
Compliance: SPC-4
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x500003964c880838
Serial number: 5520A0CST2AA
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Thu Oct 23 04:50:05 2025 UTC
device Test Unit Ready [medium or hardware error (serious)]
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
[ 2.288857] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 2.288971] sd 0:0:0:0: [sda] ASC=0x4c <<vendor>>ASCQ=0xa8
[ 2.289645] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-15-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: PX02SMQ160
Revision: MS02
Compliance: SPC-4
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x500003964c880838
Serial number: 5520A0CST2AA
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Thu Oct 23 04:50:05 2025 UTC
device Test Unit Ready [medium or hardware error (serious)]
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
[ 2.288857] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
[ 2.288971] sd 0:0:0:0: [sda] ASC=0x4c <<vendor>>ASCQ=0xa8
[ 2.289645] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Why would you post this and not post what location in the firmware needs modified? I love unnecessarily duplicating people's work, weeeeeeeeee
Also, did flashing the new firmware make your previous data accessible again? Or was the drive wiped? I don't wanna spend hours reverse engineering the firmware headers on this thing if flashing it will only get me a newly formatted empty drive. I don't have access to the existing firmware it's running so I have *no clue* what header locations to even begin diffing
EDIT: nevermind, you flashed yours before it was bricked, not after
Last edited: