Jump to content

Gradius2

Member
  • Posts

    241
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Chile

Posts posted by Gradius2

  1. Well, if the company is officially in your country, then you can, otherwise, it will be hard.

    It would be necessary to move a massive international action to win faster.

    But the best alternative until now (if you recovered your datas) is just not buying any Seagate product anymore.

    Btw, HDDs will start to die around 2015, when SSD will becomes cheap, bigger and good enough.

    Every HDD is risky (and slow) to use due the mechanical parts.

    The only advantage about HDDs is to have 10TB around ~2013, I have no idea how big SSDs will be at that time (but if they want to compete, it needs to be 2TB~4TB at least).

  2. Checking an old Maxtor (300GB), I got:

    - Burst rate: 114.3MB/sec (the drive is from 26/08/2004 !)

    While a new Seagate (750GB) with SD1A I'm getting just 89.9MB/sec. o.O

    I'm very disappointed.

    Edit: A Seagate 300GB (also like 5yo) managed to get 96.9MB/sec ! A new 1TB (Seagate) with CC1F got just 98.8MB/sec.

    The evidence:

    ST31000333AS.png

    ST3750330AS_new.png

    ST3300831AS.png

    Maxtor_6B300S0.png

  3. I tried it on my locked HD it didn't see it and do noting

    But on my second drive the update was successful

    What will happen if I will take the working updated PBC and put it on the locked HD? will it work?

    Sorry but it will not.

    Every PCB is married with HDA, they're unique.

    Flashing will never works if your HD isn't recognized by BIOS at POST time.

    You need to unlock the drive with RS232 to TTL solution, or spend $500, or just RMA.

    There is no other solution.

  4. Now please tell me, how segate finds a solution in 6 days, when they weren't able to fix the problem in the year before.

    Seagate is cutting 2950 jobs and executives salaries down to 25% too.

    They could just offer a "special bonus" to those who really knows (a firmware is always writing in assembly) to fix the HDD stuff. This is why they could fixed once for all so fast.

    The only difference is .LOD files are cryptographed, since they have HDDs on consoles like Xbox 360, if they just didn't do that, it would be very easy to defect 360's HDDs protections to accept ANY HDD, and ANY size. Plus, it could run games from HDD without any problem.

    However they still needs to release more firmwares, specially for those:

    ST31500341AS

    ST31000333AS

    ST3640323AS

    ST3640623AS

    ST3320613AS

    ST3320813AS

    ST3160813AS

    http://seagate.custkb.com/seagate/crm/self...sp?DocId=207957

    They says CC or LC firmwares aren't affected, but this is untrue, I already saw more than 10 complains with CC's firmwares, and 1 with LC.

  5. The m0,2,2,,,,,22 command took several minutes. I was concerned after about 2-3 minutes considering previous statements that the command should only take 15-30 seconds or a bit over 1 minute, but it finished anyway. So for those yet to do this: Don't panic if it takes a while.

    I wonder though, does the time it took have to do with the number of partitions? I have ten partitions, including several logical partitions for various Linux installs. I'm doubting that it's due to space used on the drive as I know some folks must've had more than 200GB used. It can't be much to do with the processor speed, I'm on a Core 2 Duo e7300 2.66GHz.

    Also, for the other people who have shown their output, only one User Partition Format line was reported - in the above I have two. Should I be concerned about that? Considering that it's working just fine I don't think so, but better safe than sorry. Could it be because I have extended partitions and those who have shown their output only have primary partitions?

    That depends a lot on drive, the smaller and more partitions on HDD (500GB or less), the slower it is. But 2~3 minutes for those drives is normal.

    My 750GB took around 70secs.

    It won't depends on computer at all. It writes on service sector (isn't for user datas).

    You're safe to test, if you see not all partitions are there, stop using and report here.

    Great news (at least for me): I managed to get my drive back to a useable state. If you remember, I was the only one getting a strange error while doing the m0,2,2,0,0,0,0,22 thing, some said my disk is physical dead, others said it's another firmware bug of the SD11-firmware on my drive.

    Well, both guesses were wrong: I tried the whole thing with another PC and it worked, so it had something to do with my COM-port. The strange thing was that I could connect to my HDD via COM-port flawlessly, but instead of the sucess-confirmation I got an "User Partition Format was not sucessful" error.

    With another PC it worked great, BIOS now recognized the drive, but the RAID0 was gone... I found a great tool solving this problem: File Scavenger. It's $50, but it works like a charm (e.g. it can make a software raid and backup the data even when the hardware raid doesn't work) - I'm confident that in about 20 hours I will have all my data back.

    Thanks to all of you helping me and solving the issue!

    I see, your problem was really totally different from the others.

    Keep in mind RAID 0 is the most risky and excelent to loss all your datas, IF just one drive goes down (crash, etc), you might lost everything, no matter if the other drives are working 100% fine.

  6. First impressions for firmware SD1A:

    - Better reading speed (more stable)

    - Better writing speed (more stable)

    - Burst rate went from 82.4MB/sec to 89.9MB/sec (much better)

    - Access time from 12.4ms to 12.3ms now (no changes)

    No problems so far.

    Tested on 4 (four) ST3750330AS [750GB] (originally: SD15, now using SD1A).

    Currently testing defrag with diskeeper, it is running for over 6h now (@ 66% atm), so far so good, the drive is 44% full.

  7. SD1A has been released, 1st impression:

    - Better reading speed (more stable)

    - Better writing speed (more stable)

    - Burst rate went from 82.4MB/sec to 89.9MB/sec (much better)

    - Access time from 12.4ms to 12.3ms now (no changes)

    No problems so far.

    Tested on 4 (four) ST3750330AS [750GB] (originally: SD15, now with SD1A).

  8. About firmware, I'll just post here.

    They finally released a different (fixed?) firmware today for those drives:

    STD Firmware Updates Barracuda 7200.11 SD1A 3 and 4 Disc Models

    (750GB and 1000GB) Distribution tabs

    ST3750330AS 9BX156

    ST3750630AS 9BX146

    ST31000340AS 9BX158

    Generic Disty/STD-OEM, 16MB and 32MB, SATA Configurations, Moose

    SHA1 comparing NEW with old firmware:

    c:Seagate>sha1sum SD1A3D4D.LOD SD1AMOOS.LOD
    b07e3a9ccf49185bc681f858c6ce568b45dd0ae5 SD1A3D4D.LOD (new)
    268c6931e85936cfac3871c5baaee0c327186233 SD1AMOOS.LOD (old)

    This is what flash.bat does:

    fdl462b -m Moose -f SD1A3D4D.LOD -i ST3750330AS -s -x -b -v -a 20

    fdl462b -m Moose -f SD1A3D4D.LOD -i ST3750630AS -s -x -b -v -a 20

    fdl462b -m Moose -f SD1A3D4D.LOD -i ST31000340AS -s -x -b -v -a 20

    I flashed all my 4x750GB, however 3 of them were with SD1AMOOS.LOD already installed, and I still don't know if it really re-flashed with new one.

    How to boot Seagate firmware from a pendrive.

    You'll just need a bootable pendrive (of course), with MS-DOS 6.22, or similar DOS.

    How to extract Seagate ISO:

    Open ISO with 7zip, extract the Bootable_1.44M.img file inside [bOOT] folder (inside the ISO).

    Then open Bootable_1.44M.img file with Power ISO, or Magic ISO, or Ultra ISO, similar, and extract SD1A3D4D.ZIP file inside.

    You only need to copy those files (unziped) to your bootable pendrive, and you're done to boot with pendrive.

    At prompt just type flash (flash.bat) and it will do the rest.

  9. Hi all!

    May the iso be extracted to an usb drive instead to a CD?

    You CAN boot and flash this from a pendrive, you'll just need a bootable pendrive (of course), with MS-DOS 6.22, or similar DOS.

    How to extract Seagate ISO:

    Open ISO with 7zip, extract the Bootable_1.44M.img file inside [bOOT] folder (inside the ISO).

    Then open Bootable_1.44M.img file with Power ISO, or Magic ISO, or Ultra ISO, similar, and extract SD1A3D4D.ZIP file inside.

    You only need to copy those files (unziped) to your bootable pendrive, and you're done to boot with pendrive.

    At prompt just type flash (flash.bat) and it will do the rest.

  10. Okay, they finally released a different (fixed?) firmware today for those drives:

    STD Firmware Updates Barracuda 7200.11 SD1A 3 and 4 Disc Models

    (750GB and 1000GB) Distribution tabs

    ST3750330AS 9BX156

    ST3750630AS 9BX146

    ST31000340AS 9BX158

    Generic Disty/STD-OEM, 16MB and 32MB, SATA Configurations, Moose

    SHA1 comparing NEW with old firmware:

    c:Seagate>sha1sum SD1A3D4D.LOD SD1AMOOS.LOD
    b07e3a9ccf49185bc681f858c6ce568b45dd0ae5 SD1A3D4D.LOD (new)
    268c6931e85936cfac3871c5baaee0c327186233 SD1AMOOS.LOD (old)

    I guess I'll be forced to open another topic to talk about firmware only.

    Edit: currently there is a problem with board, I'll wait until they fix that, meanwhile I'll make some tests, etc. If you can wait couple hours, just wait!

    Every RS232 to TTL will works, also USB to RS232 to TTL, also will works.

    To a complete list of materials, please check the 1st msg on this topic (I included everything there, links and even prices).

  11. :S Well, that was anticlimactic. I hooked it all up, powered on, and in hyperterminal I'm getting nothing. I switched the RX/TX lines (One fellow said he has his RX-RX and TX-TX instead of RX-TX and TX-RX, so I figured maybe mine was mislabled also), and still Ctrl+Z in hyperterminal does nothing. :S Any ideas?

    Edit: Nevermind. I have two COM port options, COM1 and COM3, I forgot to try COM1 again after switching the RX and TX connections. I've got the prompt now.

    Keep in mind all the commands are case-sensitive.

    Plus, double check the speed, it MUST be 38400 8 N 1

    I see you managed to get an answer from terminal though.

  12. Also note that with this one from alldav.com, it doesn't have pins on the gnd/rx/tx/vcc to connect your jumpers. I had my dad solder to it some of the headers that came with the jumper wires I got. I'm about to attempt the BSY fix with that adapter. :D I'll let you know how it goes.

    This is why I included a complete kit (wire jumpers + headers) there. ;)

    Also, Gradius: Not all the PCBs are like that. I have the rectangular one like Fatlip has on his:

    http://www.msfn.org/board/index.php?s=&amp...st&p=823633

    So it may be a little bit different in which or how many screws need to be removed. I'm going to try to do the paper thing also. I'll report how it goes, and see about some pictures for anyone interested.

    They sure can vary from HDD to HDD, but the principle is just the same and won't change.

  13. @Gradius2

    First hello. hi Gradius2 been lurking on these lists 3 or 4 weeks, and have seen your advice.

    very interested in your methods of directly talking to the hdd's. I've never seen this before, but suppose it's all logical when u think about it (communication wise).

    can you provide link to the RS232/TTL convertors you suggested... or is it simply a MAX232 based solution for example :

    http://cgi.ebay.co.uk/RS232-Serial-Port-To...A1%7C240%3A1318

    i do understand the principles, after been a radio ham, and using circuits similar over the years.

    again, many thanks for all your info in this field.

    craig

    STM31000340AS * 2 MX15

    ST31000340AS * 2 SD15

    Yes, the one will works, but keep in mind the whole solution is here (including links and prices for all the parts):

    http://www.msfn.org/board/index.php?showtopic=128807

  14. Just found this one:

    Brinks 7200.11 CC1H 4D8H 9JU138-301

    It seems those are for 1.5TB only (ST31500341AS).

    My 1TB is 9FZ136-300 (CC1F)

    ---

    Here are the files:

    http://rapidshare.com/files/178995122/Brinks-4D8H-SD1A.ISO

    Instructions:

    1. Verify the sticker on your hard disk matches these:

    Model: ST31500341AS

    P/N: 9JU138-300 (or 9JU138-336)

    Firmware: SD17 (or SD15, SD16, SD18, SD19)

    S/N: doesn't matter

    2. Burn the ISO to CD

    3. Boot from the CD.

    It is recommended to physically disconnect all the other ATA/SATA devices when running step #3.

    ----

    http://rapidshare.com/files/178995121/Brinks-4D8H-CC1H.ISO

    Instructions:

    1. Verify the sticker on your hard disk matches these:

    Model: ST31500341AS

    P/N: 9JU138-301 (NOT -300 and NOT -336 !!)

    Firmware: CC1F or CC1G (NOT SDxx !!)

    S/N: doesn't matter

    2. Burn the ISO to CD

    3. Boot from the CD.

    It is recommended to physically disconnect all the other ATA/SATA devices when running step #3.

×
×
  • Create New...