New WD SATA II HDD Won't Format in XP

[Magnusfarce]

I have two new identical Western Digital WD2500KSRTL drives purchased to use
in a RAID 1 configuration. These are SATA II drives with a 16 meg cache. I
am using them with an Abit AN8 Fatal1ty SLI motherboard with appropriate
other hardware. My main (OS) drive is a 74 gig Raptor.

After many tries, I found that I could not get the RAID array to work, and
have now tested each of the two 250's separately on different SATA channels
with various cables. It is clear that one works fine, but the other
doesn't. It will not complete formatting in XP, but instead, hangs each
time at around 52 percent. I have tried formatting it on different SATA
channels and cables with no improvement. Interestingly, I tried a "quick"
format one time, and it seemed to work. The drive would accept file copies
and the files were uncorrupted. However, when I then tried to do a complete
format, it failed in the usual way. Keep in mind that its partner, an
identical drive, is working fine.

I assume that this will end up being a warrently replacement, but in the
meantime, any idea what's going on?

- Magnusfarce

 

[Bill D.]

I have two new identical Western Digital WD2500KSRTL drives purchased to use
in a RAID 1 configuration. These are SATA II drives with a 16 meg cache. I
am using them with an Abit AN8 Fatal1ty SLI motherboard with appropriate
other hardware. My main (OS) drive is a 74 gig Raptor.

After many tries, I found that I could not get the RAID array to work, and
have now tested each of the two 250's separately on different SATA channels
with various cables. It is clear that one works fine, but the other
doesn't. It will not complete formatting in XP, but instead, hangs each
time at around 52 percent. I have tried formatting it on different SATA
channels and cables with no improvement. Interestingly, I tried a "quick"
format one time, and it seemed to work. The drive would accept file copies
and the files were uncorrupted. However, when I then tried to do a complete
format, it failed in the usual way. Keep in mind that its partner, an
identical drive, is working fine.

I assume that this will end up being a warrently replacement, but in the
meantime, any idea what's going on?

- Magnusfarce

Heheh, yeah. It's DOA.

--
"ACK",
Bill D.
<><><><><><><><><><><><><><><><><><><><>
" Now just look..... they're burning the `Porta-Potties' "
........ OPUS

 

[KC Computers]

I have two new identical Western Digital WD2500KSRTL drives purchased to
use
in a RAID 1 configuration. These are SATA II drives with a 16 meg cache.
I
am using them with an Abit AN8 Fatal1ty SLI motherboard with appropriate
other hardware. My main (OS) drive is a 74 gig Raptor.
After many tries, I found that I could not get the RAID array to work, and
have now tested each of the two 250's separately on different SATA
channels
with various cables. It is clear that one works fine, but the other
doesn't. It will not complete formatting in XP, but instead, hangs each
time at around 52 percent. I have tried formatting it on different SATA
channels and cables with no improvement. Interestingly, I tried a "quick"
format one time, and it seemed to work. The drive would accept file
copies
and the files were uncorrupted. However, when I then tried to do a
complete
format, it failed in the usual way. Keep in mind that its partner, an
identical drive, is working fine.> I assume that this will end up being a
warrently replacement, but in the
meantime, any idea what's going on?

Sounds like the drive is bad and needs replacing. A quick format won't
catch all drive errors.

 

[Bill D.]

I have two new identical Western Digital WD2500KSRTL drives purchased to use
in a RAID 1 configuration. These are SATA II drives with a 16 meg cache. I
am using them with an Abit AN8 Fatal1ty SLI motherboard with appropriate
other hardware. My main (OS) drive is a 74 gig Raptor.

After many tries, I found that I could not get the RAID array to work, and
have now tested each of the two 250's separately on different SATA channels
with various cables. It is clear that one works fine, but the other
doesn't. It will not complete formatting in XP, but instead, hangs each
time at around 52 percent. I have tried formatting it on different SATA
channels and cables with no improvement. Interestingly, I tried a "quick"
format one time, and it seemed to work. The drive would accept file copies
and the files were uncorrupted. However, when I then tried to do a complete
format, it failed in the usual way. Keep in mind that its partner, an
identical drive, is working fine.

I assume that this will end up being a warrently replacement, but in the
meantime, any idea what's going on?

- Magnusfarce

Seriously, if you want to find out, use one of the utilities
found here.

http://support.wdc.com/download/index.asp?cxml=n



--
"ACK",
Bill D.
<><><><><><><><><><><><><><><><><><><><>
" Now just look..... they're burning the `Porta-Potties' "
........ OPUS

 

[Magnusfarce]

Thanks Fellas -

Just what I needed to confirm. I was pretty sure it was DOA, but wasn't
sure why it would work on a quick format, but still not be able to endure a
full format. Thanks for the help.

- Magnusfarce

 

[David Maynard]

I have two new identical Western Digital WD2500KSRTL drives purchased to use
in a RAID 1 configuration. These are SATA II drives with a 16 meg cache. I
am using them with an Abit AN8 Fatal1ty SLI motherboard with appropriate
other hardware. My main (OS) drive is a 74 gig Raptor.

After many tries, I found that I could not get the RAID array to work, and
have now tested each of the two 250's separately on different SATA channels
with various cables. It is clear that one works fine, but the other
doesn't. It will not complete formatting in XP, but instead, hangs each
time at around 52 percent.

Bad drive.

I have tried formatting it on different SATA
channels and cables with no improvement. Interestingly, I tried a "quick"
format one time, and it seemed to work.

"Seemed" is the correct word. A "quick format" assumes the drive is good
and simply writes a new directory structure to it, that's why it's 'quick',
so as long as those few tracks are ok it "seems" to work.