Guide: Reviving Toshiba / Kioxia PX02 & PX05 drives

[BackupProphet]

It looks like a generic Toshiba. I've been trying to find images on Ebay of the same SSD with the same series of firmware version on Ebay. But without success.

sudo sg_inq /dev/sg1
standard INQUIRY:
  PQual=0  PDT=0  RMB=0  LU_CONG=0  hot_pluggable=0  version=0x06  [SPC-4]
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=1  Resp_data_format=2
  SCCS=0  ACC=0  TPGS=0  3PC=0  Protect=1  [BQue=0]
  EncServ=0  MultiP=1 (VS=0)  [MChngr=0]  [ACKREQQ=0]  Addr16=0
  [RelAdr=0]  WBus16=0  Sync=0  [Linked=0]  [TranDis=0]  CmdQue=1
  [SPI: Clocking=0x0  QAS=0  IUS=0]
    length=96 (0x60)   Peripheral device type: disk
 Vendor identification: TOSHIBA
 Product identification: PX02SMU040     
 Product revision level: 0802


sudo sg_inq -p di /dev/sg1
VPD INQUIRY: Device Identification VPD page
Designation descriptor number 1, descriptor length: 12
designator_type: NAA, code_set: Binary
associated with the Addressed logical unit
NAA 5, AOI: 0x39
Vendor Specific Identifier: 0x67c8a8580
[0x500003967c8a8580]
Designation descriptor number 2, descriptor length: 12
transport: Serial Attached SCSI Protocol (SPL-4)
designator_type: NAA, code_set: Binary
associated with the Target port
NAA 5, AOI: 0x39
Vendor Specific Identifier: 0x67c8a8582
[0x500003967c8a8582]
Designation descriptor number 3, descriptor length: 8
transport: Serial Attached SCSI Protocol (SPL-4)
designator_type: Relative target port, code_set: Binary
associated with the Target port
Relative target port: 0x1
Designation descriptor number 4, descriptor length: 12
transport: Serial Attached SCSI Protocol (SPL-4)
designator_type: NAA, code_set: Binary
associated with the Target device that contains addressed lu
NAA 5, AOI: 0x39
Vendor Specific Identifier: 0x67c8a8581
[0x500003967c8a8581]
Designation descriptor number 5, descriptor length: 28
transport: Serial Attached SCSI Protocol (SPL-4)
designator_type: SCSI name string, code_set: UTF-8
associated with the Target device that contains addressed lu
SCSI name string:
naa.500003967C8A8581

 

[therem]

UPDATE: currently a known issue with IBM/lenovo versions not taking these vanilla firmwares - working on it

TLDR: these series of drives have a 70k power on hours bug where after this amount of time, they brick themselves and become useless, with no access to your data. Toshiba fixed this in firmware which revives the drive and gets your data back too, but they refused to send it to anyone, and now are claiming they don't have access to it anymore. I've seen people with ~100 of these things now acting as door stops, here's how to revive them and get your drives back. shame on these shit companies who contribute to a massive e-waste issue, I highly recommend not purchasing Toshiba / Kioxia in the future

https://fohdeesha.com/docs/store/Toshiba-PX-Firmware.zip

# If you don't have it already:
apt install sg3-utils
# Flashing on *bsd (like truenas core) probably won't work in my experience due to weird CAM memory mapping shortfalls
# These commands all assume your dead drive is /dev/sg0, confirm that with smartctl -a /dev/sg0. It might be sg1 sg2 etc
# These are pretty safe as they confirm the firmware matches type and signature before flashing
# If it works you should get no errors
# After flashing remove and replug, or otherwise fully power cycle drive to take effect (not just warm server reboot)
# Should work regardless of OEM / vendor

PX02 Regular Models:

- PX02SMF020
- PX02SMF040
- PX02SMF080
- PX02SMB160

sg_write_buffer -vvvvv -m 5 --in PX02.bin /dev/sg0



PX02 SED Models:

- PX02SMU020
- PX02SMU040
- PX02SMU080
- PX02SMQ160

sg_write_buffer -vvvvv -m 5 --in PX02-SED.bin /dev/sg0



PX05 Regular Models:

- PX05SVB040
- PX05SVB080
- PX05SVB160
- PX05SVB320
- PX05SVB048
- PX05SVB096
- PX05SVB192
- PX05SVB384
- PX05SRB048
- PX05SRB096
- PX05SRB192
- PX05SRB384
- PX05SHB020
- PX05SHB040
- PX05SHB080
- PX05SHB160
- PX05SMB040
- PX05SMB080
- PX05SMB160
- PX05SMB320

sg_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg0



PX05 SED Models:
- PX05SVQ040
- PX05SVQ080
- PX05SVQ160
- PX05SVQ320
- PX05SVQ048
- PX05SVQ096
- PX05SVQ192
- PX05SVQ384
- PX05SRQ048
- PX05SRQ096
- PX05SRQ192
- PX05SRQ384
- PX05SHQ020
- PX05SHQ040
- PX05SHQ080
- PX05SHQ160
- PX05SMQ040
- PX05SMQ080
- PX05SMQ160
- PX05SMQ320

sg_write_buffer -vvvvv -m 5 --in PX05-SED.bin /dev/sg0




----------------
- FIPS models end with B, need signed image, contact me jon@fohdeesha.com
- If your exact model isn't on here, contact me. I know models ending in Y, like PX05SMB080Y, are SIE (secure instant erase) models, they may take the SED firmware, not sure. try and report back
- toshiba: suck my ass

Many thanks for this amazing job

Just would like to share the way I managed to reuse DELL UNITY EMC3200 3.2TB SSDs (Toshiba PX05SRB384) like any standard SAS 512e SSD drives in any server, any controller and any OS :

1) First re-format the drive to 512B/4K standard sector size : https://forums.servethehome.com/index.php?threads/how-to-reformat-hdd-ssd-to-512b-sector-size.4968/

2) Check for firmware update to avoid this f*** 70k power-on hours wall bug. The provided FW pack files

https://fohdeesha.com/docs/store/Toshiba-PX-Firmware.zip

and

https://fohdeesha.com/data/other/test.zip

did not match my drives DELL/EMC Firmware (QC4F) so the update process failed. BUT I found QC4F is actually the latest existing firmware version for those drives as per this UNITY document (Jul 23, 2024). So I guess my drives should be safe. Fingers crossed

sudo sg_scan  -i
/dev/sg0: scsi0 channel=0 id=0 lun=0 [em]
    SMI       USB DISK          1100 [rmb=1 cmdq=0 pqual=0 pdev=0x0]
/dev/sg1: scsi1 channel=0 id=0 lun=0
    HP        P440ar            7.00 [rmb=0 cmdq=1 pqual=0 pdev=0xc]
/dev/sg2: scsi1 channel=0 id=1 lun=0
    TOSHIBA   5SVB320C EMC3200  QC4F [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg3: scsi1 channel=0 id=2 lun=0
    TOSHIBA   5SVB320C EMC3200  QC4F [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg4: scsi1 channel=0 id=3 lun=0
    TOSHIBA   5SVB320C EMC3200  QC4F [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg5: scsi1 channel=0 id=4 lun=0
    TOSHIBA   5SVB320C EMC3200  QC4F [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg6: scsi1 channel=0 id=5 lun=0
    HP        P440ar            7.00 [rmb=0 cmdq=0 pqual=0 pdev=0xd]

sudo sg_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg2
found sg_bsg_major=244
found sg_nvme_char_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from PX05.bin, got 1173504 bytes
will write 1173504 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1173504
    Write buffer cdb: [3b 05 00 00 00 00 11 e8 00 00]
    Write buffer parameter list (first 256 bytes):
50 4d 30 34 44 48 57 46  0d 0a 0d 0a 54 75 65 73
64 61 79 2c 20 53 65 70  74 65 6d 62 65 72 20 32
38 2c 20 32 30 32 31 20  31 39 3a 33 30 3a 30 36
20 62 79 74 73 62 67 6c  65 0d 0a 43 6f 70 79 72
69 67 68 74 20 28 43 29  20 54 4f 53 48 49 42 41
20 43 4f 52 50 4f 52 41  54 49 4f 4e 2e 0d 0a 41
6c 6c 20 72 69 67 68 74  73 20 72 65 73 65 72 76
65 64 2e 0d 0a 50 34 4d  3a 37 37 3a 30 36 3a 30
31 3a 30 30 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 0d 0a 1a
00 00 00 00 77 06 01 00  03 00 00 00 00 e8 11 00
check_file_type: file descriptor is sg device
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument

sudo sg_write_buffer -vvvvv -m 5 --in 1.bin /dev/sg2
found sg_bsg_major=244
found sg_nvme_char_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from 1.bin, got 1117184 bytes
will write 1117184 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1117184
    Write buffer cdb: [3b 05 00 00 00 00 11 0c 00 00]
    Write buffer parameter list (first 256 bytes):
50 58 30 35 44 48 57 46  0d 0a 0d 0a 54 68 75 72
73 64 61 79 2c 20 4d 61  79 20 30 38 2c 20 32 30
32 35 20 31 36 3a 30 30  3a 33 37 20 62 79 74 73
62 67 6c 65 0d 0a 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
50 35 4d 3a 37 32 3a 30  37 3a 30 31 3a 30 30 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 0d 0a 1a
20 20 20 20 20 20 20 20  4e 41 35 36 00 00 00 00
40 00 00 00 00 00 00 00  40 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 08 11 00
40 00 00 00 72 07 01 00  04 00 00 00 00 0c 11 00
check_file_type: file descriptor is sg device
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument

sudo sg_write_buffer -vvvvv -m 5 --in 2.bin /dev/sg2
found sg_bsg_major=244
found sg_nvme_char_major=243
open /dev/sg2 with flags=0x802
tried to read 8388608 bytes from 2.bin, got 1179648 bytes
will write 1179648 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1179648
    Write buffer cdb: [3b 05 00 00 00 00 12 00 00 00]
    Write buffer parameter list (first 256 bytes):
50 4d 30 34 44 48 57 46  0d 0a 0d 0a 54 75 65 73
64 61 79 2c 20 53 65 70  74 65 6d 62 65 72 20 32
38 2c 20 32 30 32 31 20  31 39 3a 32 38 3a 34 36
20 62 79 74 73 62 67 6c  65 0d 0a 43 6f 70 79 72
69 67 68 74 20 28 43 29  20 54 4f 53 48 49 42 41
20 43 4f 52 50 4f 52 41  54 49 4f 4e 2e 0d 0a 41
6c 6c 20 72 69 67 68 74  73 20 72 65 73 65 72 76
65 64 2e 0d 0a 50 34 4d  3a 37 32 3a 30 35 3a 30
31 3a 30 30 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 0d 0a 1a
00 00 00 00 72 05 01 00  03 00 00 00 00 00 12 00
check_file_type: file descriptor is sg device
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument

sudo smartctl -a /dev/sg2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.10.10-1-liquorix-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               TOSHIBA
Product:              5SVB320C EMC3200
Revision:             QC4F
Compliance:           SPC-4
User Capacity:        3.200.824.377.344 bytes [3,20 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
Logical Unit id:      0x58ce38ee2039e3ad
Serial number:        xxxxxxx
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Sun Nov  2 10:02:37 2025 CET
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 26%
Current Drive Temperature:     29 C
Drive Trip Temperature:        63 C

Accumulated power on time, hours:minutes 56291:58
Manufactured in week 21 of year 2018
Specified cycle count over device lifetime:  33554432
Accumulated start-stop cycles:  25
Elements in grown defect list: 0

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0          0    2463598,728           0
write:         0        0         0         0          0     659560,139           0
verify:        0        0         0         0          0     216696,973           0

Non-medium error count:      630

No Self-tests have been logged

cat /etc/debian_version
12.12

NOTE : P440ar in HBA mode

Thanks again mate.

 

[TheCodeLife]

I bought a bunch of used PX05SRB384 drives a few years ago that appear to be from Toshiba, but I have been unsuccessful with the firmware update.

I am running the latest version of Proxmox on a H730p in HBA mode. When I try updating the drive, I get the following message:

g_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg3
open /dev/sg3 with flags=0x802
tried to read 8388608 bytes from PX05.bin, got 1173504 bytes
will write 1173504 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1173504
    Write buffer cdb: [3b 05 00 00 00 00 11 e8 00 00]
    Write buffer parameter list (first 256 bytes):
50 4d 30 34 44 48 57 46  0d 0a 0d 0a 54 75 65 73
64 61 79 2c 20 53 65 70  74 65 6d 62 65 72 20 32
38 2c 20 32 30 32 31 20  31 39 3a 33 30 3a 30 36
20 62 79 74 73 62 67 6c  65 0d 0a 43 6f 70 79 72
69 67 68 74 20 28 43 29  20 54 4f 53 48 49 42 41
20 43 4f 52 50 4f 52 41  54 49 4f 4e 2e 0d 0a 41
6c 6c 20 72 69 67 68 74  73 20 72 65 73 65 72 76
65 64 2e 0d 0a 50 34 4d  3a 37 37 3a 30 36 3a 30
31 3a 30 30 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 0d 0a 1a
00 00 00 00 77 06 01 00  03 00 00 00 00 e8 11 00
check_file_type: file descriptor is sg device
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument

The drive information is from smartctl is this:

smartctl -a /dev/sg3
smartctl 7.4 2024-10-15 r5620 [x86_64-linux-6.14.11-4-pve] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               TOSHIBA
Product:              5SRB384CCLAR3840
Revision:             RC4F
Compliance:           SPC-4
User Capacity:        3,840,774,504,448 bytes [3.84 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
Logical Unit id:      0x58ce38ee2022eba5
Serial number:        3810A0FGT3EE
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Tue Nov  4 21:28:01 2025 EST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 26%
Current Drive Temperature:     23 C
Drive Trip Temperature:        63 C

Accumulated power on time, hours:minutes 64416:18
Manufactured in week 09 of year 2018
Specified cycle count over device lifetime:  33554432
Accumulated start-stop cycles:  25
Elements in grown defect list: 1

All of my drives appear to have the same revision, but I haven't been able to find any information on it. Perhaps no update is needed, but I am a bit anxious as I have a bunch of these drives and I'm concerned they will fail since they are near the 70,000 hour mark. Any help would be greatly appreciated!

 

[fohdeesha]

I bought a bunch of used PX05SRB384 drives a few years ago that appear to be from Toshiba, but I have been unsuccessful with the firmware update.

I am running the latest version of Proxmox on a H730p in HBA mode. When I try updating the drive, I get the following message:

g_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg3
open /dev/sg3 with flags=0x802
tried to read 8388608 bytes from PX05.bin, got 1173504 bytes
will write 1173504 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1173504
    Write buffer cdb: [3b 05 00 00 00 00 11 e8 00 00]
    Write buffer parameter list (first 256 bytes):
50 4d 30 34 44 48 57 46  0d 0a 0d 0a 54 75 65 73
64 61 79 2c 20 53 65 70  74 65 6d 62 65 72 20 32
38 2c 20 32 30 32 31 20  31 39 3a 33 30 3a 30 36
20 62 79 74 73 62 67 6c  65 0d 0a 43 6f 70 79 72
69 67 68 74 20 28 43 29  20 54 4f 53 48 49 42 41
20 43 4f 52 50 4f 52 41  54 49 4f 4e 2e 0d 0a 41
6c 6c 20 72 69 67 68 74  73 20 72 65 73 65 72 76
65 64 2e 0d 0a 50 34 4d  3a 37 37 3a 30 36 3a 30
31 3a 30 30 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20  20 20 20 20 20 0d 0a 1a
00 00 00 00 77 06 01 00  03 00 00 00 00 e8 11 00
check_file_type: file descriptor is sg device
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument

The drive information is from smartctl is this:

smartctl -a /dev/sg3
smartctl 7.4 2024-10-15 r5620 [x86_64-linux-6.14.11-4-pve] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               TOSHIBA
Product:              5SRB384CCLAR3840
Revision:             RC4F
Compliance:           SPC-4
User Capacity:        3,840,774,504,448 bytes [3.84 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
Logical Unit id:      0x58ce38ee2022eba5
Serial number:        3810A0FGT3EE
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Tue Nov  4 21:28:01 2025 EST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 26%
Current Drive Temperature:     23 C
Drive Trip Temperature:        63 C

Accumulated power on time, hours:minutes 64416:18
Manufactured in week 09 of year 2018
Specified cycle count over device lifetime:  33554432
Accumulated start-stop cycles:  25
Elements in grown defect list: 1

All of my drives appear to have the same revision, but I haven't been able to find any information on it. Perhaps no update is needed, but I am a bit anxious as I have a bunch of these drives and I'm concerned they will fail since they are near the 70,000 hour mark. Any help would be greatly appreciated!

I don't recognize that firmware string, but I think you're probably fine. just be sure to have backups in case they do die. As for the flash error, you can't flash these through raid cards like the perc in their pretend HBA mode, you need something with direct vanilla access. It could be proxmox getting in the way, you could try live booting debian or something

 

[TheCodeLife]

Thanks! Is the firmware you provided the latest version? Even if I'm not affected by the 70K hour issue, I know there were some write endurance bugs in some versions of firmware as well. I was already considering replacing the perc with an HBA330 that I can use in IT mode.