Hay!

I think I have a common problem here, but I'm not 100% sure, because I lack some info and I can't find it on the internet or on this forum.

Basically, my Seagate FreeAgent Go (portable) has stopped working just like that. Firmware? bridge? Anyway, here's the big picture to make it simple:
- Windows does not detect the hdd
- Seatools does not detect the hdd
- I talked with Seagate and convinced them to let me open the casing to get my data back then send back the drive for RMA since I'm an expert and know how to do it. Turns out I'm not haha!
- I opened the casing and plugged it directly on my computer, but Windows does not detect it, neither SeaTools
- The BIOS detects it (the first time I plug it, then not anymore after reboot) as a 0MB drive. The 0 LBA problem or I got ripped off and bought a 0MB hard drive darn it?
- I have checked all the cables, but they are new anyway.
- I think it may be the 7200.11 firmware problem that is so common on the barracuda but I can't find if my hdd is using 7200.11
-Could a jumper change something as I have two other SATA drives and there could be a conflict?

So I have found the tutorial on how to solder the RS32 connector with the 2032 battery an all but before trying it I just wanted to know what was your opinion just in case you think it would be something else. Here are some screenshots to understand better the situation with the model number to guess if it's 7200.11 and everything else you need (don't mind the fact that it's SATA3 on first pic and SATA4 on second, i tried different ports):

First question: Is your data important to you?
If you answer yes then I would be very carefull and not rush in and apply the lba0 or busy fix.

If you look at the main drive label it will tell you which series of drive you have. If in doubt take a photo and post it.

Another observation.......your other drive on sata 2 port is most likely a 7200.11 drive and with the sd15 firmware is at great risk of failing!!!

Seatools does say SD15! Seatools even says that a firmware update is available for that drive, SN 9QM4TTLH but I never updated it since I follow on of my favorite principles in computer; "If it ain't broken, it ain't need fixin'". I've had that drive for like 3-4 years and it never failed. Also checked seagate firmare updates and it says that I don't need updates with the 9QM4TTLH SN???


Anyway, about the other drive, I already checked the label and have no idea if it's 7200.11, so I'm posting it here.
The DATA is semi-important so that's why I posted here to see everyone's opinion before trying any rash solution.

Thanks btw

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

Thanks, but how come in the RS232 tutorial, it says this might fix the LBA 0 problem?

If this won't fix it, anybody has any other solution, provided my serial number?

LBA0 is not a problems it's a symptom
Problems can be different, some can be fixed by the tutorial and some cannot
But LBA0 is not a FW bug and have nothing to do with busy bug

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

I would update the firmware of your SD15 7200.11 drive, whether or not the serial number checker tells you to. If the updater rejects your drive, there is an easy way to forcibly update it from the command line.

http://forums.seagate.com/t5/Barracuda- ... 716#M21147

As for your problem drive, use the "tutorial" to at least retrieve a terminal report from the drive. Instead of a TTL RS232 interface, or a Nokia USB-RS232 cable, you could try the following device:

Prolific USB to TTL Logic Cable (US$10):
http://www.serialstuff.com/products/Pro ... Cable.html

_________________
A backup a day keeps DR away.

WOW, this is awesome!! SO all I need would be to connect the RX, TX and ground on the hard drive and nothing else, then do the steps with hyper terminal (skipping the RS232 connection steps)? OR are you talking about something else when you say a "terminal report"?

Thanks a lot!

MArco

The "terminal report" is a diagnostic error report that helps determine what is actually wrong with the drive. If the report is consistent with the typical "0 LBA" problem, then the procedure at Loki's URL should work.

_________________
A backup a day keeps DR away.

Ok, I just got the usb to ttl wire, but all I find are dozens of tutorials on how to fix a problem but nothing to actually get a report or find what the problem is, like going to the garage to change your oil before even knowing what what's wrong with your car. Is it really called a terminal report or there is another expression?

Type Ctrl-Z and capture the output.

_________________
A backup a day keeps DR away.