Guide: Reviving Toshiba / Kioxia PX02 & PX05 drives

[EasyRhino]

just trying things....

ensure the drives don't have 3.3v power.

if there is a PSID on the sticker, run a sedutil-cli psid revert.

try sg_format without specifying block size once (format "as is") then try changing block size.

 

[Squigley]

Hello,

I have multiple PX05SRB048Y SSDs, all are showing up as 0 bytes.

I suspect it's the 70k bug.

I tried loading both the PX05 and PX05-SED bins to them using write buffer, but they both get rejected. Same result as other people have posted earlier in the thread, ie sense codes.

I also tried the 1.bin and 2.bin files from the test.zip, these too were rejected, however interestingly the sense code output was slightly different, returning something like "invalid signature" (I don't recall exactly, but I found the source code of the write buffer file under sg utils and the sense code it corresponded to).

I also found that Dell has released an update for this model of drive, firmware version AS10..

Toshiba AS10 for model number(s) PX05SMB320Y, PX05SMB160Y, PX05SMB080Y, PX05SMB040Y, PX05SVB384Y, PX05SVB192Y, PX05SVB096Y, PX05SVB048Y, PX05SRB384Y, PX05SRB192Y, PX05SRB096Y and PX05SRB048Y. | Driver Details | Dell Canada

however I also found a thread regarding this, which said it doesn't fix the 70k bug, and I would agree that it doesn't, since I was able to use Dell's update BIN to flash a couple of them, and they still showed 0 bytes.

https://forums.servethehome.com/index.php?threads/toshiba-px05srb-ssd-failures.43665/post-449361

A couple of fun things about that.. when I initially tried using the Dell update tool on the first drive, it immediately failed out, this was after having tried to flash the provided PX05.bin and SED.bin (and maybe 1.bin and 2.bin). I presume those attempted flashes had put the drive in some funny state. After a power cycle, the Dell tool.. sort of worked..

It ran, ran inventory, found the drive running firmware AS0E (I think it was), said it would upgrade it, and for about 4 minutes it printed dots across the screen, before eventually saying "no update was performed"..

However, when I ran it again, it now shows that the drive is running AS10, so it did upgrade. Power cycling the drive showed no difference, still says it's 0 bytes.

I dug through the thousands of lines of the log file that the Dell update util created, and it showed it sending all the chunks of the update to the drive, and then the drive would return the sense error code related to no media (the 70k bug), but it obviously did actually upgrade it, because it shows the new FW version from the drive when you run the update again..

Anyway, that's the back story. (Unfortunately I lost the terminal output and the logs of this, because I was running from a live environment).

I tried to see if I could use the Dell update utility to flash the PX05 you provided, digging through their stuff I found it's using some binary "sputil", so I don't know what it's doing. I also pulled their "payload" of the fwh file, and using a hex editor shows it has some sort of Dell header on the top, listing all the applicable models of drive, before the Toshiba header:

```
00000000 20 20 20 20 20 20 20 20 01 41 53 31 30 41 53 30 | .AS10AS0|
00000010 31 78 02 20 20 20 20 20 20 20 20 20 20 20 20 20 |1x. |
00000020 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000030 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 0c | .|
00000040 20 20 31 30 35 36 32 38 20 20 20 20 20 20 20 20 | 105628 |
00000050 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000060 20 20 20 20 20 50 58 30 35 53 4d 42 33 32 30 59 | PX05SMB320Y|
00000070 20 20 31 30 35 36 32 37 20 20 20 20 20 20 20 20 | 105627 |
00000080 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000090 20 20 20 20 20 50 58 30 35 53 4d 42 31 36 30 59 | PX05SMB160Y|
000000a0 20 20 31 30 35 36 32 36 20 20 20 20 20 20 20 20 | 105626 |
000000b0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
000000c0 20 20 20 20 20 50 58 30 35 53 4d 42 30 38 30 59 | PX05SMB080Y|
000000d0 20 20 31 30 35 36 32 35 20 20 20 20 20 20 20 20 | 105625 |
000000e0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
000000f0 20 20 20 20 20 50 58 30 35 53 4d 42 30 34 30 59 | PX05SMB040Y|
00000100 20 20 31 30 35 36 32 34 20 20 20 20 20 20 20 20 | 105624 |
00000110 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000120 20 20 20 20 20 50 58 30 35 53 56 42 33 38 34 59 | PX05SVB384Y|
00000130 20 20 31 30 35 36 32 33 20 20 20 20 20 20 20 20 | 105623 |
00000140 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000150 20 20 20 20 20 50 58 30 35 53 56 42 31 39 32 59 | PX05SVB192Y|
00000160 20 20 31 30 35 36 32 32 20 20 20 20 20 20 20 20 | 105622 |
00000170 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000180 20 20 20 20 20 50 58 30 35 53 56 42 30 39 36 59 | PX05SVB096Y|
00000190 20 20 31 30 35 37 33 35 20 20 20 20 20 20 20 20 | 105735 |
000001a0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
000001b0 20 20 20 20 20 50 58 30 35 53 56 42 30 34 38 59 | PX05SVB048Y|
000001c0 20 20 31 30 35 36 32 31 20 20 20 20 20 20 20 20 | 105621 |
000001d0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
000001e0 20 20 20 20 20 50 58 30 35 53 52 42 33 38 34 59 | PX05SRB384Y|
000001f0 20 20 31 30 35 36 32 30 20 20 20 20 20 20 20 20 | 105620 |
00000200 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000210 20 20 20 20 20 50 58 30 35 53 52 42 31 39 32 59 | PX05SRB192Y|
00000220 20 20 31 30 35 36 31 39 20 20 20 20 20 20 20 20 | 105619 |
00000230 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000240 20 20 20 20 20 50 58 30 35 53 52 42 30 39 36 59 | PX05SRB096Y|
00000250 20 20 31 30 35 37 33 34 20 20 20 20 20 20 20 20 | 105734 |
00000260 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
00000270 20 20 20 20 20 50 58 30 35 53 52 42 30 34 38 59 | PX05SRB048Y|
00000280 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400 50 4d 30 34 44 48 57 46 0d 0a 0d 0a 57 65 64 65 |PM04DHWF....Wede|
00000410 6e 73 64 61 79 2c 20 41 70 72 69 6c 20 30 33 2c |nsday, April 03,|
00000420 20 32 30 31 39 20 31 31 3a 32 34 3a 35 32 20 62 | 2019 11:24:52 b|
00000430 79 74 73 62 67 6c 65 0d 0a 43 6f 70 79 72 69 67 |ytsbgle..Copyrig|
00000440 68 74 20 28 43 29 20 54 4f 53 48 49 42 41 20 43 |ht (C) TOSHIBA C|
00000450 4f 52 50 4f 52 41 54 49 4f 4e 2e 0d 0a 41 6c 6c |ORPORATION...All|
00000460 20 72 69 67 68 74 73 20 72 65 73 65 72 76 65 64 | rights reserved|
00000470 2e 0d 0a 50 34 4d 3a 35 33 3a 31 30 3a 30 31 3a |...P4M:53:10:01:|
00000480 30 30 20 20 20 20 20 20 20 20 20 20 20 20 20 20 |00 |
00000490 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
*
```

AS10 is from 2019 (as you can see above), and already been established to not fix the bug. I found a page on Dell's site in regards to PX02/PX03 drives, with a fixed firmware, from 2023, but I can't find the same page for PX05 drives.

PowerEdge: PM2, PM2+, PM2R SSDs drives locking after 70000 Power On Hours | Dell UK

```
Fixed in firmware versions
PM2, Drive Firmware A3B4
PM2+, Drive Firmware A4B4
PM2R, Drive Firmware A5B4
Firmware update Web posted 24th August 2023.
```
Your PX05.bin:
```
00000000 50 4d 30 34 44 48 57 46 0d 0a 0d 0a 54 75 65 73 |PM04DHWF....Tues|
00000010 64 61 79 2c 20 53 65 70 74 65 6d 62 65 72 20 32 |day, September 2|
00000020 38 2c 20 32 30 32 31 20 31 39 3a 33 30 3a 30 36 |8, 2021 19:30:06|
00000030 20 62 79 74 73 62 67 6c 65 0d 0a 43 6f 70 79 72 | bytsbgle..Copyr|
00000040 69 67 68 74 20 28 43 29 20 54 4f 53 48 49 42 41 |ight (C) TOSHIBA|
00000050 20 43 4f 52 50 4f 52 41 54 49 4f 4e 2e 0d 0a 41 | CORPORATION...A|
00000060 6c 6c 20 72 69 67 68 74 73 20 72 65 73 65 72 76 |ll rights reserv|
00000070 65 64 2e 0d 0a 50 34 4d 3a 37 37 3a 30 36 3a 30 |ed...P4M:77:06:0|
00000080 31 3a 30 30 20 20 20 20 20 20 20 20 20 20 20 20 |1:00 |
00000090 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
```
and the SED:
```
00000000 50 4d 30 34 44 48 57 46 0d 0a 0d 0a 54 75 65 73 |PM04DHWF....Tues|
00000010 64 61 79 2c 20 53 65 70 74 65 6d 62 65 72 20 32 |day, September 2|
00000020 38 2c 20 32 30 32 31 20 31 39 3a 33 34 3a 32 31 |8, 2021 19:34:21|
00000030 20 62 79 74 73 62 67 6c 65 0d 0a 43 6f 70 79 72 | bytsbgle..Copyr|
00000040 69 67 68 74 20 28 43 29 20 54 4f 53 48 49 42 41 |ight (C) TOSHIBA|
00000050 20 43 4f 52 50 4f 52 41 54 49 4f 4e 2e 0d 0a 41 | CORPORATION...A|
00000060 6c 6c 20 72 69 67 68 74 73 20 72 65 73 65 72 76 |ll rights reserv|
00000070 65 64 2e 0d 0a 50 34 4d 3a 38 37 3a 30 36 3a 30 |ed...P4M:87:06:0|
00000080 31 3a 30 30 20 20 20 20 20 20 20 20 20 20 20 20 |1:00 |
00000090 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
``

I figured that if I tried sticking the Dell header of the model numbers on the top of PX05.bin you provided and using Dell's util to flash it (by replacing the file before accepting their license thing, which it displays after it creates the temp extracted directory, and I could swap out the payload) it may flash it?

I guess if that doesn't work, the drive would accept all the chunks of the firmware, and then just reject it anyway and not flash..

Anyway, I guess at this point I'm looking for some advice regarding the Y variant of the drives, since they don't accept the SED (or non SED) firmware, and they don't have a PSID on the label (and they were used in an R620 with the standard PERC).

Cheers,
Squigley

 

[archiethemonger]

@fohdeesha would you happen to have FW for the Cisco PX05 (not Y) variants on-hand? As you mentioned in your edit, the NetApp firmware won't flash on other brands.

---

@Squigley I went through many of the same steps for my Dell PX05SMB160Y variant. AS10 doesn't fix it and the OP's firmware is NetApp which won't pass flash validation regardless of how I edited the binary. I would be hesitant to force it since none of the FW is for the Y variants. Dell support confirmed they do not have this firmware update on-hand. At first they were very confused because the product model no longer exists in their historical product database, which also means a resolution isn't possible without a service contract. Toshiba and Kioxia US claimed the firmware is in the hands of Kioxia EU. Then ultimately Kioxia EU said were unwilling to provide any FW for this model, claiming that binaries are only authorized to be given directly to Dell.

Right now it seems like a waiting game to see if Dell will grab the update from Kioxia EU and upload it to their support portal, unless someone is willing to risk bricking their drive by wiping the drive identity and forcing NetApp firmware on it.

On a positive note, last year Dell released a firmware update for the regular (not Y) variants of the PX02 and PX03. I would assume some enterprise customer threw some money at making that release happen. So there's always hope PX05-Y might eventually get an update.

 

[fohdeesha]

@fohdeesha would you happen to have FW for the Cisco PX05 (not Y) variants on-hand? As you mentioned in your edit, the NetApp firmware won't flash on other brands.

---

@Squigley I went through many of the same steps for my Dell PX05SMB160Y variant. AS10 doesn't fix it and the OP's firmware is NetApp which won't pass flash validation regardless of how I edited the binary. I would be hesitant to force it since none of the FW is for the Y variants. Dell support confirmed they do not have this firmware update on-hand. At first they were very confused because the product model no longer exists in their historical product database, which also means a resolution isn't possible without a service contract. Toshiba and Kioxia US claimed the firmware is in the hands of Kioxia EU. Then ultimately Kioxia EU said were unwilling to provide any FW for this model, claiming that binaries are only authorized to be given directly to Dell.

Right now it seems like a waiting game to see if Dell will grab the update from Kioxia EU and upload it to their support portal, unless someone is willing to risk bricking their drive by wiping the drive identity and forcing NetApp firmware on it.

On a positive note, last year Dell released a firmware update for the regular (not Y) variants of the PX02 and PX03. I would assume some enterprise customer threw some money at making that release happen. So there's always hope PX05-Y might eventually get an update.

try this, it's for cisco's PX05SVB160 though. if it doesn't work, I can probably find the person who sent me it who can get the others

 

[archiethemonger]

Thanks a million, you coincidentally had the firmware for my exact model (Cisco PX05SVB160)! The drive wouldn't ingest the full binary without chunking, so I had to write a small script (attached). That might be the reason some of the earlier replies couldn't flash anything.

My Cisco PX05 has not locked up yet, so I can't confirm/deny if FW version 0104 resolves that issue. Prior to the update, my firmware was 0101. It doesn't appear to report power on hours over SMART. So I have no idea when it will actually hit 70k hours. EDIT: Looking at the SMART self-test log revealed my total power-on hours was ~54,000.

My Dell PX05SMB160Y are still bricks for the foreseeable future.

 

[fohdeesha]

Thanks a million, you coincidentally had the firmware for my exact model (Cisco PX05SVB160)! The drive wouldn't ingest the full binary without chunking, so I had to write a small script (attached). That might be a reason some of the earlier replies couldn't flash anything.

For the readers out there - my Cisco PX05 has not locked up yet, so I can't confirm/deny if FW version 0104 resolves that issue. My OEM firmware was 0101, and the Cisco FW doesn't appear to report power on hours over SMART. So I have no idea when it will actually hit 70k hours.

My Dell PX05SMB160Y are still bricks for the foreseeable future.

0104 definitely solves the issue

 

[archiethemonger]

For future onlookers - If Dell ever releases a FW fix then the attached script can be used to trim and flash a Dell *.fwh file using sg3_utils. The fwh file can be obtained by running the Windows Dell flash utility, clicking "extract", and going into the "payload" folder in the extracted directory. It works to flash AS10, but as mentioned above AS10 does not fix the drive lock-up.

 

[caustic]

I've some PX02SSU040 SSDs here. Is there a new firmware then MS02 available.
Thank you

 

[MKO]

I've got a Dell PX05SRB384Y,
The drives was reported as 0 bytes in two Gen10 HPE servers, now I added it into a proxmox host with LSI HBA and it is detected most of the times but sometimes it reports as 0 bytes.
Interacting with the drive through smartctl causes the system to hang for a short while sometimes I get smart output other times the drive times out or goes offline.

The drive is running firmware AS10 and is going offline during a short smart self-test

Accumulated power on time, hours:minutes 41831:42 (not 70K)
Percentage used endurance indicator: 19%
Manufactured in week 32 of year 2018
Elements in grown defect list: 0

Error counter log:
ECC delayed rereads/rewrites: 758
Non-medium error count: 6786
Uncorrected errors 0

I think this drive is broken or are there other things I should try?

 

[fohdeesha]

I've some PX02SSU040 SSDs here. Is there a new firmware then MS02 available.
Thank you

yes, MS04 which is the first firmware I linked in this post

 

[mr44er]

@fohdeesha
Regarding vendor-specific firmware locks, are you familiar with my threads on that other forum?

The HDD Oracle. • View topic - HUS724030ALS640 SAS Dell DL vs Generic GN

https://hddoracle.com/viewtopic.php?f=59&t=3280

 

[camelshoko]

Thanks very much! I need it.

 

[doogles]

Firstly, thank you to OP, this saved my bacon on a NetApp EF560 populated with the PX02SMB160 drives. I simply pulled them and plugged them up to a JBOD enclosure hooked up to an LSI9300-16e and was able to flash the PX02.bin without issue. They went from MS02 to MS03.

From reading this thread I understand that one can't flash cross-vendor (ie, I can't take a Dell PX02SMB160 and flash it with the NetApp MS03 firmware). Is it possible to source non-vendor specific PX02SMB160s (I see some folk using the term "Toshiba generic") and flash the NetApp MS03 firmware on them? I'm trying to source some more of these drives for the NetApp, but there's very few NetApp-branded drives available in the second-hand market -- looking for alternative options.

Thanks.

 

[LumpyRareHawk]

I got a bunch of used PX05SRB192Y and stumbled on this thread while looking up what was the `LU is resource provisioned, LBPRZ=1` in the smartctl output.

The firmware on mine is AU0F and they have 66000 hours, so they may have less than six month before they die.

=== START OF INFORMATION SECTION ===
Vendor:               TOSHIBA
Product:              PX05SRB192Y
Revision:             AU0F
Compliance:           SPC-4
User Capacity:        1,920,383,410,176 bytes [1.92 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Thu Mar 12 16:21:58 2026 EDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

Accumulated power on time, hours:minutes 66005:11
Manufactured in week 46 of year 2017

@Squigley @archiethemonger what was the original firmware version on your Y drives and how are they labelled?

Mine are labelled "Dell Enterprise Plus"
Model: PX05SRB192Y
PN: SDFAM81DUB01
DP/N: 08V7C5

I'm not sure where the AS10 firmware fit in the timeline.

Dell AS10 firmware release page say it's from 24 Oct 2019.

But Dell SCOS Drive firmware release table from Q1 2019 say they went from AU09 to AU0B, and then in Q1 2020 they went from that AU0B to AU0F, which is the one I have. Maybe those firmware version are specific to the drives that were in the SCv3000 series storage array?

The SCv3020 support page doesn't have any firmware release for 2021-2022. It has one for Q1 2023 but nothing for the SSD in it

The PX05.bin file of this thread is from September 28 2021, so maybe AU0F from 2020 is fixed?
Dell priority on that firmware was "Urgent".

 

[archiethemonger]

My drive's firmware was previously an older AS* number. I believe it was either AS03 or AS05. They are labeled "Dell", not "Dell Enterprise Plus".

In theory, Dell's firmware will reject any incompatible binaries. So I'm not opposed to trying to flash AU* firmware on it.

 

[LumpyRareHawk]

I didn't find any download link for the AU0F firmware. From what I could find, the firmware for Compellent disks are released through the Compellent unit, so not sure we can find it. Unless there's a way to extract it from one of my disk?

 

[fohdeesha]

I didn't find any download link for the AU0F firmware. From what I could find, the firmware for Compellent disks are released through the Compellent unit, so not sure we can find it. Unless there's a way to extract it from one of my disk?

it can be extracted from a compellent installer ISO which a few people here have I think, I have a couple but they're a few years old. what's the exact disk model / dell PN?

 

[LumpyRareHawk]

it can be extracted from a compellent installer ISO which a few people here have I think, I have a couple but they're a few years old. what's the exact disk model / dell PN?

Dell PN of the disks are 08V7C5
They were pulled out of a Compellent 3020. The firmware release date is Q1 2020, so it should be on ISOs from 2020 and later.

 

[fohdeesha]

Dell PN of the disks are 08V7C5
They were pulled out of a Compellent 3020. The firmware release date is Q1 2020, so it should be on ISOs from 2020 and later.

View attachment 48164

apparently 1MB is too large to attach now so here's a link https://fohdeesha.com/data/other/FMDELPX05SRB384Y_AU0F_NS.zip

the file in the zip was pulled directly from the compellent ISO, I imagine it'll prolly have some weird compellent header data you'll need to trim out if you're gunna flash with sg_utils etc

edit: just actually read your previous replies and you're already on this version lol. yes it's fixed

 

[LumpyRareHawk]

apparently 1MB is too large to attach now so here's a link https://fohdeesha.com/data/other/FMDELPX05SRB384Y_AU0F_NS.zip

the file in the zip was pulled directly from the compellent ISO, I imagine it'll prolly have some weird compellent header data you'll need to trim out if you're gunna flash with sg_utils etc

edit: just actually read your previous replies and you're already on this version lol. yes it's fixed

Yeah it's not for me, it's for @Squigley @archiethemonger to try on their Y SSDs that are currently bricked and using AS10 to see if it would fix them.

As for mine running this firmware, I wasn't sure if it was fixed or not. You sure it is?

Thanks!