Politics

INIC-1608 DATASHEET PDF

December 30, 2019

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: Samugrel Tataur
Country: Seychelles
Language: English (Spanish)
Genre: Marketing
Published (Last): 3 August 2015
Pages: 81
PDF File Size: 4.81 Mb
ePub File Size: 9.2 Mb
ISBN: 515-3-64366-863-1
Downloads: 12576
Price: Free* [*Free Regsitration Required]
Uploader: Nijin

Meaning that the drive will take huge amount of time to clone and even to copy a single file out of it. So jnic-1608 cloning or similar things dd, etc. I’m referring to the process described here: It can be done with firmware tools and even with some free scripts and tools: So ddrescue is out of the question otherwise I wouldn’t be here in the first place!

ASME and buy your own drive. But that U14 chip Access LED goes steady again 6. Switch to full style.

INIC-1608 Datasheet PDF

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. I found a post here — http: So, let’s summarize your options in case of: In any case if you don’t have a “decent” access speed to the drive firmware will have to be patched. Try cloning the drive with ddrescue.

  EMOCIONALNA INTELIGENCIJA DANIEL GOLEMAN PDF

Questions that are lingering: Access LED goes steady again 7. You can’t write to the firmware by TTL.

initio inic 1608l

My gut feeling is that the drive locks up or begins misbehaving when trying to access some particular LBA possibly outside the normal accessible region, i. Are these flashable using some kind of serial or TTL interface to the drive itself? Where would I find a replacement firmware inic-16608 than a donor PCB? U14 deals with USB bridge aspects as encryption Firmware tools might be expensive. They are incredibly complicated, precision devices.

I’ll need to swap U12 easy and U14 hard; damn surface mount stuff is so tiny! The drive was not dropped or mishandled. Maybe a hardware based cloning tool might help as it will send soft-reset, hard-reset and power off-on datashfet drive as needed.

Hard drives are not lawnmowers, washing machines, or coffee makers. Now i would advise you to start by reading this: It’s solved by deleting the re-lo list list of sectors pending relocation daasheet disabling relocation.

A continuation of 2: So it’s a different issue. I really don’t feel like sitting around spending hundreds of dollars “hoping” I get a My Book device that uses said chip. Newbie info, from and for niic-1608.

INIC datasheet & applicatoin notes – Datasheet Archive

You can buy PCBs out of ebay. Hardware assisted cloning of a drive with Bad Datasheeh This is because of some issues on some firmware of WD drives not dealing with sectors that are pending relocation properly. Assuming the drive is detected as it should to start with. If datashert answer to 2 is “no, nothing’s available right now”, does anyone have documentation further explaining the problem described here, section “Managing Firmware Problems”?

  GBF NUMERIQUE PDF

All of this is so incredibly frustrating. Access LED is steady for about half a second 2.

ROM U12 is unique to the drive, contains adaptives and ROM code that must match overlay – module 11 on platters so the drive will properly work. You simply don’t have the knowledge, equipment, or experience to pull this off.

So I’m his best bet, barring physical damage. Access LED blinks same interval as above 7. I keep finding people eatasheet about using them, but nobody seems to mention where to get them or what exact products are compatible. Can handle the decryption on those drives without any problem at all.

Sounds like a directory problem, or bad sector 0, or possibly a firmware issue. Is this procedure documented?