Toshiba Q300 unresponsive

Hi there,

I have a Toshiba Q300 SSD (128GB) that suddenly decided to not respond anymore.
Client's PC didn't recognise it anymore after 5 days use and in a different PC it wouldn't respond either.

dmesg output just says:

Code:: [1012057.952751] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen [1012057.952755] ata2: irq_stat 0x00400040, connection status changed [1012057.952756] ata2: SError: { PHYRdyChg CommWake DevExch } [1012057.952759] ata2: hard resetting link [1012063.724403] ata2: link is slow to respond, please be patient (ready=0) [1012067.988361] ata2: COMRESET failed (errno=-16) [1012067.988371] ata2: hard resetting link [1012073.736240] ata2: link is slow to respond, please be patient (ready=0) [1012078.016219] ata2: COMRESET failed (errno=-16) [1012078.016228] ata2: hard resetting link [1012083.792179] ata2: link is slow to respond, please be patient (ready=0) [1012113.035912] ata2: COMRESET failed (errno=-16) [1012113.035921] ata2: limiting SATA link speed to 3.0 Gbps [1012113.035923] ata2: hard resetting link [1012118.083808] ata2: COMRESET failed (errno=-16) [1012118.083818] ata2: reset failed, giving up [1012118.083823] ata2: EH complete

Now, it's still under warranty and it's not that expensive, but I'm wondering what kind of a failure this is. I can't seem to find a serial port on it, and I don't have something like a PC3K. Is there anything I can do with standard equipment?

Does the BIOS recognize the drive and it's capacity?

No, no detection on BIOS (legacy) systems and no detection on UEFI systems. USB-SATA bridge doesn't detect it either. The bridge itself is detected but it basically hangs and at some point times out trying to detect the disk.

The SSD does get slightly warmer when powered on, but not more than a few degrees celsius over room temperature. (and the room is about 19 degrees)

Upload detailed photos of both sides of the PCB and I'll try to identify the voltage test points for you.

Two pictures of both sides (once with direct light, once with indirect light... PCB's and their glare.. ugh): http://imgur.com/a/6aEFG

I noticed a few voltage TP's next to the SATA power connector, and two at the top of the PCB, as well as 3x GPIO pads and 1x 3v3 next to the SATA data connector. I haven't probed them yet.

I suspect that the GPIO pins would be the serial port. The T7 pins (on the underside) might be JTAG, but I'm only guessing.

I would measure the +3.3V (3V3) test points. I would also measure the 6 test points near the SATA power connector.

U30 is an e-fuse. There should be +5V at its output.

I have identified what I believe to the voltage test points at 6 switchmode (V1-V6) and 1 possible LDO linear regulator (V7). They are my best guesses. Your feedback should help me to correct any errors.

Attachments

Your Q300 SSD appears to be identical to an OCZ TRION 100 SSD.

Some time ago I analysed the TRION. Here are my notes:

TMP102, Texas Instruments, Low Power Digital Temperature Sensor With SMBus/Two-Wire Serial Interface, SOT563, marking CBZ, 1.4V - 3.6V:
http://www.ti.com/lit/ds/sbos397b/sbos397b.pdf

STEF4S, STMicroelectronics, electronic fuse for 3.3V and 5V lines:
http://www.st.com/web/en/resource/techn ... 095426.pdf

NT5CC256M16DP-DI, Nanya, SDRAM, 1.35V or 1.5V, x16, DDR3L-1600/1866, 96-ball BGA:
http://www.nanya.com/NanyaAdmin/GetFiles.ashx?ID=1448

RT8010GQW, Richtek, 1.5MHz, 1A, High Efficiency PWM Step-Down DC/DC Converter, 2.5V to 5.5V input, marking ET, adjustable:
http://www.richtek.com/assets/product_f ... 10A-10.pdf

marking FN5CA, 5V e-fuse, 10-pin, probably STEF4S

marking ETG, buck regulator, 6-pin, possibly RT8010GQW or equivalent
http://es.aliexpress.com/item/Free-ship ... o_detail_b
http://g02.a.alicdn.com/kf/HTB1zVjtIXXX ... s-lot-.jpg
photo shows "ETH" marking with same font and similar dots

marking EC4ZB or EC4Z8, buck regulator, 10-pin, probably STMicroelectronics

13 2C 13 2E alternate markings for EC4ZB on other PCBs
L1U 53Q

Code:: VCC ___ | +----. L .--------. | | Vout ___ .-|1 10|-| --- o-+----+--UUU--|-|2 9|-| --- | | '-|3 8|-' | | --- | | | | --- |4 7| === | | | | GND | | <--R--|5 6|--. | === '--------' | | GND | | | | ___ | +-|___|-+---+--------------' | | | | || | .-. '---||--' | | || | | '-' | | === GND

marking 63JC (63JB on other PCB), LDO regulator (?), 5-pin

marking AD, 5V power reset or supervisor (?), 3-pin, probably not Texas Instruments, possibly STMicroelectronics
- same pinout as CAT8801
http://www.onsemi.com/pub_link/Collateral/CAT8801-D.PDF

TH58TET0UDKBAEF, Toshiba NAND
TH58 = multichip
T = toggle mode NAND
E = Vcc/VccQ = ?? VCC = 2.7V to 3.6V, VCCQ = 2.7V to 3.6V / 1.7V to 1.95V (from TC58TEG6DCJTA00 datasheet)
T0 = 128GB = 1 Tbits
U = 8 level
D = org, page/block size ??
K = design rule ie nm ?? A19nm TLC (from anandtech)
BA = BGA, lead free, halogen free
E = number of channels and CEs ??
F = number of BGA balls, dimensions ?? 272-balls

Underside of PCB has two zero-ohm configuration resistors, S4 and S5, probably to select 1.8V or 3.3V for VccQ.

Also D1 (underside of PCB) is a bidirectional protection diode across 5V input.

That is a ton of good information! It does indeed look like a TRION 100, seems that is one of the first Toshiba-made OCZ's before they branded it with their own name.
Measurements so far:

Test points next to the SATA connector (in order of the photo):

5v
GND
2.5v
1.8v
1.34v (most likely 1v3 but my meter probably isn't too exact)
1v

Voltage regulators as tagged on the pictures:

V1= 3.3v
V2= 1v
V3= 1v
V4= 1v
V5= 1.8v
V6= 3.3v

V7: I measured the pins, there is 3, 3v3 and 2v5 on them. Let's say the bottom two pins are 1 and 2 and the top three are 3, 4 and 5 from left to right;
V7-2: 2.5v
V7-3: 3v
V7-5: 3.3v

With regards to the position next to the SATA connector with the four pins where you usually find a serial port/UART:

GPIO 104 = GND
3v3 = 3.3 Volt (as it should)
GPIO 103 = TX
GPIO 100 = RX

When powering on, GPIO 103 goes high for a bit.
The DMM I used is an Extech EX330. Not the worst meter in the world, but it's not a Fluke ;-)

I also checked if all chips seem to consume power, and they do, all BGA's are getting a few degrees above room temperature, so they are definitely getting power. I haven't hooked up a 3v3 serial adapter yet, but I'm not sure what to expect there. There is nothing like a boot log or anything as far as I can detect (I did simply connect a buzzer to TX and GND, it clicked once on boot), it's more like the CPU booting and enabling the GPIO/UART pin than actual data. Also not sure what baud to set if I were to try it out.

Small update:

I couldn't find any 3.3v level serial adapter so I connected it to the UART on a Raspberry Pi which didn't help much: on reset, the CPU on the SSD apparently sends SysRQ-compatible bits out the line as I get a SysRq Help page spammed every time I reset the thing. But at least I know I have the serial port connected right. No console I/O so far, it doesn't seem to take any command.

Since I had it connected to a USB-SATA bridge for easy powering (using a battery as power source), testing went smooth until the battery went flat, I decided to connect it to a USB port on a linux box here and I suddenly have SATA comms back! It's not doing any disk I/O, so still something wrong, but the CPU must be working. I can do Identify and SMART read. Logs and output:

dmesg:

Code:: [1309699.609845] usb 1-6: new high-speed USB device number 58 using xhci_hcd [1309699.739778] usb 1-6: New USB device found, idVendor=174c, idProduct=5136 [1309699.739781] usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [1309699.739782] usb 1-6: Product: AS2105 [1309699.739783] usb 1-6: Manufacturer: ASMedia [1309699.739784] usb 1-6: SerialNumber: 00000000000000000000 [1309699.740410] usb-storage 1-6:1.0: USB Mass Storage device detected [1309699.740543] scsi host14: usb-storage 1-6:1.0 [1309700.738548] scsi 14:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6 [1309700.738843] sd 14:0:0:0: Attached scsi generic sg13 type 0 [1309700.739213] sd 14:0:0:0: [sdn] 4032 512-byte logical blocks: (2.06 MB/1.96 MiB) [1309700.739608] sd 14:0:0:0: [sdn] Write Protect is off [1309700.739610] sd 14:0:0:0: [sdn] Mode Sense: 43 00 00 00 [1309700.739998] sd 14:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1309700.741965] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.741968] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.741969] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.741971] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.741972] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.741975] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.742592] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.742593] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.742595] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.742596] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.742597] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.742598] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.743201] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.743202] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.743203] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.743204] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.743205] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.743206] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.743806] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.743807] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.743808] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.743809] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.743809] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.743810] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.743813] ldm_validate_partition_table(): Disk read failed. [1309700.744431] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.744432] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.744433] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.744434] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.744435] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.744435] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.745056] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.745058] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.745059] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.745060] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.745061] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.745062] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.745681] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.745682] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.745683] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.745684] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.745684] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.745685] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.746306] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.746308] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.746309] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.746310] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.746311] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.746312] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.746324] Dev sdn: unable to read RDB block 0 [1309700.746930] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.746932] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.746933] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.746934] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.746934] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.746935] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.747555] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309700.747556] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309700.747557] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309700.747558] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309700.747559] blk_update_request: critical medium error, dev sdn, sector 0 [1309700.747560] Buffer I/O error on dev sdn, logical block 0, async page read [1309700.748807] sdn: unable to read partition table [1309700.750080] sd 14:0:0:0: [sdn] Attached SCSI disk [1309776.500872] scsi_io_completion: 4 callbacks suppressed [1309776.500877] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.500879] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.500880] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.500882] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.500883] blk_update_request: 4 callbacks suppressed [1309776.500884] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.500886] buffer_io_error: 3 callbacks suppressed [1309776.500887] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.501513] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.501515] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.501516] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.501518] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.501519] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.501520] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.503641] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.503643] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.503645] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.503646] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.503647] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.503649] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.504297] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.504299] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.504301] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.504302] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.504303] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.504305] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.504934] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.504936] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.504938] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.504939] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.504940] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.504942] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.505557] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.505558] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.505560] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.505561] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.505562] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.505563] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.505567] ldm_validate_partition_table(): Disk read failed. [1309776.506180] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.506181] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.506182] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.506183] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.506184] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.506184] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.506805] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.506806] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.506807] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.506807] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.506808] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.506809] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.507409] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.507410] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.507411] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.507412] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.507413] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.507413] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.508012] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309776.508013] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309776.508015] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309776.508016] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309776.508016] blk_update_request: critical medium error, dev sdn, sector 0 [1309776.508017] Buffer I/O error on dev sdn, logical block 0, async page read [1309776.508021] Dev sdn: unable to read RDB block 0 [1309776.510452] sdn: unable to read partition table [1309789.514014] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 30 ep 2 with no TDs queued? [1309789.514573] scsi_io_completion: 6 callbacks suppressed [1309789.514577] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309789.514579] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309789.514580] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309789.514582] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 20 00 [1309789.514583] blk_update_request: 6 callbacks suppressed [1309789.514584] blk_update_request: critical medium error, dev sdn, sector 0 [1309789.515205] sd 14:0:0:0: [sdn] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [1309789.515207] sd 14:0:0:0: [sdn] Sense Key : Medium Error [current] [1309789.515208] sd 14:0:0:0: [sdn] Add. Sense: Unrecovered read error [1309789.515210] sd 14:0:0:0: [sdn] CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [1309789.515211] blk_update_request: critical medium error, dev sdn, sector 0 [1309789.515212] buffer_io_error: 5 callbacks suppressed [1309789.515213] Buffer I/O error on dev sdn, logical block 0, async page read

smartctl -i:

Code:: smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.3.0-1-amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: TOSHIBA Q300 Serial Number: 75LB51AUKNRX LU WWN Device Id: 5 00080d c0026eae6 Firmware Version: SAFM11.1 User Capacity: 2,064,384 bytes [2.06 MB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Mar 3 02:05:23 2016 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled

smartctl -A:

Code:: smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.3.0-1-amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 0 167 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 0 168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 169 Unknown_Attribute 0x0003 000 000 010 Pre-fail Always FAILING_NOW 0 173 Unknown_Attribute 0x0012 200 200 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0023 069 069 030 Pre-fail Always - 31 (Min/Max 0/31)

Now, I don't know in what mode the SSD booted up or if any of the values are 'real', but it seems it's not completely dead after all. Interesting...

Update:

After unplugging and plugging it back in, it shows the same data. So now it's booting in whatever mode it's in (not using the NAND flash, as the capacity now reports something like 2MB), and it's staying there. I can finally see the firmware revision, and there does seem to be an update, but I'm not going to try to flash it as-is, unless there are no more other things to try.

I suspect that the SMART data and the 2.06 MB capacity are probably default values which indicate a firmware related problem, but others would be better placed to advise you.

The test points near the SATA connector seem to be OK. The DDR_VDDQ voltage matches the +1.35V supply for the SDRAM.

The other test points also appear OK, although I don't understand why there are so many 1V regulators. Normally I would associate 1V supplies with MCU cores, so I'm surprised that there appear to be 3 of them.

U39 does appear to be a 2.5V LDO linear regulator, although it could also be an adjustable type.

One more thing you could do is to measure the voltages at the two zero-ohm configuration resistors, S4 and S5, on the underside of PCB. These will probably be 3.3V and 1.8V.

I could be wrong, but it seems to me like a NAND problem. High chance the soldering joints have weakened.

More test points ...

Attachments

: S4_S5.jpg (67.96 KiB) Viewed 24379 times

: reg2.jpg (73.67 KiB) Viewed 24379 times

Perhaps forum member HaQue might be able to shed some light on how the SSD behaves with a missing NAND IC?

viewtopic.php?f=10&t=32747&start=0

Hi, Sorry haven't much time lately and haven't read anything but Francs post above. Normally shorting or removing a NAND will put the controller in a different mode. Exactly what this means can vary between vendors and also models of the same vendor. Some flash drive such as ones based on Silicon Motion controllers will show "Memory Bar" as the drive name, and trying to access it as a drive will show "I/O error"

Edit: just noticed the link, and now have better context. I can probably test in a day or 2 but right now just don't have the time

I also have a toshiba q300, it's 6 months old, I can hear a audible hiss and click from the ssd, it is also unmountable in a removable enclosure or in the laptop, also not showing in the bios... any suggestions? unit still under warranty so I'm iffy on opening the unit but I'm interested to see how this turns out... gl

Yes, the hiss and click from the SSD is feedback via the USB connection. Using internal SATA you don't get the sound issue. It's usually because of bad grounding on the system.

Anyway, so far no luck in getting it to behave differently. I'm trying to find out what to do with the UART pins or how to get them active. Maybe it requires a specific unlock sequence. At this moment it doesn't really output any usable data. I might try capturing the TX and posting it here as a hex file. Could also be simple jitter on a DC line causing random bits to appear tough.

As for it's current mode (whatever that is): it does work regardless of direct SATA or SATA-USB bridge connections as it is now. It seems all of this is due to a firmware bug, or bad handing of an environmental change (such as temperature or voltages). There was no special condition that triggered this, one day the client's system just decided to not boot anymore as the BIOS couldn't find the SSD. It didn't even hang when trying to detect, it just fails completely and moves on.

Hello together.
I have a Toshiba Q300 480GB SSD that I have used for 4 weeks without any problem. 2 days ago as I started my laptop and noticed that the SSD is not detected anymore. I have tried to power cycle the SSD more times without any success. I opened it and made the measurements on the V1,V2,V3,V4,V5,V6,V7 points and found following voltages:
V1= 3.05v
V2= 0.9v
V3= 0.9v
V4= 0.93v
V5= 1.67v
V6= 3.04v
V7-2= 2.29v (lower left pin)
V7-3= 2.61v (upper left pin)
V7-5= 3.05v (upper right pin)
What I have also noticed is that the 12V is completely missing when the SSD is connected to the Laptop (0V). The Laptop is bypassing the SSD detection without hanging or any hanging. As I not an expert in SSD, I want to ask you about your opinion. Do you have any hint?
Thank you.

I have also measured the points next to the SATA connector (from the left to the right) and got following:
0.9v
1.25V
1.67v
2.29v
0v
4.68v
Any further suggestions? Thank you.

Hello again, I also measured the V8, S4 and S5, below the values...
V8= 1.24v
S4= 1.67v
S5= 1.67v (upper point)
S5= 3.04v (lower point)
have no idea where to look now...

Where is the 12V missing from exactly? Mine didn't use 12V.

I still have mine (and I managed to crack the case without breaking the warranty seal haha), but haven't had the time to look into it.
Seems to be a controller config problem, either the config is bad or can't be read at all.

Toshiba Q300 unresponsive

Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive

Re: Toshiba Q300 unresponsive