Текущее время: 19 апр 2024, 03:05




 Страница 1 из 1 [ Сообщений: 5 ] 
Автор
Сообщение
[ТС]
 Заголовок сообщения: Micron M600 drive damaged
СообщениеДобавлено: 01 окт 2020, 02:34 
Интересующийся
Интересующийся
Аватара пользователя
Зарегистрирован: 01 окт 2020, 02:15
Наличности на руках:
111.19

Сообщения: 143
Откуда: europe
Hello

Dropped a small screwdriver on the mainboard, it hit EC, on the bottom side was this drive. After that it no longer mounts or boot, but it was still detected in OS with full size - only unallocated.
Then, during diagnose, made a short somewhere and also drive did not recognized anymore at all. After made a short I lost 1.8V on R10, does it mean the MSP430 is gone?

For reference here is what I gathered:

Вложение:
20200626_111118.jpg


Вложение:
RESISTORS.jpg


У вас нет доступа для просмотра вложений:
1. Пожалуйста авторизуйтесь или зарегистрируйтесь.
2. Вы должны иметь 15 (ПЯТНАДЦАТЬ) или более сообщений.
3. У нас можно купить доступ к файлам.


Не в сети
 Профиль    
 
[ТС]
 Заголовок сообщения: Re: Micron M600 drive damaged
СообщениеДобавлено: 30 янв 2024, 13:42 
Интересующийся
Интересующийся
Аватара пользователя
Зарегистрирован: 01 окт 2020, 02:15
Наличности на руках:
111.19

Сообщения: 143
Откуда: europe
anybody out there having a chip or dump of MA01 fw ? the drive came from some asus laptop.
M25P16 is damaged


Не в сети
 Профиль    
 
[ТС]
 Заголовок сообщения: Re: Micron M600 drive damaged
СообщениеДобавлено: 05 фев 2024, 06:59 
Интересующийся
Интересующийся
Аватара пользователя
Зарегистрирован: 01 окт 2020, 02:15
Наличности на руках:
111.19

Сообщения: 143
Откуда: europe
both RAU and TPS22920x taken off, TPS are identical, one RAU has lower resistance in SW pin. 5505 and MSP430 off, 3.3V went from 6 to 3 ohm. started to worry about NAND. then applied 3.3V and about 300mA goes and 88ss9189 heats up.
marvell down, 3.3V goes into kiloohms - NAND appears OK. and looks like MSP430 also survived, but need to compare it better than just VCC
parts ordered, some already shipped few days ago


Не в сети
 Профиль    
 
[ТС]
 Заголовок сообщения: Re: Micron M600 drive damaged
СообщениеДобавлено: 26 мар 2024, 01:18 
Интересующийся
Интересующийся
Аватара пользователя
Зарегистрирован: 01 окт 2020, 02:15
Наличности на руках:
111.19

Сообщения: 143
Откуда: europe
with some help on hddguru a progress has been made

M25P16 with only 13ohm on VCC was getting hot, but still detected and most of the data looked good

     0      ??               CORRUPT
 30000      Identify Device            OK
 40000      BOOT (marvell bootloader)      OK
 50000      ?? table            OK
 60000      zero marker            OK
 B0000      DSSR table            OK
 C0000      multi DSSR table         OK
 E0000      MSP430 fw            OK
110000      unknown table            OK
130000      unknown table            CORRUPT
140000      unknown table (ascii indicate thermal)   OK
150000      unknown table            CORRUPT
170000      unknown               OK
1A0000      backup of unknown at 170000      OK
1F0000      signature?            OK


now it was figured out first (most damaged) block is the same as BOOT block at 0x40000 (backup), the two coruppted tables have about 100 or less bytes of difference when compared multiple dumps.

if someone have any kind of micron/crucial dump from disk with 88ss9189 cpu please share here (or in private message)


Не в сети
 Профиль    
 
[ТС]
 Заголовок сообщения: Re: Micron M600 drive damaged
СообщениеДобавлено: 10 апр 2024, 10:16 
Интересующийся
Интересующийся
Аватара пользователя
Зарегистрирован: 01 окт 2020, 02:15
Наличности на руках:
111.19

Сообщения: 143
Откуда: europe
flashed new BIOS with what was recovered, in short, drive starts it's detected but with same messages as before. as there have been attempts already to do secure erase, it is probably fooled now and 100% working BIOS would not help anyway.

it can be fixed with JTAG, but need to map pins first somehow, and the question now is what voltage levels 88ss9189 is working at on JTAG port ?

should i use level shifter or 3.3V is safe ?

[    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


Не в сети
 Профиль    
 
Показать сообщения за:  Поле сортировки  
 Страница 1 из 1 [ Сообщений: 5 ] 


   Похожие темы   Автор   Ответы   Просмотры   Последнее сообщение 
Эта тема закрыта, вы не можете редактировать и оставлять сообщения в ней. БП Hiper Type M600 Опознать микросхему

в форуме Ремонт блоков питания | Power supply repair

maxst83

11

5783

01 июн 2016, 16:04

Ale6ka Перейти к последнему сообщению

В этой теме нет новых непрочитанных сообщений. Lenovo ThinkCentre M600 (IBSWIH1) Нужен рабочий дамп

в форуме Lenovo IBM

bald

0

712

13 апр 2018, 02:10

bald Перейти к последнему сообщению

В этой теме нет новых непрочитанных сообщений. Toshiba Satellite M600 (NBQAA-LA-6072P REV:1.0) Нужна ЕС прошивка и биос

в форуме Toshiba

Zhanbolat

7

1261

07 фев 2021, 01:42

Zhanbolat Перейти к последнему сообщению

В этой теме нет новых непрочитанных сообщений. damaged 820-3209-A board

в форуме Apple

hondavtec

2

1235

25 авг 2015, 09:10

hondavtec Перейти к последнему сообщению

Эта тема закрыта, вы не можете редактировать и оставлять сообщения в ней. Lenovo b50-30 (la-b102p) kbc damaged

в форуме Lenovo IBM

scobay

2

1713

01 дек 2015, 19:33

siberian Перейти к последнему сообщению


Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 0


Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

Найти:
Перейти:  
cron