Jump to content

kadolf

Member
  • Posts

    25
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Germany

Everything posted by kadolf

  1. Yes, I'm using IDE mode. No other drives are connected, exept a SATA-DVD-writer - I will try to get one with IDE, maybe that's the problem.
  2. Has anyone tried to flash the new firmware for ST3320613AS? I tried, but without success: The firmware update tool says that it will work with ST3320613AS/9FZ162-300, SDxx only. My drive is such a ST3320613AS/9FZ162-300 with SD11 and the tool recognizes that: Model ST3320613AS SN 9SZ0**** FW SD11 on Generic PCI ATA Bus 0 Device 1 But then it aborts with following error messages: NO MATCH! WILL NOT DOWNLOAD FIRMWARE! ********* Error: Specific model not found. ST3320613AS expected. ********* Cycle power to continue...
  3. I know that RAID0 is risky, that was the reason I bought an external Seagate ST31500341AS, I wanted to make a backup every week. Sadly one of my RAID0-drives got broken before I had the change to back up. Well, now everything is fine I think.
  4. 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!
  5. Connect the HD on terminal, you should be able to see which error is (if CC or not). Gradius I don't get the CC message, but the method of "unbricking" 0LBA-drives does not work. Seems like I have to wait for any news or for an answer from Seagate.
  6. Nobody has an idea what will help against my problem described in #56 ? I can't imagine it's a hardware fault. It just won't regenerate the partition successfully...
  7. I used Realterm with Windows Server 2008, the terminal session works, so at least Realterm is going to work with Vista.
  8. Hi. Do you mean this page: https://apps1.seagate.com/rms_af_srl_chk/ ? Well, when I entered S/N a few days ago it showed "Not Affected" - but there may are reasons why they deleted the serial checker But if it's affected by both the BSY and the 0 LBA error, shouldn't the CC errorcode show up in HyperTerminal?
  9. Hi. I hope you can use this data: ST3320613AS, P/N 9FZ162-300, FIrmware: SD11, Date Code: 08391; Site Code: TK. Many thanks for your commitment! I'll be off for the next hours - it's 12:30am in Germany and I've to work tomorrow. Good night
  10. As far as I can say it went into 0 LBA while my PC booting. A month ago, when this happened, the RAID-BIOS said failed and when I deactivated the RAID-controller BIOS said "HDD S.M.A.R.T. CAPABILITY: NONE". Unfortunately my next action was not to look into the drive configuration of the Setup Utility, I first tried a few other thinks (different controller, different cables, different HDD-PCB) - all without sucess before I saw, that the drive is still recognized, but with all drive parameters set as 0 and without any capacity. EDIT: Thanks for your help, but neither m0,1,1,0,0,0,0,22 nor m0,1,1,2,2,0,0,22 are working, the same error as described in Post 65 appears.
  11. Yes it is. As I unterstood your tutorial I just have to disconnect it if I'd need the BSY-fix, am I right?
  12. I would like to apply the fix, but as stated in post #65 unfortunately it doesn't work.
  13. Hello Shuky. I have started reading the thread on page 27, but I don't get it - has someone found out how to deal with my problem?
  14. Hello. The cable is a simple data-cable I bought a long time ago for removing my mobile phones simlock. I don't know where it takes it's power from - I think likely from the serial port (I know, it's not build for providing power, but well, the interface seems to work?). I just searched google for a schematic of the EXAR SP232AET, unsoldered the cables leading to the SAGEM-plug and soldered two short cables to the right pins of the IC, leading to my drive. It was just a typo here in the board, in HyperTerminal I entered the comma. What catches my eye is that when I connect the faulty drive BIOS says "HDD S.M.A.R.T. Capability: NONE" - is this regular when a drive is affected by 0LBA-bug? @Shuky: Thanks for the link, I'm going to read...
  15. I tried the 0 LBA fix (HDD is recognized by BIOS, but as 0MB), but it doesn't seem to work: When I input "m0 2,2,0,0,0,0,22" it takes a few seconds until the first line ("Max Wr Retries"...) shows up completly but then appears the following error message: Error 1008 DETSEC 0000500D User Partition Format Failed - Elapsed Time 0 mins 00 secs R/W Sense 00000002, R/W Error 00000084, File Error 00001002 Blk Addr 01080001, Blk Addr Type D0, Cyl 01590000, Hd 00 Anyone experienced the same or can help? EDIT: Interface is a modified Sagem data-cable with SP232AET-chipset (equal to MAX232), but this interface seems to work as it gets an answer.
  16. Gradius, you are a hero! If Seagate won't repair my drive (their tool thinks I'm not affected...) I'll have to use this method. Is it true, that I have to use a partition recovery tool after doing the steps against the 0 LBA error? I ask because the affected drive was part of a RAID0 - are such tools able to recover partitions on a RAID0-drive?
  17. My drive is bricked, but their serial number check thinks it's not affected.
  18. Good to hear. Hopefully it wasn't just an official statement for the media, but they will realize it for everyone who was affected by the bug(s).
  19. Didn't they say "through December"? English isn't my native language, but doesn't this mean that all drives, including the ones producted in December, are affected? EDIT: Sorry, I meant all drives till December.
  20. I think at the moment no one can say for sure. There where many presumptions of circumstances leading to the firmware issue (e.g. the firmware version, ...), but some people had this issue with other firmware, with an other country of production, ... I think the only thing we can say for sure is that many of the 7200.11 drives are affected and that you better should make a backup.
  21. I don't want to make you troubles, but I have a similiar chipset (MCP56) and was affected at least by the 0MB-Bug... I can choose between IDE-mode, AHCI-mode (which is with NCQ) and RAID-mode (which was activated) in my NForce560-mainboards BIOS.
  22. What a doubtful glory Thanks for the link, it's very interesting. Well, the whole 7200.11-story seems to become quite popular in Germany at the moment, most of the online magazines have published articles, hopefully Seagate reacts.
  23. It's a Xilence SPS-XP420.(12)R 420W PSU I know that Xilence isn't a brand known for superior quality, but voltages are quite good even with Prime95 and 3DMark running and the whole system worked stable for months. Further data about my PC you can find at http://www.sysprofile.de/id58426 - although it's a German page you should be able to gather all needed information.
  24. 67:9SZ*****:ST3320613AS:9FZ-162-300:SD11:08391:TK:August 2008:2008-12-22:OEM:kadolf:Germany:0GB-Bug:WinServer 2k8 x64 Broke-down as a christmas present. Often recognized as 0GB, but twice it was recognized by the BIOS as 8GB.
  25. I just read on a German website (http://www.computerbase.de/news/hardware/laufwerke/massenspeicher/2009/januar/barracuda_720011/), that Seagate is going to make a statement in the course of tomorrow. Currently it's not clear, if this statement will be good or bad for us 7200.11-victims By the way, am I the only one having troubles with a ST3320613AS (320 GB, one platter, SD11, Site-Code: TK)? Two days before Christmas Eve my PC stopped while booting. I made a reset and the RAID-Bios didn't find one of the two harddisk (it's a RAID0) anymore... So I put that thing in IDE- instead of RAID-mode and looked what the BIOS recognized: It recognized the name of the hardisk, but didn't recognize it's size and parameters. The worst thing is that I had bought an external harddisk for backups (a Seagte ST31500341AS ) - sadly the parcel service brought it 10 minutes before I lost my data (last and just partial backup: july 2008). What a sad fate!


×
×
  • Create New...