Installed New WD SE Hard drive - File Name error and slow

[mark]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

I just installed a newWD Caviar SE WD2000 JB 200G hard drive. All my
NTFS partitions have a Partition Magic error 1611 -BAD FILE NAME
error. My FAT32 partitions are fine. I used initially Partition
Magic and 1/2 NTFS had the same error, now I used WD drive utility and
all but the FAT32 have file error messages. My cluster sizes are 4K.

Also, the drive is running really slow. I have a ECS PVMM2
motherboard with one UDMA 100 IDE slot. I have the WD hard drive
piggy backing as slave. I am wondering if that is why it is slow. HD
Tach shows the speed of 16MB/second while my other Maxtor drive is 53
MB.sec

What have I done wrong?

Thanks

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

On Thu, 06 Jan 2005 07:52:57 GMT, "Mark" <none@none.com> wrote:

>I just installed a newWD Caviar SE WD2000 JB 200G hard drive. All my
>NTFS partitions have a Partition Magic error 1611 -BAD FILE NAME
>error. My FAT32 partitions are fine. I used initially Partition
>Magic and 1/2 NTFS had the same error, now I used WD drive utility and
>all but the FAT32 have file error messages. My cluster sizes are 4K.
>
>Also, the drive is running really slow. I have a ECS PVMM2
>motherboard with one UDMA 100 IDE slot. I have the WD hard drive
>piggy backing as slave. I am wondering if that is why it is slow. HD
>Tach shows the speed of 16MB/second while my other Maxtor drive is 53
>MB.sec
>
>What have I done wrong?
>
>Thanks

They have a version of HD Tach for BeOS now? Amazing!

--
Michael Cecil
http://home.comcast.net/~macecil/

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

Michael Cecil wrote:

> On Thu, 06 Jan 2005 07:52:57 GMT, "Mark" <none@none.com> wrote:
>
>>I just installed a newWD Caviar SE WD2000 JB 200G hard drive. All my
>>NTFS partitions have a Partition Magic error 1611 -BAD FILE NAME
>>error. My FAT32 partitions are fine. I used initially Partition
>>Magic and 1/2 NTFS had the same error, now I used WD drive utility and
>>all but the FAT32 have file error messages. My cluster sizes are 4K.
>>
>>Also, the drive is running really slow. I have a ECS PVMM2
>>motherboard with one UDMA 100 IDE slot. I have the WD hard drive
>>piggy backing as slave. I am wondering if that is why it is slow. HD
>>Tach shows the speed of 16MB/second while my other Maxtor drive is 53
>>MB.sec
>>
>>What have I done wrong?
>>
>>Thanks
>
> They have a version of HD Tach for BeOS now? Amazing!

Have I missed a post somewhere? Who said anything about BeOS?

--
--John
Reply to jclarke at ae tee tee global dot net
(was jclarke at eye bee em dot net)

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

On Thu, 06 Jan 2005 15:41:18 -0500, "J. Clarke" <jclarke@nospam.invalid>
wrote:

>Michael Cecil wrote:
>
>> On Thu, 06 Jan 2005 07:52:57 GMT, "Mark" <none@none.com> wrote:
>>
>>>I just installed a newWD Caviar SE WD2000 JB 200G hard drive. All my
>>>NTFS partitions have a Partition Magic error 1611 -BAD FILE NAME
>>>error. My FAT32 partitions are fine. I used initially Partition
>>>Magic and 1/2 NTFS had the same error, now I used WD drive utility and
>>>all but the FAT32 have file error messages. My cluster sizes are 4K.
>>>
>>>Also, the drive is running really slow. I have a ECS PVMM2
>>>motherboard with one UDMA 100 IDE slot. I have the WD hard drive
>>>piggy backing as slave. I am wondering if that is why it is slow. HD
>>>Tach shows the speed of 16MB/second while my other Maxtor drive is 53
>>>MB.sec
>>>
>>>What have I done wrong?
>>>
>>>Thanks
>>
>> They have a version of HD Tach for BeOS now? Amazing!
>
>Have I missed a post somewhere? Who said anything about BeOS?

Exactly. Who said anything about the operating system?
You cannot just plop a large drive into any OS and necessarily expect it
to work.

--
Michael Cecil
http://home.comcast.net/~macecil/

 

[Guest]

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

1) make sure the jumpers are correctly installed on both drives.

2) run WDDiag (free from WD) on this drive first. make sure there are
no HD problems.

3) make sure Windows is running the drive in UDMA mode (device mgr).

4) make sure you have no viruses

5) make sure you have no trojans

6) make sure you are using a UDMA/66 or higher approved IDE cable (80
wires, not 40 wires).