hard drive probs..

  • Thread starter Thread starter mojo
  • Start date Start date
M

mojo

Apologies for the multi post.

This is driving me nuts. I was running win2k - primary hd (seagate) was
20gig, secondary (maxtor) 200gig with about 100gig of data. When all was
running well, the original seagate drive - with OS - had jumpers set to CS;
and so did the secondary. The seagate HD got knackered. so, i shoved in a
replacement HD (20 gig western digital), installed new win2k again only now,
the second drive isn't being recognised. under 'disk management' it says
something like the drive is unreadable or damaged and that this is a
'dynamic' drive whereas the primary drive is 'basic'. the old seagate
primary was also basic so i'd have thought this made no difference in case
there's a compatibility issue or something. messed around like crazy with
jumper settings (went to both drive manufacturer sites and got all
docs/settings) and the best i can get is the second drive being picked up as
'basic' but only when i set the jumper to 'Slave with CLJ'. however, even
when it does come up in my computer, only 31.5gig is seen. I can't access
this drive because i'm told the drive is unformatted! aargh! someone help,
please!!!!!!!!! tia. mojo
 
Gary said:
What "second drive"? Are you saying you left the bad one connected?

Note that there is a registry setting you need to set manually (I have
no real idea why MS left this "booby trap" in) to allow support of
very large drives (>127GB). Failure to set this will cause the OS to
overwrite system areas of the disk, making it unbootable. Search for:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi\Parameters

and set EnableBigLBA to 1.

Then reboot. There is no way to recover a disk damaged by that
problem.




The drive is probably OK physically, but the data structures on it
have been corrupted. It will need to be completely reformatted (just
like anew drive would).




What is "CLJ"? Could that be "Cylinder Limitation Jumper"?




Sounds like you're using a jumper that limits drive capacity, for use
with older systems that couldn't handle drives larger than 32 GB.
Since you have larger drives before, your system must not be so
limited, and you should have no need of this jumper.
Click to expand...


while i am no expert at it, i had a problem with having large partitions
and not having set the registry correctly. one sunny day all my
partitions disapeared and i was asked if i wanted to format the drive
(with my data on it). i was then able to recover all my data using the
following tools:

- check http://www.48bitlba.com/enablebiglbatool.htm for a tool to set
the registry flag to enable big LBA

- i then used test disk to search, and repair all my partitions. i can't
actually remember the steps but i think the manual gives some
instructions on how to do it. i followed the instructions on
http://www.computerbase.de/forum/showthread.php?t=110869 to recover my
data.

(http://www.cgsecurity.org//index.html?testdisk.html)

if in dire need, post again and i'll try to find the time to translate
some if it.

HTH,

T
 
Rather than using CS try the Master / Slave jumpering setup. I have
used that with WD drives for years with no problems but each time CS was
tried, years ago, problems came up similar to yours. The OS drive
should be Master with the Data drive as Slave.

James
 
Back
Top