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

[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.