Main » Forums home » Flash storage, SSD

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 6 of 6
  [ 116 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6
  Print view Previous topic | Next topic 
Author Message
fzabkar
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: March 20th, 2019, 17:15 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15525
Location: Australia
Does the "48H6ZI" chip have exactly the same markings on both PCBs? If not, then the differences could be in the date/batch code. I'm thinking that "48H" may be the part code, while "6Z" could be the year (2016) and week (26 or 52?).

_________________
A backup a day keeps DR away.
Top
 Profile  
 
maxfox04
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: March 21st, 2019, 5:30 
Offline

Joined: February 27th, 2019, 6:49
Posts: 13
Location: Estonia
Good day!
On donor board there are "54Y6ZI" chip at the same place, as "48H6ZI" on original board. On donor there is another "54Y6ZI", but on original board at the same place is "4C56ZI". I`m thinking it`s the same purpose chip, but don`t know what it does.
Also I repaired broken trace near 25211 and all voltages got rised:
5505VIN=5.2V
Storage caps voltage (pin 10) went up to 12.7V
Input voltage on all regulators also increased to 5.2V - as input voltage from SATA.
But PC still doesn`t recognises SSD... :(
It looks like all is stuck at the software or something like it...
Looks like I have to return original flash and MPS430 chips back to original board and hope that it will help.
Top
 Profile  
 
maxfox04
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: March 21st, 2019, 6:43 
Offline

Joined: February 27th, 2019, 6:49
Posts: 13
Location: Estonia
Success!
Needed to put original flash back and drive got recognised and right now copying all important data to external drive.
Fzabkar: Thank you so much for your efford, time and all important advices you gave me. Without your help I wouldn't be able to ressurect this drive.
Also can say, that MPS430 is from donor, and even it's slightly different it still maches this version of PCB.

Again many thanks!
Top
 Profile  
 
fzabkar
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: March 21st, 2019, 16:39 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15525
Location: Australia
I still can't identify that mystery part, but I suspect that its markings may be encoded as follows:

    1st char -> year of manufacture
    2nd char -> week
    3rd -> batch/country code

    6ZI -> device code

Congratulations anyway.


Edit:

FWIW, the TPS22920 load switch has a part marking of 6Z and comes in a DBGA package. However, its input voltage range is limited to 3.6V.

http://www.ti.com/lit/ds/symlink/tps22920.pdf

_________________
A backup a day keeps DR away.
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: June 27th, 2020, 9:10 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
Hello

Have a broken m2 drive Micron M600, detected by system, show as uninitialized in disk management, cannot initialize or fix MBR.

Made a measurement with DMM, there is 0 volts across two capacitors, unsure if they are blown or something else in circuit.
Also suspicious look the SATA line voltages, the measurements were done with only power connected to drive.

Any suggestion, what to start replacing?


Attachments:
20200626_102222.jpg
20200626_102222.jpg [ 1.32 MiB | Viewed 13400 times ]
20200626_111118.jpg
20200626_111118.jpg [ 1.1 MiB | Viewed 13400 times ]
Top
 Profile  
 
fzabkar
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: June 27th, 2020, 17:35 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15525
Location: Australia
ISTM that all the supply voltages are OK (3.3V, 2.5V, 1.8V, 1.2V). It's looking like a firmware fault.

_________________
A backup a day keeps DR away.
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: June 28th, 2020, 5:38 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
it is what i thought too at first, but i'm not so sure anymore, few hours before i noticed the drive failed a small screwdriver was dropped on the mainboard just above drive area while the system was on. continuity test with DMM is giving a beep on C1. also measured about -0.01V to -0.06V on few resistors nearby MSP430. this leaves me under impression part of the SoC is not initializing.

do you know what voltages should be on MSP430 pins? it is MSP430V402, looks like it is identical to MSP430G2353 as the latter one is also used in this same drive model according to this review image

Image
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: June 29th, 2020, 4:55 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
thought the same at first. small screwdriver was dropped on the mainboard above ssd area an hours before it would no longer boot (haven't noticed immediately because hdd was used for windows). 0 volts across capacitor sounds like a hw problem, DMM beeps with probes on the cap, reading 50 in continuity test, couldn't find other component in parallel with the cap... MSP430V402 looks like is identical to MSP430G2353 (is linking photos from other site not allowed, since my reply was submitted for moderation and it wasn't posted?)
Top
 Profile  
 
xapt
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: July 8th, 2020, 7:26 
Offline

Joined: July 8th, 2020, 7:01
Posts: 1
Location: Minsk
The power supply is broken. It worked undervoltage by 1.5-2 times. That is, instead of 5 volts 3 volts, instead of 12 volts 8. When I discovered and approached the computer, everything survived except for the SSD. SSD is not detected in the BIOS. The voltage was reduced and not increased, hardly something burned out. Can I use jumpers to try it? They discussed something similar, but my scheme is slightly different. Tell me please what you can try to do. Thank.


Attachments:
IMG_20200708_141150.jpg
IMG_20200708_141150.jpg [ 2.16 MiB | Viewed 13207 times ]
IMG_20200708_141215.jpg
IMG_20200708_141215.jpg [ 2.33 MiB | Viewed 13207 times ]
IMG_20200708_141302.jpg
IMG_20200708_141302.jpg [ 1.99 MiB | Viewed 13207 times ]
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: July 10th, 2020, 7:32 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
anyone know which part number is the marked 6pin IC? cannot see the reading on mine, it looks like MX100 drives have them too


Attachments:
Micron-M600-M.2-256GB-DRAM.jpg
Micron-M600-M.2-256GB-DRAM.jpg [ 181.03 KiB | Viewed 13155 times ]
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: July 19th, 2020, 10:07 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
ok, missed that this IC was identified as on the image
Image

IN to C1 cap give only 56ohm, while GND to C1 give 50ohm, is that good?

next, these voltages, pin pointed with black arrow (XIN) was always 0V, pin pointed with yellow arrow would measure 0.6V and then dropping fast to as low as 0.08V
pin pointed with white arrow (XOUT) was 1.8V, i made a mess somewhere while measuring voltages, it is 0V now and disk size is no longer detected in OS (SATA errors)

replace MSP430?


Attachments:
222.jpg
222.jpg [ 267.83 KiB | Viewed 12964 times ]
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: September 9th, 2020, 14:59 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
fzabkar wrote:
Here is the header for the fwb.img file (size 0xC00) in the M500 update:

Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  30 33 34 4D CD 4E 2D F8 54 C2 00 08 00 0A 2A ED  034MÍN-øTÂ....*í

The signature is "M430" which would suggest that it represents the firmware for the MSP430.

The following command executes the update:

    dosmcli.exe --bus ALL -U fwa.img --segmented 10 -p M500:S0:MU05 -t None --asic-fw fwb.img --bl fwc.img

The MCU is referred to as an ASIC.

Perhaps an alternative solution would have been to purchase a blank MSP430 and program it with the image from a suitable MX100 firmware update.


how likely it is the MSP430 doesn't need to be programmed at all, and the SSD bootcode would take care of it automatically?
i see some references inside the firmware update binary like:

"MSP430 Firmware Requires Repair"
"MSP430 Repaired with NOR Backup: OK"
"ERROR: MSP430 NULL image"
"Writing MSP430 Image to MSP430"

got a brand new MSP430G2353 meanwhile and trying to figure out what to do with it now
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: September 9th, 2020, 18:33 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
fzabkar wrote:
I still can't identify that mystery part, but I suspect that its markings may be encoded as follows:

    1st char -> year of manufacture
    2nd char -> week
    3rd -> batch/country code

    6ZI -> device code

Congratulations anyway.


Edit:

FWIW, the TPS22920 load switch has a part marking of 6Z and comes in a DBGA package. However, its input voltage range is limited to 3.6V.

http://www.ti.com/lit/ds/symlink/tps22920.pdf


one of these fell off while removing msp430. the pinout below IC corresponds to TPS22920 pinout in datasheet
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: April 7th, 2024, 0:39 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
continuing from here https://forum.hddguru.com/viewtopic.php?f=10&t=43617 tried to flash partially damaged dump to a new chip (same type M25P16), during POST it was taking long then threw out SMART not supported, continued to boot, errors on screen, after booted no device detected.

some 0201 SMD components were lost and i had to find another ones identical or as close as possible, here some confusion kicked in because of way these were designated (white square dot on top of resistor, as i understand it should indicate 0ohm, but here we have everything 270ohm, 300ohm, 6K, 1K etc with white dot - what the fuck is this?) and memory voltage was 0.45V, also 1.8V was not present.

to fix this rearranged some resistors, and resoldered 1.8V load switch as it did not sit properly

this time POST goes as usual, no messages, during OS boot they start to appear (boot is slowed down of course). drive is detected, tried to leave it on for 10 minutes then shut down and turn on again, but nothing has been reconstructed. it appears BIOS will need to be fixed manually. 1V, 1.23V, 1.85V are there as well as 3.3V. on the storage caps 17.28V i thought it is too much and tried to disconnect power cord to run laptop on battery only, but still same voltage

here are the related messages

Code:
[    0.515965] ahci 0000:00:11.0: version 3.0
[    0.516376] ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
[    0.516379] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pio ccc
[    0.517761] scsi host0: ahci
[    0.518055] scsi host1: ahci
[    0.518296] scsi host2: ahci
[    0.518534] scsi host3: ahci
[    0.518738] scsi host4: ahci
[    0.518976] scsi host5: ahci
[    0.519049] ata1: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509100 irq 20
[    0.519052] ata2: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509180 irq 20
[    0.519054] ata3: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509200 irq 20
[    0.519056] ata4: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509280 irq 20
[    0.519059] ata5: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509300 irq 20
[    0.519061] ata6: SATA max UDMA/133 abar m1024@0xd2509000 port 0xd2509380 irq 20

[    0.830661] ata6: SATA link down (SStatus 0 SControl 300)
[    0.830699] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.830727] ata5: SATA link down (SStatus 0 SControl 300)
[    0.830755] ata4: SATA link down (SStatus 0 SControl 300)
[    0.830791] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.830819] ata3: SATA link down (SStatus 0 SControl 300)
[    0.830895] ata1.00: ATA-8: OCZ-ARC100, 1.01, max UDMA/133
[    0.830897] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    0.839876] ata1.00: configured for UDMA/133
[    0.840103] scsi 0:0:0:0: Direct-Access     ATA      OCZ-ARC100       1.01 PQ: 0 ANSI: 5
[    0.853284] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    0.853308] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[    0.853441] sd 0:0:0:0: [sda] Write Protect is off
[    0.853444] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    0.853495] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.854312]  sda: sda1
[    0.854886] sd 0:0:0:0: [sda] Attached SCSI disk

[    3.941131] ata2.00: failed to enable AA (error_mask=0x1)
[    6.417442] ata2.00: READ LOG DMA EXT failed, trying unqueued
[    7.636949] ata2.00: failed to get Log Directory Emask 0x1
[    7.636951] ata2.00: ATA-10: Micron_M600_MTFDDAV256MBF, MA01, max UDMA/133
[    7.636952] ata2.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    7.919911] ata2.00: failed to get Identify Device Data, Emask 0x1
[   12.543788] ata2.00: failed to enable AA (error_mask=0x1)
[   12.621373] ata2.00: failed to get Log Directory Emask 0x1
[   13.117093] ata2.00: failed to get Identify Device Data, Emask 0x1
[   13.117097] ata2.00: configured for UDMA/133 (device error ignored)
[   13.117262] scsi 1:0:0:0: Direct-Access     ATA      Micron_M600_MTFD MA01 PQ: 0 ANSI: 5
[   13.131222] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   13.131262] ata2.00: Enabling discard_zeroes_data
[   13.131287] sd 1:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[   13.131289] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[   13.131454] sd 1:0:0:0: [sdb] Write Protect is off
[   13.131457] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   13.131508] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   13.131763] ata2.00: Enabling discard_zeroes_data
[   18.927491] ata2: failed to read log page 10h (errno=-5)
[   18.927528] ata2.00: exception Emask 0x1 SAct 0x4 SErr 0x0 action 0x0
[   18.927563] ata2.00: irq_stat 0x40000001
[   18.927598] ata2.00: failed command: READ FPDMA QUEUED
[   18.927636] ata2.00: cmd 60/08:10:00:00:00/00:00:00:00:00/40 tag 2 ncq dma 4096 in
[   18.927636]          res 41/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   18.927677] ata2.00: status: { DRDY ERR }
[   18.927710] ata2.00: error: { ABRT }
[   23.818734] ata2.00: failed to enable AA (error_mask=0x1)
[   26.865931] ata2.00: failed to get Log Directory Emask 0x1
[   29.347253] ata2.00: failed to get Identify Device Data, Emask 0x1
[   37.619699] ata2.00: failed to enable AA (error_mask=0x1)
[   40.584111] ata2.00: failed to get Log Directory Emask 0x1
[   43.191926] ata2.00: failed to get Identify Device Data, Emask 0x1
[   43.191929] ata2.00: configured for UDMA/133 (device error ignored)
[   43.191944] ata2: EH complete
[   43.205093] ata2.00: Enabling discard_zeroes_data
[   48.489537] ata2: failed to read log page 10h (errno=-5)
[   48.489573] ata2.00: NCQ disabled due to excessive errors
[   48.489575] ata2.00: exception Emask 0x1 SAct 0x10 SErr 0x0 action 0x0
[   48.489610] ata2.00: irq_stat 0x40000001
[   48.489644] ata2.00: failed command: READ FPDMA QUEUED
[   48.489681] ata2.00: cmd 60/08:20:00:00:00/00:00:00:00:00/40 tag 4 ncq dma 4096 in
[   48.489681]          res 41/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   48.489722] ata2.00: status: { DRDY ERR }
[   48.489760] ata2.00: error: { ABRT }
[   52.841119] ata2.00: failed to enable AA (error_mask=0x1)
[   52.928427] ata2.00: failed to get Log Directory Emask 0x1
[   53.232110] ata2.00: failed to get Identify Device Data, Emask 0x1
[   55.571414] ata2.00: failed to enable AA (error_mask=0x1)
[   56.398928] ata2.00: failed to get Log Directory Emask 0x1
[   58.273812] ata2.00: failed to get Identify Device Data, Emask 0x1
[   58.273815] ata2.00: configured for UDMA/133 (device error ignored)
[   58.273828] ata2: EH complete
[   60.854110] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   60.854154] ata2.00: irq_stat 0x40000001
[   60.854193] ata2.00: failed command: READ DMA
[   60.854234] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 22 dma 4096 in
[   60.854234]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   60.854289] ata2.00: status: { DRDY ERR }
[   60.854327] ata2.00: error: { ABRT }
[   63.249316] ata2.00: failed to enable AA (error_mask=0x1)
[   63.548272] ata2.00: failed to get Log Directory Emask 0x1
[   63.711722] ata2.00: failed to get Identify Device Data, Emask 0x1
[   64.770564] ata2.00: failed to enable AA (error_mask=0x1)
[   64.839050] ata2.00: failed to get Log Directory Emask 0x1
[   64.897732] ata2.00: failed to get Identify Device Data, Emask 0x1
[   64.897735] ata2.00: configured for UDMA/133 (device error ignored)
[   64.897748] ata2: EH complete
[   65.177107] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   65.177147] ata2.00: irq_stat 0x40000001
[   65.177185] ata2.00: failed command: READ DMA
[   65.177225] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 23 dma 4096 in
[   65.177225]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   65.177279] ata2.00: status: { DRDY ERR }
[   65.177316] ata2.00: error: { ABRT }
[   66.108741] ata2.00: failed to enable AA (error_mask=0x1)
[   66.472860] ata2.00: failed to get Log Directory Emask 0x1
[   68.587025] ata2.00: failed to get Identify Device Data, Emask 0x1
[   70.801023] ata2.00: failed to enable AA (error_mask=0x1)
[   72.331933] ata2.00: failed to get Log Directory Emask 0x1
[   72.819403] ata2.00: failed to get Identify Device Data, Emask 0x1
[   72.819406] ata2.00: configured for UDMA/133 (device error ignored)
[   72.819419] ata2: EH complete
[   73.321106] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   73.321146] ata2.00: irq_stat 0x40000001
[   73.321184] ata2.00: failed command: READ DMA
[   73.321224] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 24 dma 4096 in
[   73.321224]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   73.321279] ata2.00: status: { DRDY ERR }
[   73.321316] ata2.00: error: { ABRT }
[   74.158237] ata2.00: failed to enable AA (error_mask=0x1)
[   74.922513] ata2.00: failed to get Log Directory Emask 0x1
[   75.474763] ata2.00: failed to get Identify Device Data, Emask 0x1
[   78.083653] ata2.00: failed to enable AA (error_mask=0x1)
[   78.586504] ata2.00: failed to get Log Directory Emask 0x1
[   79.087432] ata2.00: failed to get Identify Device Data, Emask 0x1
[   79.087435] ata2.00: configured for UDMA/133 (device error ignored)
[   79.087448] ata2: EH complete
[   79.544105] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   79.544144] ata2.00: irq_stat 0x40000001
[   79.544182] ata2.00: failed command: READ DMA
[   79.544222] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 25 dma 4096 in
[   79.544222]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   79.544277] ata2.00: status: { DRDY ERR }
[   79.544314] ata2.00: error: { ABRT }
[   83.234211] ata2.00: failed to enable AA (error_mask=0x1)
[   83.574308] ata2.00: failed to get Log Directory Emask 0x1
[   83.878648] ata2.00: failed to get Identify Device Data, Emask 0x1
[   86.676831] ata2.00: failed to enable AA (error_mask=0x1)
[   87.269850] ata2.00: failed to get Log Directory Emask 0x1
[   87.680971] ata2.00: failed to get Identify Device Data, Emask 0x1
[   87.680974] ata2.00: configured for UDMA/133 (device error ignored)
[   87.680990] sd 1:0:0:0: [sdb] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   87.680993] sd 1:0:0:0: [sdb] tag#25 Sense Key : Illegal Request [current]
[   87.680996] sd 1:0:0:0: [sdb] tag#25 Add. Sense: Unaligned write command
[   87.681000] sd 1:0:0:0: [sdb] tag#25 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[   87.681014] blk_update_request: I/O error, dev sdb, sector 0
[   87.681054] Buffer I/O error on dev sdb, logical block 0, async page read
[   87.681098] ata2: EH complete
[   88.247049] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   88.247089] ata2.00: irq_stat 0x40000001
[   88.247126] ata2.00: failed command: READ DMA
[   88.247166] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 26 dma 4096 in
[   88.247166]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[   88.247222] ata2.00: status: { DRDY ERR }
[   88.247258] ata2.00: error: { ABRT }
[   90.175382] ata2.00: failed to enable AA (error_mask=0x1)
[   90.556796] ata2.00: failed to get Log Directory Emask 0x1
[   91.431298] ata2.00: failed to get Identify Device Data, Emask 0x1
[   94.895635] ata2.00: failed to enable AA (error_mask=0x1)
[   97.725086] ata2.00: failed to get Log Directory Emask 0x1
[   99.748702] ata2.00: failed to get Identify Device Data, Emask 0x1
[   99.748705] ata2.00: configured for UDMA/133 (device error ignored)
[   99.748718] ata2: EH complete
[  102.443111] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  102.443151] ata2.00: irq_stat 0x40000001
[  102.443189] ata2.00: failed command: READ DMA
[  102.443229] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 27 dma 4096 in
[  102.443229]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[  102.443284] ata2.00: status: { DRDY ERR }
[  102.443321] ata2.00: error: { ABRT }
[  107.362437] ata2.00: failed to enable AA (error_mask=0x1)
[  110.155674] ata2.00: failed to get Log Directory Emask 0x1
[  112.016021] ata2.00: failed to get Identify Device Data, Emask 0x1
[  114.195136] ata2.00: failed to enable AA (error_mask=0x1)
[  114.599967] ata2.00: failed to get Log Directory Emask 0x1
[  115.056393] ata2.00: failed to get Identify Device Data, Emask 0x1
[  115.056396] ata2.00: configured for UDMA/133 (device error ignored)
[  115.056409] ata2: EH complete
[  115.167107] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  115.167147] ata2.00: irq_stat 0x40000001
[  115.167184] ata2.00: failed command: READ DMA
[  115.167224] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 28 dma 4096 in
[  115.167224]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[  115.167279] ata2.00: status: { DRDY ERR }
[  115.167316] ata2.00: error: { ABRT }
[  115.586820] ata2.00: failed to enable AA (error_mask=0x1)
[  115.777539] ata2.00: failed to get Log Directory Emask 0x1
[  116.085981] ata2.00: failed to get Identify Device Data, Emask 0x1
[  121.464289] ata2.00: failed to enable AA (error_mask=0x1)
[  124.249129] ata2.00: failed to get Log Directory Emask 0x1
[  127.208265] ata2.00: failed to get Identify Device Data, Emask 0x1
[  127.208268] ata2.00: configured for UDMA/133 (device error ignored)
[  127.208281] ata2: EH complete
[  129.368108] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  129.368149] ata2.00: irq_stat 0x40000001
[  129.368187] ata2.00: failed command: READ DMA
[  129.368226] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 29 dma 4096 in
[  129.368226]          res 51/04:00:00:00:00/00:00:00:00:00/60 Emask 0x1 (device error)
[  129.368281] ata2.00: status: { DRDY ERR }
[  129.368318] ata2.00: error: { ABRT }
[  131.075137] ata2.00: failed to enable AA (error_mask=0x1)
[  136.160085] ata2.00: qc timeout (cmd 0x2f)
[  136.160096] ata2.00: failed to get Log Directory Emask 0x5
[  136.160097] ata2.00: failed to get Identify Device Data, Emask 0x40
[  136.160101] ata2.00: failed to set xfermode (err_mask=0x40)
[  136.160143] ata2: hard resetting link
[  136.470587] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  141.792060] ata2.00: qc timeout (cmd 0xec)
[  141.792071] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[  141.792072] ata2.00: revalidation failed (errno=-5)
[  141.792112] ata2: limiting SATA link speed to 1.5 Gbps
[  141.792114] ata2: hard resetting link
[  142.102637] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  152.544078] ata2.00: qc timeout (cmd 0xec)
[  152.544089] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[  152.544090] ata2.00: revalidation failed (errno=-5)
[  152.544128] ata2.00: disabled
[  152.544138] ata2: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x6 frozen t4
[  152.544183] ata2: SError: { HostInt }
[  152.544220] ata2: hard resetting link
[  152.854491] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  152.854499] ata2: EH complete
[  152.854508] sd 1:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  152.854511] sd 1:0:0:0: [sdb] tag#30 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[  152.854512] blk_update_request: I/O error, dev sdb, sector 0
[  152.854551] Buffer I/O error on dev sdb, logical block 0, async page read
[  152.854628] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  152.854632] sd 1:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[  152.854634] blk_update_request: I/O error, dev sdb, sector 0
[  152.854674] Buffer I/O error on dev sdb, logical block 0, async page read
[  152.854728] ldm_validate_partition_table(): Disk read failed.
[  152.854756] sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  152.854759] sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[  152.854760] blk_update_request: I/O error, dev sdb, sector 0
[  152.854799] Buffer I/O error on dev sdb, logical block 0, async page read
[  152.854852]  sdb: unable to read partition table
[  152.855081] sd 1:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  152.855083] sd 1:0:0:0: [sdb] Sense not available.
[  152.855144] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  152.855146] sd 1:0:0:0: [sdb] Sense not available.
[  152.855324] sd 1:0:0:0: [sdb] Attached SCSI disk
[  154.221502] sd 1:0:0:0: [sdb] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  154.221508] sd 1:0:0:0: [sdb] tag#25 CDB: ATA command pass through(16) 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
[  162.361298] sd 1:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  162.361304] sd 1:0:0:0: [sdb] tag#29 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e6 00
[  162.361321] sd 1:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  162.361323] sd 1:0:0:0: [sdb] tag#30 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 40 99 00
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: April 7th, 2024, 13:49 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
R19, R20, R31 have been lost as well as resistor next to R18
R19 and R20 replaced with 100ohm, R31 with 22K
i took off R4 and R5, put R4 next to R18, and in place of R4 22K, R5 67K

C1 from voltage screenshot also lost, no idea if it is 220nF or maybe 1uF, installed there 330nF. it appeared at first this C1 had connection to one of resistors on the bottom side of the CPU, but there was something wrong with this (maybe because of shorted CPU?) as it now appears not to be connected to the same resistor. this is in fact a single line under the CPU bypassed to GND. either way still no voltage on it even though the resistance is not in low 50ohm range anymore

in windows it is installed, then disk management prompts to initialize it and fails with I/O error. no idea if it has anything to do with the D9RLT memory, is this chip powered via 3.3V ?

Attachment:
RESISTORS.jpg
RESISTORS.jpg [ 1005.18 KiB | Viewed 267 times ]
Attachment:
20200626.jpg
20200626.jpg [ 1.13 MiB | Viewed 267 times ]


I/O would look like SATA interface, it looks like differential voltage there is OK. and if this was bad there would be no any kind of information from the disk provided to the OS, like FW version, right?
so it is internal I/O problem
Top
 Profile  
 
westcoast
 Post subject: Re: Crucial MX100 repair after PSU failure
PostPosted: April 8th, 2024, 14:26 
Offline

Joined: June 27th, 2020, 8:58
Posts: 22
Location: europe
when i first looked up reviews for this ssd some of the sites incorrectly decoded D9RLT part and result in digikey showed operating voltage such as 1.8-2.5 V
now i found correct part and digikey specifies it as 1.13-1.30V. good thing i did not experiment with 1.4V feedback resistors and took the correct one from 1.8V divider
so it's safe to assume there is nothing wrong with memory

a logical next step would be to try recover damaged BIOS tables, but the question coming up is: were they electrically damaged (overwritten) during or after failure.
if yes, this would result in nothing again.
even if BIOS weren't damaged and i could get all the original content, there were attempts to do security erase afterwards, and we know these ssd fool up on such attempts and remain in dumb state even when there is no hardware failure. so a 100% working BIOS does not guarantee anything.

a dumb drive with messages like the above posted ones can be recovered via JTAG. but this requires some work as well. this is what i'm going to focus on as the data are not important to recover
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 6 of 6
  [ 116 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6

Main » Forums home » Flash storage, SSD

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 15 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Switch to mobile style
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group