Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Seagate ST3160023A here and gone

Status
Not open for further replies.

Naro

Technical User
Sep 4, 2003
38
US
Installed as second HD, Cable Select, initialized, formatted, operating properly, data transfered to the drive.
Then.. let it run 24hrs, then shutdown.
NOW. PC (eMachineT3092) with XP2 will not boot as long as the new HD is in. Remove the second HD, and boots up fine. plug the data and power back in on the second HD and the system won't boot. Period. Bios error messages only that OS can't be found... insert Windows startup disk. Which I didn't do.
.....This drive is in warranty (3 days old). Do you think I have a hardware failure, and should I return it? I don't know what else to try: cable was fine. And I even swapped in a known-good cable. No luck.
 
Naro,

See this thread

thread751-1170231

Set it to slave at the middle connector boot insure it is master. Should be good to go.

Hope this helps

rvnguy
"I know everything..I just can't remember it all
 
Thanks rvnguy, but no luck. I've tried, and it doesn't matter whether it's jumpered to Slave, to Cable Select, or if it is moved to the Primary position on the cable. The drive seems broken. The stepper-motor clacks and clacks LOUDLY.. but OS finds no HD. That HD can't be seen thru the network, or with a floppy boot disk either.

I really believe the drive is broken.... it didn't survive the 24hr "burn in".
 
Do both drives ID correctly in BIOS? Together? Separately?
Since it worked at the beginning and now doesn't it appears a victim of infant mortality.

Ed Fair
Give the wrong symptoms, get the wrong solutions.
 
The new HD doesn't ID in BIOS. I'm sure enough now that this is "infant mortality" (thanks, edfair) that my next step is to Seagate Warranty return.

That raises another darn problem though. There is confidential and legally protected data on that dead HD, and I really should degauss it. Of course, if I do, I can't expect Seagate to honor their warranty. All-in-all, it looks like I may have to just walk away from the $$ I spent on the new drive.. and start again.

Thanks for your ideas, gang.
 
Seagate DiskWizard contains a utility that will zero fill a drive. You can download a bootable floppy or CD version from their website. It should erase the drive making it safe to return to Seagate, and may even fix whatever problem you are having with it.

I have used their zero fill a couple of times where a drive was so corrupted that chkdsk and fixmbr wouldn't run. I couldn't even install a Ghost2k3 image.
 
Thanks frank4d. I had thought of that. But...
NOTHING sees that drive! Seagate's tools and diagnostics don't. DOS boot disks don't.

Heck, I don't know why I'm worrying about sensitive data. I bet it would take a dedicated lab pulling the drive apart to access the data. That drive is BROKE!
 
I can't even imagine that they would spend any time looking at the contents.
Suspect that it will be all automated except for the board replacement. If they even try to refurb it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top