hwdiver

Member
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hwdiver

  • Rank
    Member

Contact Methods

  • MSN
    hwdiver@hotmail.com
  • ICQ
    113340769

Profile Information

  • Location
    Russia
  • Interests
    hardware, reverse engineering
  1. No ! "A4" is a revision of MASK ROM of MPU core. Zes, this drive maz fail in near time... Backup all important information.
  2. Ever looked into the 120g ibm 120gxp? I have one, which occasionally makes strange noises like it's powered down and back up for a second. DFT says it's ok, the SMART monitoring tool from IBM says it's healthy, but my ears don't! What is the application you used to get those disk surface images? Is it available for download anywhere? Hmmm... I use the vendor specific software, it`s confidential. But I can post P/G-DEFECT LIST images from some AVVA and AVVN drives. Interesting ?
  3. It`s a future family, Professor ! 8-) The latest Fujitsu drive are FUJITSU MPG3xxxAx drives - PB-16xx family. But Fujitsu used PB-17H family in vendor specific software and I interesting for ANY information about IS THIS DRIVES ARE REAL OR ONLY FUTURE FUJITSU`s PROJECT ??? Bye.
  4. Hi ! Hmmm... I don`t think so. Fujitsu MPDxxx drives has own specific problems, but it different from described Fujitsu MPG3xxxAx bugs. In Russia, most of HDD repairers call IBM 75GXP drives (DTLA-3070xx series) as "Woodpecker" because of the nice ;-) sound when the drive try to retrain defective sectors on R/W operration. 8-) The basic problems with 75GXP drives: ============================ 1) Faulty contact with PCB and disk enclosure (DE). The best solution in this case is soldering the contact pad on the back side of the PCB. 2) This drives has MANY firmware revision with stupid (oooppsss!) bugs - in some cases while drive process a WRITE command it damage one or more SA modules in firmware zone (!). Of course, after this drive can`t to initialize and BIOSes (and utils too) report the "Drive not detected". This bug corrected on the last firmware updates. 3) Incorrect functioning of S.M.A.R.T. off-line test. The way to skip problem - disable S.M.A.R.T. operation. WBR, Mishail Mavritsin ================ HDD Service Engineer Russia, Moscow Very interesting stuff. Can you possibly post the firmware version that fixes the problems? I have a 30GB 75GXP, that had old firmware, so I flashed it with the newest OEM firmware, to supposedly fix those bugs, and then it died a month later. It has errors in the sectors used to store the error logs and remapping info! It would really be a shame, if those drives are in fact, basically sound, except for the software (firmware) bugs present. I like the drives otherwise, they are fast, cool, and quiet. I think Fujitsu Co. is not takes pleasure if I post patched firmwares. 8-) Do you know about big fiasco of Fujitsu MPG`s drives ?
  5. Oh wow, that's some pretty low-level hacking. Is there any possibility you could investigate bugs in the IBM 75/60/120GXP firmware revisions? Specifically the ones that can apparently cause the drive to get stuck in "write mode", when power is removed from the drive, and therefore wipe a good portion of the servo info (among other things) when the heads retract? My 30GXP had some old firmware, and I flashed it with the newest generic OEM firmware upgrade, to fix the supposed problem with the drive possibly wiping user data sectors during SMART and other internal self-test operations. It died not more than a month after that. Now, I have sector errors in the reserved sectors used to store where the defective user sectors are on the drive! You can hear it re-seek during a DFT full test, when it hits the part "reading internal error logs" (or something like that). I have also had problems, instant red RMA screen, while running DFT full-erase. My guess is that it encountered a sector with an unrecoverable error, and couldn't store that sector's address in the reserved sectors properly (kind of like a double-fault in an Intel CPU), so it instantly errored. Larry, REVERSE ENGINEERING is NOT A HACK. I don`t use this information in commerce. But it VERY interesting to know the REAL way of hdd`s life ;-) Hmmm... I know about most of IBM bugs. Many of these may repaired in 10-15 min without lost of user information;-) IBM internal error log called as "ELG1" and internal event log called as "EVLG". This modules a part of IBM firmware and it can repaired in many cases. ;-) Information about reassigned defects stored in RDMT module (Reassigned DefectMap Table). If you want to remove all unrecoverable errors indicated in SMART reports (for example), try to execute this sequence of ATA commands: 1) SECURITY ERASE PREPARE 2) FORMAT UNIT - documented cmd 0xF7. Use 0x11 in Features register to MERGE Grown defects (G-List) to Primary Defect List (P-list). You lost all of your information on drive, but after this drive looks as NEW 8-) Bye. P.S. Check my old web site on http://pcjs.chat.ru and look for IBM specific "feature" - crazy defects count in Primary Defect List. The second IBM`s "feature" - very many reassigned defects.
  6. I have a lot of vendor specific information and know about head damage, landing zone, firmware structure, defect management, etc. But head damage not a problem - I have a lot of experience with changing damaged HDA to good head assembly from donor drive and repair much more than 1000 drives by myself. No any clean room required! 8-) By the way, you can try to shift 4-head HDA (or more) on IBM drives (DTLA, AVER, AVVA/AVVN). This is a best way to appreciate the "stiction" problem. ;-)
  7. Hi ! Hmmm... I don`t think so. Fujitsu MPDxxx drives has own specific problems, but it different from described Fujitsu MPG3xxxAx bugs. In Russia, most of HDD repairers call IBM 75GXP drives (DTLA-3070xx series) as "Woodpecker" because of the nice ;-) sound when the drive try to retrain defective sectors on R/W operration. 8-) The basic problems with 75GXP drives: ============================ 1) Faulty contact with PCB and disk enclosure (DE). The best solution in this case is soldering the contact pad on the back side of the PCB. 2) This drives has MANY firmware revision with stupid (oooppsss!) bugs - in some cases while drive process a WRITE command it damage one or more SA modules in firmware zone (!). Of course, after this drive can`t to initialize and BIOSes (and utils too) report the "Drive not detected". This bug corrected on the last firmware updates. 3) Incorrect functioning of S.M.A.R.T. off-line test. The way to skip problem - disable S.M.A.R.T. operation. WBR, Mishail Mavritsin ================ HDD Service Engineer Russia, Moscow
  8. No ! Head stick - is FATAL for most of drives except Fujitsu hdds. If you can provide power supply to you hardware on 24/7 - lets drive to spin up ! Bye.
  9. Hi, everybody ! Does anybody know about Fujitsu MPH3xxxAH drives (PB-17H family) ? I found a mention about this drives in Fujitsu diagnostic software and I was amazed... :? On Fujitsu web sites I can`t find any information about this phantom family. WBR, Mishail Mavritsin ================== HDD Service Engineer Russia, Moscow
  10. Hi, everybody! The fault with the drives isn`t in the Cirrus Logic controller chip ONLY. In many cases this drive have problems with SA (system area) modules - they can damaged by many factors and drive fail to start-up initialization. This is not a BUG, it`s like a feature and repaired in about 99.9% cases. But problems with CirrusLogic chip are real. By the way, there are two revision of this chip: CL-SH8671-450E-A3 CL-SH8671-450E-A4 I know exaclty the difference is in the MASK code within the core. MASK code allow to manage a low-level operation in drive SafeMode and starting main firmware code from FlashROM. I reverse Fujitsu MPG3xxx (AT,AH & AV) firmware code, MaskCode and collect some specific Fujitsu bugs and nice undocumented features. The common problems are: * Spontaneous and repeatable SpinDown/SpinUp sequence. (Fatal, PCB) * Error while programming flash chip. Original FlashROM data erased by MaskCode, but transferred data from interface isn`t programmed. (Fatal, PCB) * Drive not detected. Problems with system information on the plates (in firmware zone). Recoverable in 99.9% cases. * Drive can`t to SpinUp after power on. Firmware code in FlashROM damaged or PCB fault (i.e. CirrusLogic chip). Recoverable. * Drive come to "READY" state very fast (DRDY/DSC bits in status port), but spindle is not running. And drive not responded to 0xEC (IDENTIFY DEVICE) command (BIOS and ALL utilites says "Drive not ready/not detected"). This problem is happen because firmware code in FlashROM damaged. Recoverable. Hmmmm... Something else ? Maybe, but it`s too large for one message... P.S. Sorry for bad English. It`s not my native language... BTW, Mishail Mavritsin =============== HDD Service Engineer Russia, Moscow
  11. Clicks - you hear the knocking of HDA (head assembly) and spindle while drive fault to thermal calibration, lose a ServoMark signal or fault to Seek to bad track. Freezes - because of drive spontaneously stop and restart the spindle motor. It`s indicates the problems with PCB (CirrusLogic chip). I`ll recommend to you to change this drives or send it to repair :-). WBR, Mishail Mavritsin ================= HDD Service Engineer Russia, Moscow
  12. Hi, everybody! The fault with the drives isn`t in the Cirrus Logic controller chip ONLY. In many cases this drive have problems with SA (system area) modules - they can damaged by many factors and drive fail to start-up initialization. This is not a BUG, it`s like a feature ;-) and repaired in about 99.9% cases. But problems with CirrusLogic chip are real. By the way, there are two revision of this chip: CL-SH8671-450E-A3 CL-SH8671-450E-A4 I know exaclty the difference is in the MASK code within the core. MASK code allow to manage a low-level operation in drive SafeMode and starting main firmware code from FlashROM. I reverse Fujitsu MPG3xxx (AT,AH & AV) firmware code, MaskCode and collect some specific Fujitsu bugs and nice undocumented features. The common problems are: * Spontaneous and repeatable SpinDown/SpinUp sequence. (Fatal, PCB) * Error while programming flash chip. Original FlashROM data erased by MaskCode, but transferred data from interface isn`t programmed. (Fatal, PCB) * Drive not detected. Problems with system information on the plates (in firmware zone). Recoverable in 99.9% cases. * Drive can`t to SpinUp after power on. Firmware code in FlashROM damaged or PCB fault (i.e. CirrusLogic chip). Recoverable. * Drive come to "READY" state very fast (DRDY/DSC bits in status port), but spindle is not running. And drive not responded to 0xEC (IDENTIFY DEVICE) command (BIOS and ALL utilites says "Drive not ready/not detected"). This problem is happen because firmware code in FlashROM damaged. Recoverable. Hmmmm... Something else ? Maybe, but it`s too large for one message... P.S. Sorry for bad English. ;-) It`s not my native language... BTW, Mishail Mavritsin =============== HDD Service Engineer Russia, Moscow