"webpa" wrote in message
ups.com...
On Oct 29, 12:02 pm, Meat Plow wrote:
On Mon, 29 Oct 2007 14:17:01 -0400, PeterD wrote:
On Mon, 29 Oct 2007 08:26:59 -0700, SCIENCE
wrote:

i want that PCB of 160 GB Seagate Hard Disk in
order to replace the burnt one . Can you help me ? where do
i get that
PCB ? Please............

Not an option, there is information about the drive
platters, heads,
etc, stored on NVRAM on the card. Any other card won't hve
the right
information.

Why not if the heads and the platters are the same which they
should be in
an identical drive. Critical data is stored on an engineering
track on the
media itself, not nvram.

Any specific drive is never generic. It, and all others made
in the
same batch, with exactly the same hardware, were caused to scan
themselves and note each bad physical spot on each platter. The
number
of such spots is sometimes zero, more often not. Depending on
the
specific manufacturer, this info is stored in NVRam on the PCB
(possibly on the disk itself, somewhere, as well). The bad
physical
spots are mapped-around in the drive's firmware so that normal
disk I-
O does not attempt to use them.

The (**VERY**) expensive data recovery services have created
hardware
and software capable of getting around these drive-unique
characteristics for possibly thousands of sets of drive
hardware (and
production block changes). That is why they are expensive. It
may be
worth your time to substitute a new drive PCB and try it...but
don't
get your hopes up.


if moving the nvram from old drive pcb to new pcb does not work
then ...

Is is not possible to reset the nvram on the new card so that it
thinks there are no bad spots ( a fresh and clean drive so to
speak )

AFAIK
since the disk layout information is FileSys info on the drive,
put there by operating system then the OS should not send a
request to access a spot on drive that is actually bad ? just
access spots where it knows the data was placed ? any READ errors
could handle by OS (slow things up a bit)

only trouble i suppose would be trying to write new data then
there would be trouble (using nvram clear) but i am hoping the OP
only wants to recover (ie READ) the DATA to a new drive ???? yes
???? and NOT planning to BOOT from this drive either ???

m2c
robb