• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jroymd

  1. To jaclaz, It looks like you are right; it turned out to be an LBA 0 error and a bunch of bad cables. The 1.5 TB drive is back to its old self, ready to crash another day.
  2. I am late to this forum but familiar with the problem of the Seagate bricked drives. I have a 1.5 TB primary drive and also have 2nd drive for Vista and a 3rd drive for Xp. I would like to apologize for a simplistic question, but I have been unable to find the answer in the last 111 pages. The drive functioned for 6 months, booted daily under Win7 RC, and one day would not boot. It hung at the post and would only proceed to the BIOS if the F1 key was depressed. The BIOS indicated that the drive was present but was ZERO megabytes in size. I can boot from the other disks, and the affected drive cannot be read by any other computer. Pressing F1 does not allow booting from the primary disk. I have been wrestling for three weeks with the CA-42 data cable issue for reprogramming the PCB. After trying SIX different cables I finally found one that communicates with the PCB. (It's amazing how many different and unmarked CA-42 cables there are.) My question is basically that I am not sure which error I have. It seems likely it is one of the two previously cited: 0 LBA or the BSY problem. I read the posts by Gradius2 where he states: There are two common errors on Seagate 7200.11 HDDs (caused by bugs on firmware): - 0 LBA error: it happens when your BIOS can recognize your HDD at POST moment, but as an 0MB drive. - BSY error: it happens when your HDD enter on a halt state, or BuSY state. In this condition, your HDD will not be recognized by BIOS at POST moment. I'm not sure if the drive is not booting because it is not recognized as having more than ZERO megabytes or is it not proceeding because it is in a perpetual BSY state. The fixes are different, and I do not want to screw things up now. Is there any post in this thread that can clarify my problem?