Gradius2

Just to report (because is a new record!). A ST2000DM001 just died (out of nothing) with less than 250 working days! And yes, it was using the last FW available to the public. I can't see (or wait) the time when 1TB (and more) SSDs would be cheaper.

I would never use (or continue to use) such HDDs. Backup the DATA while you still can, and go for something more reliable.

That's right, and don't forget the Pizza + beer (or wine!).

The real option is backup, and you also need to check backup time after time. I went for WD not Hitachi. Looks like Samsung is also a good (cheap) alternative. Btw, the Seagate list with FW problem is: Barracuda 7200.11 ST31000340AS ST3750330AS ST3750630AS ST3640330AS ST3640530AS ST3500320AS ST3500620AS ST3500820AS ST31500341AS ST31000333AS ST3640323AS ST3640623AS ST3320613AS ST3320813AS ST3160813AS Barracuda ES.2 SATA ST31000340NS ST3750330NS ST3500320NS ST3250310NS STM3320614AS STM3160813AS DiamondMax 22 STM31000340AS STM3750330AS STM31000334AS STM3500320AS SV35 ST31000340SV ST3750330SV ST3500320SV ST3320410SV I got a lot more apart of how/what HDD companies works/do, and I can tell you is a total prehistoric business. They should unite and create an UNIVERSAL and up-to-date standard for HDD's firmwares. Just the algorithm would continue to be unique, but the way to access the drive and allows us a much easier way to recovery, diagnostic, etc any HDD would hundred fold (or even more). S.M.A.R.T. is way too limited and not completely reliable. Is time to change, specially when many of us know the real future is indeed SSD drivers, when they fail you can still easily read all the stuff there, just cannot write/erase/format anymore. The same will never happen with HDDs.

Just to let you guys to know... yes, I'm alive and well. Specially since I decided to change HDD manufacture. ;-)

Yes, 3V is more than enough. If you change to 5V you will see no difference. Your problem is different, it seems like something else. It might be related to mechanical part or some important data (on service area) was lost. Gradius

When you put the HDA back and does Spin UP cmd, it really goes up? Can you confirm this? Gradius

Keep in mind to use the LAST firmware available, as I reported here: http://www.msfn.org/board/index.php?showto...st&p=836051

You're probably doing wrong this step: F3 2>Z (enter) Spin Down Complete Elapsed Time 0.147 msecs (the time will vary here) F3 2> Now you need to re-connect PCB HDA to HDD, without turn off anything ! and only then continue to: F3 2>U (enter) Spin Up Complete Elapsed Time 7.093 secs F3 2> F3 2>/1 (enter) F3 1>N1 (enter) Steps. Gradius

So far they're operating normal here, no reformat at all, just chkdsk /f after I flashed with last firmware. I used HD Tune PRO for S.M.A.R.T., to check cache I used Everest Ultimate Edition 4.60.1591

Actually the correct is just "Vai te fuder Seagate", no need - (hyphen) there. Personally I prefer "Vá se fuder Seagate!". Edit1: Those who are using a cable from mobile phone will need to use GND too, that is not necessary if you're using a dedicated RS232 to TTL adapter (like me). Edit2: I recommend to everyone who updated SD1A with older version, do it again with the NEW version. I'm sure they messed with code again, the most recent (and probably the last one) is from 27/01/2009 (or 01/27) released in 29/01/2009 (01/29) at best. Firmware is from 27/01 and flasher from 29/01. Details here: http://www.msfn.org/board/index.php?showto...st&p=836051

Probably, but I'm not 100% sure. All I got was "sending binary to the drive" or something like that.

Flashed with "new" SD1A no apparent changes so far.

Well, I have some bad and "good" news from Seagate. "Good" one first: They released a new firmware (yes, AGAIN!) dated from 27/01/2009 @ 8:17am (but released only in 29/01/2009 at best). BAD one is: If they did that, is probably for a good reason (?), what isn't fair (for us) it was labeled as SD1A (yes, again), but they're different. Probably they labeled as same old SD1A to not showing for everyone they slipped with the code again (sigh). Old flasher: FDL462b.EXE (v4.62b) NEW flasher: fdl464.exe (v4.64) Firmwares (SD1A3D4D.LOD): OLD: b07e3a9ccf49185bc681f858c6ce568b45dd0ae5 NEW: d7877432f3d4827a39857b30d793df4081342d1d Direct link for firmwares: http://support.seagate.com/firmware/firmnav_en.html I checked SD1A only, no idea on others. This is for: ST3750330AS, ST3750630AS, ST31000340AS running AD14, SD15, SD16, SD17, SD18, SD19 or SD81 firmwares.

Hi cmburns, I tried to access the link, but it was just impossible, it never appeared here, perhaps is under overload. You're not the only one disappointed with Seagate, I'm sure the company will suffer a big drop on profit, personally after all this I don't think I'll buy another Seagate product, specially with that kind of support they provided to the users when this thing "exploded".

That's the head motor, nothing to do with SPIN motor. aviko is just trying to discredit a proven fine guide. We all have enough of it. If you see, those guys have just 1 to 3 post max, and this is why they don't know this dirty play aviko is doing. If he was right since start, he should just started long ago his own topic (or leave) in first place, and not trying to continue to discredit a proven fine guide. This topic got so messed because of him, I'll just close it.

If you have this problem, please report it here.

Sure, no problem. Now they will think you're me.

Turn off all, remove the PCB from HDA, power on, then try CTRL+Z.

Me? for profit? registered puma34? LOL !!! You guys are too funny. Nice try aviko's clone.

It's looking like that. We'll know more in coming weeks.

The real part of the OS <between> HDD is on SATA controller drivers, keep this always updated with most stable release. The others are hints to keep your computer running fine and responsive. About NTFS and journal, yes: http://technet.microsoft.com/en-us/library/cc781134.aspx

I thought the firmware version out there now was SD1B and not SD1A..... I upgraded my ST31000333AS from SD15 to SD1B although my drives didn't fail before the upgrade. So far it seems a new 7200.11 symptom with SD1A: http://www.msfn.org/board/index.php?showtopic=129459 Well, SD1B and SD2B are for other HDDs. SD1B: ST31500341AS: http://support.seagate.com/firmware/Brinks-4D8H-SD1B.ISO ST31000333AS: http://support.seagate.com/firmware/Brinks-3D6H-SD1B.ISO ST3640323AS: http://support.seagate.com/firmware/Brinks-2D4H-SD1B.ISO ST3640623AS: http://support.seagate.com/firmware/Brinks-2D4H-SD1B.ISO While those uses SD2B: ST3320613AS: http://support.seagate.com/firmware/Brinks-1D2H-SD2B.ISO ST3320813AS: http://support.seagate.com/firmware/Brinks-1D2H-SD2B.ISO ST3160813AS: http://support.seagate.com/firmware/Brinks-1D1H-SD2B.ISO From Seagate: Note: If your drive has CC firmware, your drive is not affected and no further action is required. Attempting to flash the firmware of a drive with CC firmware will result in rendering your drive inoperable. Funny enough, they removed LC above. Gradius It seems CC are affected after all: Know issue: Clicking: doesn't read/write while clicking leading to BSOD or other errors.

Important steps to follow: - Always keep your OS updated; - Check your HDD for any possible error (like cmd > chkdsk, or similar); - Keep your drivers updated, specially drivers for SATA controller chipset; - Always use a good anti-virus, anti-spyware and firewall, and keep them all updated; - Whenever possible keep a backup of your most precious data; - If using Windows, keep the registry as clean as possible (for example: Registry Booster, or Registry Mechanic, or CClean [is freeware], or other). To speed up a bit: - Clear your browser cache (aka Temporary Internet Files), etc; - Remove programs you don't use or need anymore; - Remove services you don't use or need anymore; - Remove auto-startups (msconfig) you don't use or need anymore; - Use defrag disk like diskeeper (or your favourite tool). Gradius

So far, this applies only to those who just did a firmware update/upgrade to SD1A, without requirement of 0 LBA or BSY fixes. It seems more and more reports are coming from those who just did an update/upgrade to SD1A. I was thinking on possibility on bads (AD14, SD15, SD16, SD17, SD18 and SD19) firmwares didn't write well the "journal sector" (I'll use this term) while those drives were operating before upgrading to the fixed SD1A. If this is confirmed, then it explains why we read more and more reports talking about getting BSOD errors on Vista and unable to perform a new format to re-install Vista, leaving the drive unusable. There are also error reports while using Linux too. From Seagate: http://stx.lithium.com/stx/board/message?b...ing&page=10 More reports: http://forums.seagate.com/stx/board/messag...;thread.id=8569