INIC Initio Corporation. 1. INIC USB to SATA Bridge. Specification. Version August 10, Initio Corporation. INIC initio datasheet pdf data sheet FREE Datasheets (data sheet) search for integrated circuits (ic), semiconductors and other electronic components such . inic, USB to SATA Bridge Overview The INIC provides an advanced solution to connect SATA devices to w,

Author: Nijinn Kigakasa
Country: Philippines
Language: English (Spanish)
Genre: Technology
Published (Last): 5 December 2008
Pages: 52
PDF File Size: 6.48 Mb
ePub File Size: 7.49 Mb
ISBN: 259-6-99135-900-8
Downloads: 19740
Price: Free* [*Free Regsitration Required]
Uploader: Doll

I’m referring to the process described here: Meaning that the drive will take huge amount of time to clone and even to copy a single file out of it. If the answer to 2 is “no, nothing’s available right now”, inic-16008 anyone have documentation further explaining the problem described here, section “Managing Firmware Problems”?

Datasheets search archive of electronic components datasheets

Can handle the decryption on those drives without any problem at all. It’s solved by deleting the re-lo list list of sectors pending relocation and disabling relocation. The drive was not dropped or mishandled. Your original board is You can buy PCBs out of ebay.

Assuming the drive is detected as it inkc-1608 to start with. Try cloning the drive with ddrescue.

INIC – INITIO – IC Chips – Kynix Semiconductor

Test it first by reading a few sectors at random places — start, middle, end. So drive cloning or similar things dd, etc. So, let’s summarize your options in case of: After about 45 full seconds or so, 4 happens, rinse lather repeat Questions that are lingering: So I’m his best bet, barring physical damage.


Switch to full style. Now i would advise you to start by reading this: You can’t write to the firmware by TTL. I found a post here — http: Hardware assisted cloning of a drive with Bad Sectors: So it’s a different issue.

The SMART data I can understand fully trust me — been doing this part of it for about 15 years now, quite familiar with ATA protocol as well and see absolutely no anomalies, so I’m left thinking there is something more nefarious going on.

A continuation of 2: Are these flashable using some kind of serial or TTL interface to the drive itself? ROM U12 is unique to datasheft drive, contains adaptives and ROM code that must match overlay – module 11 on platters so the drive will properly work.

Drive spins up 3. ASME and buy your own drive.

Initio Corporation – INIC

Hard drives are not lawnmowers, washing machines, or coffee makers. But that U14 chip It can be done with firmware tools and even with some free scripts and tools: I don’t like power-cycling drives repeatedly I shouldn’t have to explain why, you guys understand.

Maybe a hardware based cloning tool might help as it will send soft-reset, hard-reset and power off-on the drive as needed. Where would I find a replacement firmware other than a donor PCB? Hi folks, thought I’d post a current status update on this recovery project. The access LED interval also sometimes varies.


Firmware tools might be expensive. I really don’t feel like sitting around spending hundreds of dollars “hoping” I get a My Book device that uses said chip.

Looking for advice on what to do. I’ll need to swap U12 easy and U14 hard; damn surface mount stuff is so tiny! In any case if you don’t have a “decent” access speed to the drive firmware will have to be patched.

A colleague sent this drive to me. I keep finding people talking about using them, but nobody seems to mention where to get them or what exact products are compatible. My gut feeling is that the drive locks up or begins misbehaving when trying to access some particular LBA possibly outside the normal accessible inic-168, i.

Cheapest available option might be WDMarvell. You do not have dataasheet required permissions to view the files attached datssheet this post. So ddrescue is out of the question otherwise I wouldn’t be here in the first place! Access LED goes steady again 7. This is because of some issues on some firmware of WD drives not dealing with sectors that are pending relocation properly. You simply don’t have the knowledge, equipment, or experience to pull this off.