Sep 15, 2021
2
0
10
0
I was testing a faulty USB keyboard. When I plugged it in, it which produced a message that went something like "your device is drawing more power than what the USB port can supply". After that the computer froze, so I shutdown the power and rebooted. This was on Windows 10. Now, the internal SSD drive is no longer being recognized. The BIOS is reporting 0 bytes. It was a PNY 1TB drive. I connected it to a Linux machine and ran smartctl, and it gave the following output

=== START OF INFORMATION SECTION ===
Device Model: PS3111
Serial Number: 00222222120033100022
Firmware Version: 0956
User Capacity: 20,972,032 bytes [20.9 MB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Wed Sep 15 13:51:47 2021 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x00) Offline data collection not supported.
SMART capabilities: (0x0000) Automatic saving of SMART data is not implemented.
Error logging capability: (0x00) Error logging NOT supported.
No General Purpose Logging support.

SMART Error Log not supported

SMART Self-test Log not supported

Selective Self-tests/Logging not supported

dmesg shows:
[10628.027675] ata7.15: exception Emask 0x4 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027678] ata7.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027682] ata7.00: failed command: READ DMA
[10628.027689] ata7.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[10628.027692] ata7.00: status: { DRDY }
[10628.027696] ata7.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027699] ata7.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027702] ata7.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027705] ata7.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
[10628.027709] ata7.15: hard resetting link
[10633.489241] ata7.15: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[10633.489616] ata7.00: hard resetting link
[10633.950469] ata7.00: SATA link up 3.0 Gbps (SStatus 123 SControl 310)
[10633.950511] ata7.01: hard resetting link
[10634.957089] ata7.01: failed to resume link (SControl 0)
[10634.957447] ata7.01: SATA link down (SStatus 0 SControl 0)
[10634.957515] ata7.02: hard resetting link
[10635.964041] ata7.02: failed to resume link (SControl 0)
[10635.964337] ata7.02: SATA link down (SStatus 0 SControl 0)
[10635.964410] ata7.03: hard resetting link
[10636.970936] ata7.03: failed to resume link (SControl 0)
[10636.971249] ata7.03: SATA link down (SStatus 0 SControl 0)
[10636.971328] ata7.04: hard resetting link
[10637.977870] ata7.04: failed to resume link (SControl 0)
[10637.978169] ata7.04: SATA link down (SStatus 0 SControl 0)
[10637.978929] ata7.00: configured for UDMA/33
[10637.979012] sd 6:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[10637.979017] sd 6:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] [descriptor]
[10637.979020] sd 6:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4
[10637.979024] sd 6:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00
[10637.979026] blk_update_request: I/O error, dev sdb, sector 0
 
The SSD has suffered a firmware "panic". It has now reverted to "safe mode". The model now being reported is the part number of the Phison controller, PS3111.

Your data is inaccessible in this state.

Code:
Device Model: PS3111
Serial Number: 00222222120033100022
Firmware Version: 0956
User Capacity: 20,972,032 bytes [20.9 MB]
 
Sep 15, 2021
2
0
10
0
The SSD has suffered a firmware "panic". It has now reverted to "safe mode". The model now being reported is the part number of the Phison controller, PS3111.

Your data is inaccessible in this state.

Code:
Device Model: PS3111
Serial Number: 00222222120033100022
Firmware Version: 0956
User Capacity: 20,972,032 bytes [20.9 MB]
Any suggestions on it can be switched back to "normal mode"? I am not afraid of removing the chips and soldering them onto a working controller board, but I would rather do it through software if at all possible.
 

ASK THE COMMUNITY

TRENDING THREADS