Forum Home
Press F1
 
Thread ID: 61793 2005-09-16 23:06:00 200GB seagate barracuda problems BlackNBlue (8897) Press F1
Post ID Timestamp Content User
388826 2005-09-26 22:45:00 Put both hard drives on Primary IDE, (one as master and the other slave) .

Whichever one has an operating system on it, put it as Master .

And connect an 80 wire IDE cable on Primary IDE .

If u have one (Its got a blue connection, on the motherboard end) .

And put the cds/dvd burner on secondary IDE (one as master one as slave) .

Hard drives and cd's/dvd's etc shouldnt go together on the same IDE connection .
Speedy Gonzales (78)
388827 2005-09-27 00:50:00 The most likely casue is the new ram. It is possible the system is freezing at post (detecting HDD) throwing off what the actual problem is. Also resetting is consistent with incompatible or bad ram.

First and most logical step is to remove the NEW ram and run it for a day (see if all is OK or not)

Eliminate the ram before you do anything else.
Battleneter (60)
388828 2005-09-27 10:49:00 Thanks for all your replies,



Hard drives and cd's/dvd's etc shouldnt go together on the same IDE connection .



Primary IDE
Master Drive - Maxtor 6Y120L0
Slave Drive - Seagate Barracuda ST3200822A
Secondary IDE
Master Drive - LG CD-ROM CRD-8400B
Slave Drive - ATAPI COMBO DC4801


Speedy G,

Maybe my post wasn't very clear, but that is exactly how my system is connected at the moment, both the CD drives are on secondary IDE and both my HD is on primary IDE .

What I don't understand is why my Barracuda drive is using PIO mode even though it was configured to use DMA if available . :illogical

Battleneter,

I didn't take the memory out but I did run memtest as suggested by Prescott, the memory passed all the test . :thumbs:

Another disaster this morning, woke up to a blue screen of death, claim that ftdisk . exe blah blah blah . . . . last thing I ran before I went to bed was the defragmenter . Couple with the blue screen is a beeping sound that I have never heard before, so I am not sure which part of the PC is beeping . . . . but everytime I hear the barracuda HD runs, the beeping goes away temporarily, and then back and off again . The beeping went away eventually but I have no idea what stopped it .

Took a few resets to get the PC to recognise the HD again, ran the memtest, then boot it up again, maybe I am getting paranoid but Windows is really slow . . . :groan:

I am very tempted to format my HD and start from scratch, I am thinking of purchasing a DVD burner to back up my crap before hand . Also, can I re-install the OS on my C drive but leave my partitoned drives alone and later retrieve the data?? I am guessing I could but I don't want to risk loosing my stuff without checking first . I currently have a dual boot (Debian Unstable MBR) set up on my PC, will I loose the MBR and need to reinstall my linux as well?

Sorry for the long post but I am at my wits end . . .

thanks in advance

BNB
BlackNBlue (8897)
388829 2005-09-28 09:21:00 Did a play around with my PC yesterday, it was slow as hell....then I check the IDE Advance Settings, for whatever reason, both my HD is now running on PIO mode when the first HD use to be running on Ultra DMA Mode 6!! So I risk it again and run defragmenter on my primary HD and now my PC is a lot faster, but I am still not sure why it dropped to PIO Mode.

One of my friend suggested to upgrade the BIOS, and when I check the MSI website, none of the fixes in the release notes has anything to do with HD detection and they did advice not to upgrade the BIOS unless absolutely necessary, so....should I?

I am at the brink of :badpc:
BlackNBlue (8897)
388830 2005-09-28 09:31:00 no dont update bios. Prescott (11)
388831 2005-12-17 03:44:00 DMA reverts to PIO (www.michna.com)

Good site. I used it when my DVD drive was on PIO and wouldn't let me change.

Make sure you follow the registry instructions carefully.
Agent_24 (57)
388832 2005-12-17 05:55:00 DMA reverts to PIO (www.michna.com)

Good site. I used it when my DVD drive was on PIO and wouldn't let me change.

Make sure you follow the registry instructions carefully.You will notice that link refers to Win 2000. Try it anyway as Win 2000 and Win XP are within the same family of Win O/Ss and share a few similarities.
As far as the RAM and memtest, memtest is far from 100% correct. Just coz memtest said the RAM is okay does NOT mean it is 100% ok. It does miss some errors. So it may still be the RAM

If you reformat, you will lose the loader for Debian (what does Debian use? Grub??). Just remount your root and reinstall grub (or what ever loader you are using).

I'm not sure the PSU is 100% reliable as well, try the other ideas (including taking out the new RAM).. if none of them work, you may be looking for a new PSU.
Myth (110)
388833 2005-12-17 08:25:00 I too have windows XP and that registry tweak worked fine for me. Agent_24 (57)
388834 2005-12-17 08:40:00 It is possible that the seagate and maxtor are not compatible, on the same IDE channel.
Try removing the drives from the secondary channel and put the seagate on the secondary, so you have only two hard drives in the system. If the seagate behaves itself, you may have an answer - but not the solution :illogical
wuppo (41)
388835 2006-01-15 02:31:00 Hi i also have a lot of HDDs and Partitions on my PC, which was running fine.
I needed more space and got a Seagate ST3200822A Barracuda 200GB.
My Setup was a 2 Maxtor Drives a DVDRW Drive and the Seagate.

I Fdisked the Seagate to 1X 80GB and 2 X 53GB Partitions. Only in Windows
XP the 3rd Partition would not format to NTFS, nor Fat32 the others Formated to Fat32, so i ran a windows ME boot Disk formated 3rd Partition in Dos to Fat32, then reformated in XP to NTFS, All was fine for a few days.
Then In Windows XP the 3rd Partition said drive not formated, so i tried
reformat, no luck again.

I did the whole format in Dos then in XP again and it worked but after a few days, it said Drive not formated, i looked in Disk Manager and noticed that the Seagate was shown as 137GB Drive?.

Also by now i noticed that all my devices ran in PIO mode and wont change.
I reformated Partition in Dos again but kept as Fat32, now Windows ME will see the Drive but XP says it is not formated and HDD is 137GB total?

After a while all the data on the 3rd Partition in ME became corupt, the 3 folders on there changed to 40 folders with funny characters as folder names and files, and said 350GB used, these folders could not be accessed or
deleted, so i formated again then after a week, same happened again.

I also noticed the HDD Making a noise like a train going over Rail Tracks, a tut tut, tut, tut sound.
This Disapears when 3rd Partition is removed or not formated.

What i have found out is the Seagate has isues with WinXP SP1, Win XP cant recognise Drive and sets it and all other Drives to PIO both in Win XP and ME. and Windows XP recognises Drive as 137GB, and as Drive is split to
80GB+53GB+53GB the 1st two Partitions come to 133GB, the 3rd 134GB-186
maybe suffers Problems as Windows XP cant read past 137GB.

This maybe what your having, try updating to Service Pack2 and /or see if Seagate have a Patch!

I will try these and fingers crossed this will fix problem!

Dave
BigDaveBear (8898)
1 2 3