November 29, 2009

 

SUCCESS: I've recovered data from my hdd

I've recovered all data from my Maxtor Diamond max 22 (Seagate 7200.11 clone), see this link for details. The HDD was locked due to Seagate firmware problem (BSY status error). Finally, I've used commands from this guide and Siemens M55 RS-232 cable. Also I asked my friend to make a MAX232-based scheme, but it was incompatible for some reason and I've fallen back to phone cable (which was the backup solution). I did not get the LBA 0 problem after fixing BSY state error.
So if you have this problem, drop me a message in comments to get details on procedure, I will try to help you.
UPD: here's cool video guide (using Nokia USB cable and they disconnecting head block while I disconnected spin motor - result seems to be the same).

Labels: , , , , , ,

November 22, 2009

 

I had Maxtor HDD failure: factory problem, bad firmware

I have Maxxtor Diamond  Max 22 500Gb (STM3500320AS model with "mx15" firmware).

The problem this model has is same as in Seagate 7200.11 series: some counters in system area overflow... and microcontroller disables all IO operations to prevent data loss (which is, of course, logicallly thinking, good idea. But the criteria does not seem to be the right). Therefore, all data is stored OK inside bricked HDD. 

Symptops: HDD BUSY led are being turned on during computers seeks for HDD on startup, this process is VERY long and ALWAYS ends with either a message "boot device not found" (if affected HDD is a system one), or system loads, but affected HDD is not detected by the system (at all, not only partitions, but THERE'S NO ANY HDD detected, even with specialized Seagate's Tools, or DriveDetect utils).

This is it, so-called "BSY" failure. The HDD is brick now :-)

Now I've restored my system partition from backup and waiting for my friend to solder the RS232-to-TTL (COM - to - service connector) signal convertor. I've also found the needed Seagate service commands to unbrick the HDD with BSY error.

Please check whether your HDD is affected and in any case: BACK your data UP regularily!

Labels: , , , , , ,

This page is powered by Blogger. Isn't yours?