Jump to content

Gradius2

Member
  • Posts

    241
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Chile

Posts posted by Gradius2

  1. Good to see you around :) and know everything is fine.

    But don't be too proud about hard disk manufacturer change, though the 7200.11 (and to some extents the 7200.12) have been total crap, we do have the deskstar/deathstar preceding issue:

    http://en.wikipedia.org/wiki/Hitachi_Deskstar

    so I won't bet against the possibility that sooner or later another disk manufacturer will fall in a similar issue.

    jaclaz

    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.

  2. An update:

    A PM brought to mind the idea of - is my RS232 to TTL getting enough power at 3 volts? Well, it's the SchmartBoard module "Populated RS-232 SchmartModule" which says it wants 5 volts to run, but seems to be communicating fine with the HDD at 3 volts. Okay, but I should try 5 volts, right? Tried that too, and got the same "Unknown Diag Cmd Failure 12CC4" when I tried the "N1" command.

    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

  3. The other command set that came up no good was trying to list all the commands available to the drive. I don't remember where I saw that in this topic, but it was something like "/Q" from the "F3 T>" prompt. Or maybe "/C", I don't remember. Anyway, I DID do it as the post said, and I got the same "Unknown Diag Cmd Failure 12CC4" response.

    In case you're thinking it could be shaky contacts that I'm jiggling when doing the PCB re-attach, I'm using jumpers going from the HDD pins to the pins on the RS232-TTL converter, and they're solidly connected. Also I've tried it about 6 times with always the same result.

    Thanks for the idea, I'll try again when I get home in a few hours....but...any other ideas?

    Thanks,

    Chris

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

    Gradius

  4. I hooked up my RS232 to TTL, disconnected the drive's PCB, powered up the drive with a SATA power cable, hooked up two D cells for 3 volts to the converter, attached the ground wire. Hyperterminal talked to the drive fine. I spun the drive down, reconnected the PCB and typed:

    F3 2>U

    and the drive spun back up, so far so good. Here's what happens next:

    ____________________________

    Spin Up Complete

    Elapsed Time 7.093 secs

    F3 2> (I type /1 and enter)

    F3 1> (I type N1 and enter)

    Unknown Diag Cmd Failure 12CC4

    F3 1>

    ____________________________

    I've tried several times, powering down and starting from scratch. I tried going ahead and typing in the

    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

  5. I'm so happy I learnt a new language here!!

    VAI-TE FUDER SEAGATE!

    VAI-TE FUDER SEAGATE!

    VAI-TE FUDER SEAGATE!

    Actually the correct is just "Vai te fuder Seagate", no need - (hyphen) there. ;)

    Personally I prefer "Vá se fuder Seagate!". :whistle:

    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

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

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

  8. And finally before commands:

    post-230434-1233749943_thumb.jpg

    That's the head motor, nothing to do with SPIN motor. :whistle:

    aviko is just trying to discredit a proven fine guide. :rolleyes:

    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.

  9. Hi again,

    Now i've tried the loopback test so my setup is correct.

    I dont get any response from the terminal, I dont get "F3 T>", but i can type..

    I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?

    Anyone that can help me? Over msn maybe?

    I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.

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

  10. @my77stang:

    Yura is well known data recovery researcher, aviko works in data recovery company and posted yura's solution. The original solution was given into public domain in Polish, gradius is from Chile - do you think he understand Polish better then aviko? I don't think so. He used translator to make his 'help topic' - just for profit as we see now (gradius registerd puma34 account just to force people to pay more and discredit aviko - which is even more unfair than stealing somebody's work).

    Me? for profit? registered puma34? LOL !!! :w00t::lol:

    You guys are too funny. :thumbup

    Nice try aviko's clone. ;)

  11. How would optimizing the OS affect the HDD? if indeed it's a journaling problem (does NTFS use journaling?) Anyways, I've got BOTH 7200.11 500GB running on SD1A now (one of up unbricked using your solution, thanks!), I have a 640 GB Western D for my important files, and using Drive Image to back up the OS drive to newly unbricked drive. Seagate's such a b***h.

    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

  12. I'm using 6 HDDs, 2 them were with BSY error, and 1 with wrong firmware, I updated those 4 (SD15) to SD1A and they all are running just fine at this very moment.

    Gradius

    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:

    31000333asxf4.jpg

    Know issue:

    Clicking: doesn't read/write while clicking leading to BSOD or other errors.

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

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

    This is my experience with this problem so far:

    I completed a successful firmware upgrade on my ST31000340AS one week ago after receiving problems of an I/O device error in Windows Vista when I tried to access my data on the harddrive. Now, one week later, I am completely unable to access my harddrive. BIOS will not detect it.

    Anyone else?

    I have a computer w/ one ST3500320AS drive.

    I went ahead and updated the firmware (to SD1A).

    Everything seemed to be stable, but then I started getting blue screens (Vista x64) after a few days.

    I got really upset and said: oh well... lets try to do a clean Windows Vista installation.

    I did just that and noticed that after I start the Vista installation, it's not able to format the drive.

    At the moment, the drive is unusable since I cannot format or reinstall Windows at all.

    I tried setting the BIOS to either AHCI or ATA, but none worked. Please note that the BIOS does see the drive.

    Looking at some other forum posts, I think this has to do w/ the I/O errors people reported regarding the firmware update (for the exact same model).

    Seagate, do you have any known issues w/ the SD1A firmware update? Can you check this issue out (more poeple reported it) and revalidate the update?

    I'm writing this from a friend's laptop, since my only computer is just a piece of metal atm.

    A topic I opened few days ago has been deleted with no reason.

    I was talking about a problem with ICH9R and two disks in RAID...

    Sometimes the computer freezes, an event says "Device\Ide\IaStor0... not responding" and the RAID starts rebuilding or the disk is marked as offline.

    Three or four persons seem to have the same problem and was explaining their problem before the removal of the topic.

    This problem started with the new (second) firmware : SD1A.

    I don't know why the topic has been deleted ?

    Does Seagate want to ignore the problem or is it because the problem wasn't explained here ?

    I flashed both of my ST31000340AS drives on the22nd and one died on the 30th, or it got so bad that mdadm pulled it from service anyway.. Several SMART errors were logged, including two reported uncorrectable. I'm going to bring the drive in to work tomorrow to run some tests and maybe do a low level format with SeaTools, but I'm not expecting much. This is getting tiring.
    I have downloaded SD1A and tried to flash my ST3500320AS HDD. HDD had previously problems when I run Linux reporting some I/O errors. I have 2nd HDD als Seagate but is 250GB and it is somehow old. I have Windows Vista on him and problems still rise from time to time having no access to ST3500320AS from Vista or during startup BIOS recognizing. Yesterday I have returned all settings to BIOS to non-overclocked and I couldn't update to SD1A saying that can't detect Seagate drive model ST3500320AS. Does anybody else have this problem too?

    More reports:

    http://forums.seagate.com/stx/board/messag...;thread.id=8569

×
×
  • Create New...