[Spann]

Ok. Installed a brand spanking new 60GB Maxtor HD the other day to go with the 120GB Maxtor I've already got (They're the same drives, just one's twice the size)

Anyway, whenever I try to copy significant amounts of data to/from it, my system restarts itself.

Any ideas? Both drives are formatted in FAT32, with XP+SP2 installed on the 120GB.

I'm hoping for something more concrete than "*SUCKS TEETH*Nah, It's fucked, mate."

What's wierd is that then when chkdsk rears it's ugly head it doesn't want to check the drive that is almost certainly causing the problem.

Big billy bollocks. Any help is appreciated.

This post has been edited by Spann: 13 August 2007 - 07:48 PM

[Bond]

Erm... Ad-Aware?

[Deepsycher]

When it restarts does it just reboot from post?
Do you hear the drive power down?

[Spann]

I know its spy/ad/malware clean, as it's spanking new, and that machine isn't connected to the net, never has been. Well some bits of it have, but if virii are in monitors now, this isn't a world I want to live in.

DEEP - It boots from where it checks my RAM, right at startup. It's literally:

Windows on, copying files - Monitor Blinks - Machine is checking RAM again in DOS

The HD doesnt have chance to power down.

EDIT:Deep Ninja'd me.

This post has been edited by Spann: 13 August 2007 - 08:06 PM

[Deepsycher]

I would check the power cables going to the hard disk by toggling them near the connector to see if it powers down. I'll explain about the problem I found in many situations I experienced after.

First of all to check the voltages in the bios setup to see if they match 3.3 volts, 5 volts and 12 volts.

This post has been edited by Deepsycher: 13 August 2007 - 08:21 PM

[Spann]

Thanks Deep, I'll try that.

[Bond]

If users were dairy, Deep would be the Big Cheese...

Or something like that.

[Chefelf]

Go to Start=>Control Panel
Open System Properties.
When System Properties appears, click the Advanced tab.
Under Startup and Recovery click Settings.
Uncheck Automatically restart under System Failure.
Click OK.

See if that stops the rebooting problem.

[Deepsycher]

From the information I didn't think it got up to that point.
I would check the system logs.

Also stating what other hardware or specification you have might help provide a detailed insight and some ideas on what could be the problem.

Does the drive have an IDE or SATA interface?

If it is an IDE drive and you haven't done this yet try connecting it to the second channel alone and transfer that significant amount of data to see if that works. Just as an attempt to rule out other things.

This post has been edited by Deepsycher: 13 August 2007 - 09:54 PM

[Bond]

Um...

I have no idea what you just said, but you sound so cool saying it...

[Spann]

I'll be honest with you - I don't know too much about hard drives.

http://www.superware...Y120P0/p/193160

But thats what they are (that page takes you to the 120gb, the 60gb's product code is 6Y060P0.)

EDIT: Brackets.

This post has been edited by Spann: 14 August 2007 - 06:42 AM

[Deepsycher]

That would be an IDE drive.

Just to check, I don't know where you connected the drive, I mean if it is on the same cable as the first hard disk which would be the first channel. You could try connecting it to the second channel with nothing else connected. Usually I see that CD/DVD devices are connected to the second channel.

Then try that large transfer to make sure that it is or is not the first channel or the jumper configuration of the first drive alone.

Also I mean't some specifications might help like the name of the motherboard and the name of the power supply. Also did you check you voltage readings within the bios setup and the molex power plug to the drive to see if it spins down?

This post has been edited by Deepsycher: 14 August 2007 - 08:28 AM

[David-kyo]

You might need one of them PCI cards that make IDE drivers compatible with SATA systems, if nothing else works. You'll spare a lot of frustrating wire-plugging fuckabout as well.

Bond, if you haven't got anything worthwhile to say, then stfu already.

This post has been edited by David-kyo: 14 August 2007 - 10:59 AM

[Bond]

Okily-dokily, neighbor-ino!

[Radu094]

I know it's not related (or helpful), but FAT32? Why are you still using FAT32?

On a more helpful note:

Did you try to force a chkdsk on the new HDD? If it doesn't want to even test the disk, then it's not a connection problem. It's a HDD electronics or physical failure.

In the device manager, do you see the HDD installed and recognized properly? ie. 6Y060P0 ?
If you don't then it might be a problem not w/ HDD but with cables, power connectors, motherboard.. even windows installation.