Guide: Reviving Toshiba / Kioxia PX02 & PX05 drives

[fohdeesha]

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

 

[NablaSquaredG]

Doing the lords work, as always.

 

[ano]

batteling ewaste, getting good deals. thanks

 

[BackupProphet]

I vote for never ever buying Kioxia over another brand. Trust has to be earned.

 

[octris]

Hi, thank you so much, I immediately tried it, but it did not work, I got this:

root@truenas[~]# sg_inq /dev/sg22                                   
standard INQUIRY:
  PQual=0  PDT=0  RMB=0  LU_CONG=0  hot_pluggable=0  version=0x06  [SPC-4]
  [AERC=0]  [TrmTsk=0]  NormACA=1  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=164 (0xa4)   Peripheral device type: disk
 Vendor identification: IBM-E051
 Product identification: PX05SRB192     
 Product revision level: 6402
 Unit serial number: 3720A0CMTQHE

root@truenas[~]# sg_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg22
found sg_bsg_major=247
found sg_nvme_char_major=246
open /dev/sg22 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
      duration=220 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
ASC=26, vendor specific qualification ASCQ=99 (hex)
  Field replaceable unit code: 1
Raw sense data (in hex), sb_len=48, embedded_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 99 01 00
        00 00 00 00 54 02 02 00  00 00 00 00 00 00 78 00
        00 1d 32 20 1e 00 00 00  00 00 54 08 00 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode

 

[fohdeesha]

Hi, thank you so much, I immediately tried it, but it did not work, I got this:

root@truenas[~]# sg_inq /dev/sg22                                  
standard INQUIRY:
  PQual=0  PDT=0  RMB=0  LU_CONG=0  hot_pluggable=0  version=0x06  [SPC-4]
  [AERC=0]  [TrmTsk=0]  NormACA=1  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=164 (0xa4)   Peripheral device type: disk
Vendor identification: IBM-E051
Product identification: PX05SRB192    
Product revision level: 6402
Unit serial number: 3720A0CMTQHE

root@truenas[~]# sg_write_buffer -vvvvv -m 5 --in PX05.bin /dev/sg22
found sg_bsg_major=247
found sg_nvme_char_major=246
open /dev/sg22 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
      duration=220 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
ASC=26, vendor specific qualification ASCQ=99 (hex)
  Field replaceable unit code: 1
Raw sense data (in hex), sb_len=48, embedded_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 99 01 00
        00 00 00 00 54 02 02 00  00 00 00 00 00 00 78 00
        00 1d 32 20 1e 00 00 00  00 00 54 08 00 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode

what exact OS are you trying to flash on?

 

[fohdeesha]

also what's the output of smartctl -a /dev/sg22 (mostly curious about fw / revision)

 

[octris]

what exact OS are you trying to flash on?

TrueNAS Scale

also what's the output of smartctl -a /dev/sg22 (mostly curious about fw / revision)

root@truenas[~]# smartctl -a /dev/sg22
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.32-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               IBM-E051
Product:              PX05SRB192
Revision:             6402
Compliance:           SPC-4
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x50000397ac886975
Serial number:        3720A0CVTQHE
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Wed Oct 29 13:12:51 2025 CET
device Test Unit Ready  [medium or hardware error (serious)]
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

[fohdeesha]

TrueNAS Scale

root@truenas[~]# smartctl -a /dev/sg22
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.32-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               IBM-E051
Product:              PX05SRB192
Revision:             6402
Compliance:           SPC-4
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x50000397ac886975
Serial number:        3720A0CVTQHE
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Wed Oct 29 13:12:51 2025 CET
device Test Unit Ready  [medium or hardware error (serious)]
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

I worry the read-intensive variants PX05SRB (these: https://www.kioxia.com/content/dam/...et/productbrief/eSSD-PX05SRB-480GB-Series.pdf ) take a different sub-firmware, not the usual px05. hmmm

edit: I see it's also an IBM model, it's possible IBM is running modified firmware and will only allow their own -we'll have to wait for others to try to know more

 

[fohdeesha]

@octris think I got it, can you try both of these? If one works, let me know which one

 

[fohdeesha]

helps if i include the link:https://fohdeesha.com/data/other/test.zip

 

[octris]

Unfortunately, same error. The storwize I have btw does not recognize them at all.

root@truenas[~]# sg_write_buffer -vvvvv -m 5 --in 1.bin /dev/sg22
found sg_bsg_major=247
found sg_nvme_char_major=246
open /dev/sg22 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
      duration=28 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
 Raw sense data (in hex), sb_len=48, embedded_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 00 00 00
        00 00 00 00 54 02 02 00  00 00 00 00 00 00 78 00
        00 1d 32 20 1e 00 00 00  00 f0 54 08 00 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode
root@truenas[~]# sg_write_buffer -vvvvv -m 5 --in 2.bin /dev/sg22
found sg_bsg_major=247
found sg_nvme_char_major=246
open /dev/sg22 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
      duration=224 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
ASC=26, vendor specific qualification ASCQ=99 (hex)
  Field replaceable unit code: 1
 Raw sense data (in hex), sb_len=48, embedded_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 99 01 00
        00 00 00 00 54 02 02 00  00 00 00 00 00 00 78 00
        00 1d 32 20 1e 00 00 00  00 00 54 08 00 00 00 00
Write buffer failed: Illegal request, type: sense key, apart from Invalid opcode
root@truenas[~]#

 

[octris]

I have the option to actually take them apart btw, maybe flash something via a SOIC Clip?

 

[octris]

This contains the firmware right? The 2103 chip? Could I flash the bin directly?

 

[fohdeesha]

I have the option to actually take them apart btw, maybe flash something via a SOIC Clip?

shouldn't be necessary, it's rejecxting the files cuz they aren't right, forcing it on via jtag would just brick it further. DMing you. I should have the fw, but their header ident is a mess

 

[BackupProphet]

didnt work:

[olav@localhost ~]$ sudo sg_write_buffer -vvvvv -m 5 --in PX02-SED.bin /dev/sg1
open /dev/sg1 with flags=0x802
tried to read 8388608 bytes from PX02-SED.bin, got 1003520 bytes
will write 1003520 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1003520
    Write buffer cdb: [3b 05 00 00 00 00 0f 50 00 00]
    Write buffer parameter list (first 256 bytes):
50 58 30 32 44 48 57 46  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 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
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 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  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 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
00 00 00 00 00 00 00 00  00 00 00 00 00 0d 0a 1a
10 00 00 00 87 04 01 00  02 00 00 00 00 50 0f 00
check_file_type: file descriptor is sg device
      duration=1170 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
 Raw sense data (in hex), sb_len=48, calculated_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 00 00 00
        00 00 00 3b 08 02 03 00  00 00 00 00 00 00 23 00
        00 41 50 19 16 00 00 00  00 00 00 00 00 00 00 00
Write buffer failed: Sense category: 19



[olav@localhost ~]$ sudo smartctl -x /dev/sg1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.0-142.el10.x86_64_v2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: PX02SMU040
Revision: 0802
Compliance: SPC-4
User Capacity: 400,088,457,216 bytes [400 GB]
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: 0x500003967c8a8580
Serial number: 85Q0A034TZK9
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Wed Oct 29 22:03:57 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Enabled

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

Percentage used endurance indicator: 0%
Current Drive Temperature: 26 C
Drive Trip Temperature: 65 C

Manufactured in week 35 of year 2015
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 0.722 0
write: 0 0 0 0 0 1493.240 0

Non-medium error count: 969

No Self-tests have been logged

 

[fohdeesha]

didnt work:

[olav@localhost ~]$ sudo sg_write_buffer -vvvvv -m 5 --in PX02-SED.bin /dev/sg1
open /dev/sg1 with flags=0x802
tried to read 8388608 bytes from PX02-SED.bin, got 1003520 bytes
will write 1003520 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1003520
    Write buffer cdb: [3b 05 00 00 00 00 0f 50 00 00]
    Write buffer parameter list (first 256 bytes):
50 58 30 32 44 48 57 46  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 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
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 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  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 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
00 00 00 00 00 00 00 00  00 00 00 00 00 0d 0a 1a
10 00 00 00 87 04 01 00  02 00 00 00 00 50 0f 00
check_file_type: file descriptor is sg device
      duration=1170 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Raw sense data (in hex), sb_len=48, calculated_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 00 00 00
        00 00 00 3b 08 02 03 00  00 00 00 00 00 00 23 00
        00 41 50 19 16 00 00 00  00 00 00 00 00 00 00 00
Write buffer failed: Sense category: 19



[olav@localhost ~]$ sudo smartctl -x /dev/sg1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.0-142.el10.x86_64_v2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: PX02SMU040
Revision: 0802
Compliance: SPC-4
User Capacity: 400,088,457,216 bytes [400 GB]
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: 0x500003967c8a8580
Serial number: 85Q0A034TZK9
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Wed Oct 29 22:03:57 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Enabled

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

Percentage used endurance indicator: 0%
Current Drive Temperature: 26 C
Drive Trip Temperature: 65 C

Manufactured in week 35 of year 2015
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 0.722 0
write: 0 0 0 0 0 1493.240 0

Non-medium error count: 969

No Self-tests have been logged

Arg! That's my drive and the same SED bin I successfully recovered mine with...I see the revision string is totally different, just numerical like IBM drives....I worry IBM is actually running their own modified firmware that will not allow "vanilla" toshiba fw to be flashed. I will work on this. can you send me the output of sg_inq /dev/sg1 and sg_inq -p di /dev/sg1

 

[mattventura]

Is there a way to pre-emptively tell if my drives will have this issue before they get bricked? Can this command be used preemptively to prevent a failure?

 

[fohdeesha]

Is there a way to pre-emptively tell if my drives will have this issue before they get bricked? Can this command be used preemptively to prevent a failure?

the only way to know is to see what firmware version they're on, and see if it's before or after the bug was fixed.Another way to tell is to check if the drive has more than 70,000 power on hours - if it does, and it still works, it's on fixed firmware. smartctl -a /dev/sdX should show both these things

 

[fohdeesha]

didnt work:

[olav@localhost ~]$ sudo sg_write_buffer -vvvvv -m 5 --in PX02-SED.bin /dev/sg1
open /dev/sg1 with flags=0x802
tried to read 8388608 bytes from PX02-SED.bin, got 1003520 bytes
will write 1003520 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1003520
    Write buffer cdb: [3b 05 00 00 00 00 0f 50 00 00]
    Write buffer parameter list (first 256 bytes):
50 58 30 32 44 48 57 46  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 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
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 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  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 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
00 00 00 00 00 00 00 00  00 00 00 00 00 0d 0a 1a
10 00 00 00 87 04 01 00  02 00 00 00 00 50 0f 00
check_file_type: file descriptor is sg device
      duration=1170 ms
Write buffer:
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Raw sense data (in hex), sb_len=48, calculated_len=48
        70 00 05 00 00 00 00 28  00 00 00 00 26 00 00 00
        00 00 00 3b 08 02 03 00  00 00 00 00 00 00 23 00
        00 41 50 19 16 00 00 00  00 00 00 00 00 00 00 00
Write buffer failed: Sense category: 19



[olav@localhost ~]$ sudo smartctl -x /dev/sg1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.0-142.el10.x86_64_v2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: PX02SMU040
Revision: 0802
Compliance: SPC-4
User Capacity: 400,088,457,216 bytes [400 GB]
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: 0x500003967c8a8580
Serial number: 85Q0A034TZK9
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Wed Oct 29 22:03:57 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
Temperature Warning: Disabled or Not Supported
Read Cache is: Enabled
Writeback Cache is: Enabled

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

Percentage used endurance indicator: 0%
Current Drive Temperature: 26 C
Drive Trip Temperature: 65 C

Manufactured in week 35 of year 2015
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 0.722 0
write: 0 0 0 0 0 1493.240 0

Non-medium error count: 969

No Self-tests have been logged

so after some more digging IBM/Lenovo never had this model, or any PX02 for that matter, so it's not IBM (backed up by the fact vendor does not show IBM, like some PX05's have). I've tracked down and carved out the IBM custom firmwares for the PX05 series, so those will be fixed and flashable, but for your drive, I can't figure out where it comes from. It's not running standard toshiba firmware from what I can tell, do you have any guess as to it's origin? Anything on the label?