Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[ZDev]

Specs: Win7 x64 ASUS P8Z68-V PRO/GEN3 Intel Core i7-2600K G.SKILL ECO 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Crucial M4 CT064M4SSD2 2.5" 64GB SSD Seagate Barracuda ST1000DM003 Coolermaster 800W PSU The drive is not being detected in BIOS/Windows on cold boot. Will also not be detected on a warm boot after the first cold boot. The only way that the drive is detected is when the PC is powered down then back up after the first cold boot. I have tried changing SATA cables/ports and that does not appear to be the issue. I have run Seatools/Check Disk and the drive has checked out OK. Any ideas?

[eTrips]

Hey,

I have the same issue!

I purchased 3 ST1000DM003 for my storage array (Raid 5).

I discovered this as I was just building the machine (obviously booting it cold several times). One of the 3 ST1000DM003 Drives fails to be detected on 1 of every 5 boots, and consistently on cold boots.

I swapped all the cables and mobo sata ports and troubleshoot it; It is only happening on the one drive.

I returned the drive for another ST1000DM003 and got back up and running; soon after the new drive (and only the new drive) started doing this again and my raid array degraded. I thought I had ruled out mobo and power issues...

My plan is to try another drive but if this is a know issue I will perhaps consider an alternative to the ST1000DM003 model.

Anyone else have info/thoughts on this?

Thanks!

Computer Specs:

Crucial 128GB SSD

3x ST1000DM003

Asus Ramp Extreme 4 LGA2011 w/ i7 3960k

Asus GTX590

16GB Ram

1000W PS

Blu Ray DVD ROM

[ZDev]

More info: I have only been able to reproduce this on a cold boot when the machine has been disconnected from power for an extended period (~1 day). Temperature does not seem to be a factor because when the machine is warm booted the drive is still not detected. I can see if there is a difference if I wait for an extended period (half-hour or so) before performing the warm boot. The only way the drive will be detected is by powering down the machine then powering back up. I have not experienced this issue with the SSD or an additional SATA II HD drive. Once the drive is detected it is still detected on subsequent warm boots and cold boots within intervals of a couple of minutes. I am in the process of obtaining a different drive and new SATA cables and will see if I can reproduce the issue with the new drive.

[MapleTree]

Hello,

I would double check to see if there are any firmware updates for your drive. You can check that on this link by entering the serial and the model number of your drive.

http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931&NewLang=en

Let us know if you have any other questions.

[ZDev]

Thanks for the reply MapleTree. I have run the Download Finder/DriveDetect utility and have found no firmware updates. I believe this is a fairly new drive so I wouldn't expect there to be any firmware updates yet.

[eTrips]

Update: Just got another replacement ST1000DM003 So far so good, I am not experiencing the cold boot issue from before but I am getting the occasional single thrash. My disks are in RAID 5 and the array has not degraded as it was before but overall these drives seem to have issues. Hopefully Seagate releases some firmware update at a later time can correct this or I'm going to replace them all (Grrr). Anyone else having problems with this drive model?

[Cantbecanit]

@ eTrips.

You have the wrong drives

http://www.seagate.com/docs/pdf/whitepaper/mb578_7200_drive_specification_comparison.pdf

Raid 0 or 1, you need a higher class drive for Raid 5 mate, hth.

[eTrips]

@Cantbecanit Appreciated, However I can report that these drives work quite well in RAID 5 (for me anyways). The only issue I experienced was on cold booting which happened whether or not it was part of the array. Could that document be out of date? Thx

[Cantbecanit]

Yeah they may well work, but so does a car @ 9000 RPM for a little while, if you get my drift, I'd drop Raid levels myself, but good luck with it in future, it may stay ok for you.

[ZDev]

OK, I have replaced cables, etc.. and installed a different drive (not the same model) and am not having issues with it although still having issues with the original drive. The actual disk itself seems OK since it passes all SeaTools tests but it appears that this might be some type of firmware issue. I would like to send this drive back to Seagate under the warranty but am concerned it will be rejected because I don't have a SeaTools code. Does anyone have advice as to what I should do now?

[Cantbecanit]

Dev, if you can get it loaded to another O/S installed drive, simply format it in disk management, I think all you've got missing is the sata driver, if it's in Windows at all a format there should sort that for you.

[ZDev]

The drive is not detected in BIOS when the system is started. When it is detected in BIOS Windows detects it fine. The OS is not on this drive, it is on the SSD.

[FredSoDak]

I have the same problem here; on a cold boot, the ST1000DM003 is not detected by the AHCI bios version 0001.0075 on the ASRock M3A770DE motherboard.  When it was first installed, it worked fine, then the problem gradually got worse over the course of the weekend.  It has only been in the computer for 3 days.  The drive is setup in the bios in AHCI mode; if I choose IDE or RAID mode, the display will just black out the screen and freeze the boot process entirely, forcing a power down & disconnect of the drive.  When the bios is in AHCI mode, it will pause until the detection timeout period expires, then the boot process will continue without the drive being detected.

[Sonick]

Almost same issue here on this configuration:

Core i5 2500k,

2 x 4 GB Corsair Vengeance 1866 MHz,

ATi Radeon 6970, 2 GB RAM,

AsRock Extreme 4 Gen3

1xSSD Corsair F60 (for Windows 7 x64)

1xST1000DM003 (for my stuff)

First happened when I was playing (my games are installed on the HDD). Game freezed, then exited, then I noticed in Windows there was no HDD drive detected. Did a cold restart, BIOS did not detect it.

It detects the drive only if I reset the BIOS settings or cold reboot the PC.

At first, both the SSD and the HDD were connected to SATA-3 ports. I've connected the SSD to the SATA-2 port since it's a SATA-2 SSD. HDD is connected to the SATA-3 port where the SSD was.

No failure yet. Will get back on this if the issue happens again.

[Cantbecanit]

No code, no rma, try Sentinal, if the health or report page shows bad sectors then it's not long for this world, if it doesn't it's your congiuration doing it, hth.

[Sonick]

Model ID: ST1000DM003-9YN162

Serial Number: [ Edited to comply with forum guidelines ]

Revision: CC46

Some weird thing is that the size of the buffer is reported as "unknown" by every app that I used for getting HDD info.

Tested with Seagate Tools (thorough test) and no error found.

[ZDev]

OK, after trial and error I have identified a situation where it seems to be detected at every boot. When I power down my machine I always turn off the PSU and the UPS (not sure if this matters, might be sufficient to just turn off one or the other). If I turn on the UPS then switch on the PSU then WAIT for some amount of time THEN power on the PC it seems to always be detected. I have not yet determined what amount of time is sufficient but I give it 30 seconds to a minute. Would be interested if someone has some insight as to why this might be.

[wing0809]

i also have the same problem

my computer was just built for one week

the new hard drive could be recognized in bios and windows at the beginning

but at the third day, the hard drive cannot be detected in the bios and windows on cold boot and warm boot too.

every time i power off the computer and turn off PSU

the new hard drive cannot be recognized.

i tried to use differenct sata ports and cables, but it cannot help.

the way the drive can be detected only is that i plug the sata cable in the new hard drive before the computer start

if the new hard drive is detected, it performs well.

and it passed short and long test of seatools

is the firmware problem or the hard drive is defective??

how can i solve this issue??

my computer config:

cpu intel i5 2400

motherboard asus H61-MPro

Power supply antec EA430W

ram corsair ddr3 4G

hard drive seagate st1000dm003

                 wd sata 2 320GB (old hard drive)

os windows xp sp2

[Ganther]

I am also having the same issue.. I have a ST1000DM003-9YN162 connected to the grey sata3 6g port and in the bios the controller is set to AHCI.

On cold boot or even a restart the drive is not detected by the bios.I have to power down the PC reseat the power and sata cable and power on and keep repeating until the drive is recognized.

I thought at first it could be an MB issue, so I returned the Asus P8H67-V board and upgraded to the Asus P8P67 Rev B3 and updated the firmware to the latest. I am getting the same issue during a cold boot or even a restart the hard drive is not recognized by the bios. I have tried swapping ports, and cables makes no difference. 

firmware revision on the drive is cc46 I could not find a new one.

Does anyone have a solution for this issue.

[Sonick]

Since my last post the issue is somewhat gone. On warm reboot, once, it did hang up for a minute or so. I had the PC turned off (PSU power button was on) and when I powered up the machine it hanged for about a minute in the BIOS screen, just before showing the connected drives. It detected the drives successfully and carried on with the boot process.

Question for the others: can you get the correct buffer size for this drive ? Because I get Unknown in every app I try.

[wing0809]

I use hdtune pro v.5.0

the buffer is shown n/a

[Sonick]

So it seems like a general issue with the buffer being not reported.

[wing0809]

http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=223651&NewLang=en&Hilite=ST1000DM...

seagate has released the updated firmware.

if i update the firmware, Could this issue be solved??

[Sonick]

Thank you Seagate for this update though I can't find a changelog or something.

I've updated my firmware successfully and tested with a few cold an warm reboots. For the moment everything is stable. Buffer size still reported 'unknown'.

[galenagolfer]

I have the identical issue.  I have 2 ST1000DM003 drives, firmware version CC46 in Raid 1 mode running on Windows 7 64-bit Home Premium Edition on a Gigabyte GA-A75-UD4H motherboard bios release F7, AMD A8-3870K APU, PNY (2x4GB) DDR3 1600 (PC3 12800), Antec 500W PSU (EA-500D).  One of the drives failed and causes the raid array to go CRITICAL.  Its so bad that the disk controller fails and the physical drive won't show up in RaidXpert.  This happened after the computer was totally off overnight with the power supply off and the plug out of the power supply. As was stated earlier in this thread, after a couple of boots, the drive amazingly reappears and can then rebuild the raid array.  The Seagate Drive Detect software didn't work on a raided disk set.  It won't see each individual drive.  So the firmware update utility won't run in WIndows either.  I burned the ISO CD image and tried to boot and run from that and that failed also.  I changed the bios to ACHI and tried to run again and that didn't work either.  SInce this was a new computer I was building, I took the drives to my old computer and hooked them up there one at a time and used (booted from) the ISO disk there and it did update the firmware on each drive.  If you are running in non-Raid mode, I think you should be able to run it on your computer without using another computer.  I then powered down for 7 hours and the Raid array is still functional.  So the firmware upgrade may do the trick.  I will be powered down for 12 hours and then another instance for a day and I will report back.  If that's the case, I think I am done.  I now have 2 drives running in Raid1 mode with a  firmware version of CC4C.   

[galenagolfer]

The firmware upgrade definitely solved my issue.  The array has not gone done since I upgraded it and the computer has been shudown and unplugged for extended periods of time.

[Sonick]

I got problems again here even with CC4C firmware version. Everything was good for a few days after the update of firmware, then I got a bluescreen when I wanted to restart Windows. I didn't pay attention and tried to play a game (installed on ST1000DM003). Sound and image frozed during gameplay, then bluescreen and reboot. Another bluescreen and reboot when I was listening to music from this HDD. Scanned for bad sectors and problems with windows' check disk and nothing found. There were no power problems in my area, no fluctuations.

Bluescreen occured even when I was trying to post this - which is kinda funny. Every component in my system is brand new, latest drivers are installed for all except video card, windows is fully updated. Tried a CMOS reset, no results, I got blue screens out of nowhere. I am very frustrated over this issue, I will disconnect the Seagate drive and run only on SSD for a while to see if it still occurs.

Anyone else who updated the firmware has these issues ?

[Cantbecanit]

If this is a raid problem, check you are not above Raid 1, otherwise the drives aren't supported in higher raid configs.

[Sonick]

I don't have a RAID configuration. Just one SSD for OS and the Seagate drive for other stuff, set in AHCI mode.

Last night I had no issue, no blue screen. I am totally confused about the cause of this.

[Cantbecanit]

THB it's highly unlikely the HDD is causing blue screens, it's normally a bad psu or heat issue, if you are running failsafe monitoring at say 80 degrees for the cpu and the cpu hits 85 you will find the pc will either simply freeze up of blue screen on you.

[Sonick]

It's not a heating problem. Case is a CoolerMaster HAF 912 Plus with all the coolers installed and running, except for the top one. Airflow is good and also the temperatures.

A new thing happened.. now after the blue screen it doesn't detect the SSD drive. I must shutdown and turn off the PSU power button to detect it again.

So maybe it's the PSU or the mainboard. Can there be anything else ?

[Sonick]

Checked for variations of voltage on the PSU HDD cable. Everything nice and stable when I did the measurement.

Went for a BIOS downgrade and now I'm waiting to see if it fails again. Hope not.

[Sonick]

I think the BIOS downgrade solved the issue. No more blue screens and misterious dissapearences of HDD or SSD. I've bought another Seagate drive, identical to the one I had, did the firmware upgrade and have them both in RAID 0. I'm a happy camper now

[knightwing24]

Just remove the CMOS battery...Boot without the Battery...

[dallas118]

Hi guys...apologies for ressurecting this thread.

I bought a ST1000DM003 1TB last week as a storage drive for music production. Like lots of folks in this thread, my ST1000DM003 only shows up intermittently. Basically, I have to open my PC and disconnect/reconnect the sata and power cables. I've also changed both cables just in case they were faulty. It disappears regardless. This is all a major pain as everything on the back of my PC has to be unplugged.

My PC has Win XP (32bit) with a 400 GB Seagate ST3400620AS OS Drive.

Am I correct that the firmware update referred to in this thread resolves this issue? I just tried a moment ago (out of desperation) and couldn't get it to work due to the ST1000DM003 not being detected at present. I've no time to unplug everything and open the PC up tonight to get it detected.

I seen the advice in the firmware installation window which said not to be used for Raid systems. I'm not a computer expert and don't know what this means. What I do know is that the word Raid does not feature in my Device Manager anywhere. Does this mean my OS drive (Seagate ST3400620AS) would  be okay running this ST1000DM003 firmware update? Or do I risk losing important things on it?

Any advice would be greatly appreciated.

Scott.

[CoolFENIX]

First of all, sorry for my English, I came here from Russia.

I have the same problem. Computer is turned up so far with a third or tenth attempt. Remove cmos Battery helps partially - I don't need to climb to the wire, now I need to press reset many times.

Cooler Master HAF X, RC-942-KKN1, FullTower, ATX

ASUS P8Z68 DELUXE/GEN3, Z68, Socket 1155, DDR3, ATX

Intel Core i7-2600K Sandy Bridge (3400MHz, LGA1155, L3 8192Kb) OEM

Noctua NH-D14, Socket 1155/1156/1366/775/AM2/AM3/FM1

DDR3, 8ГБ (2x4ГБ), PC3-14900, 1866МГц, Kingston HyperX Genesis PnP, KHX1866C11D3P1K2/8G

3072МБ, MSI N580GTX Lightning Xtreme Edition, GTX580, 2xDVI,HDMI, DP, GDDR5, 384-бит, Retail

Windows 7 x64

Any help, people??

[CoolFENIX]

i bought the new pc with

1Tb 3.5 ",7200rpb, 64mb, SATA III, Seagate Barracuda 7200.14, ST1000DM003

in december of 2011 and still have problems

[RQ]

I have the same problem. To start my PC I need to start and restart it a lot of times. I do not use raid. I have just 1 hard drive an 1 dvd writer.

My HDD is ST1000DM003-1CH162, Serial: Z1D[Edited: Removed personal information per the community rules and regulations.], Firmware: CC46

And don't exists firmware for my hard drive. I think that this is realy strange. For me is interesting when will appear new firmware for this hard drive? Or no chanse to recieve it and better to replace it with other drive from different vendor?

[Tomasz_G]

Hello all,

this is my first post here.

I'm big fan of Seagate drives, I see the future in them.

I sell thousands of Seagate drives to my customers, but only 6 x ST1000DM003 model so far.

However, I'm concerned this thread, since I've two of them.

I have following:

Model 1:
ST1000DM003-1CH162
Firmware: CC44
Model 2:
ST1000DM003-9YN162
Firmware: CC4H

I would like to have them in Matrix RAID, which simply means: "mixed RAID 1 and 0". I'm afraid about my data however.

So far both are running well, but even they are same model is this recommended to run them in 50/50 split in RAID0/1 matrix? Anyway, for me all of You're saying "not detected" means problems with PSU or firmware..

SATA3 drives are very sensitive to: data cable, power. Do not ignore this.

[gagnakureki]

Hi,

I recently bought a 1TB Seagate disc (ST1000DM003-9YN162 ATA) and inserted it into my PC, which already had a Western Digital (WDC WD3200JS-63PDB1) disc in it. (both discs are SATA)

The problem is this. Sometimes when I turn on the computer it doesn't detect the new Seagate disc. The BIOS just hangs for about a minute or two and then displays only the Western Digital disc and continues. If I turn the computer on and off few times it will eventually detect the Seagate drive.

I have tried the Seatools without getting errors. And I've replaced the SATA cables without luck. This problem always persists.

Please help!

E

[gagnakureki]

Firmware CC49

[bstay2]

---

gagnakureki wrote:

Hi,

I recently bought a 1TB Seagate disc (ST1000DM003-9YN162 ATA) and inserted it into my PC, which already had a Western Digital (WDC WD3200JS-63PDB1) disc in it. (both discs are SATA)

The problem is this. Sometimes when I turn on the computer it doesn't detect the new Seagate disc. The BIOS just hangs for about a minute or two and then displays only the Western Digital disc and continues. If I turn the computer on and off few times it will eventually detect the Seagate drive.

I have tried the Seatools without getting errors. And I've replaced the SATA cables without luck. This problem always persists.

Please help!

E

---

I have exactly the same problem. My drive has new part number 1CH162 and firmware CC46, but it does not qualify for the CC4H firmware update (only for 9YN162).  Please help!!