01-07-2009 12:43 PM - edited 01-07-2009 01:02 PM
I bought this drive in 2006. I had three partitions on it (C/D/E, C has windows installed and the other two are for data storage) I recently experienced harddrive performance down in D partition when I tried to open some files, drive keep on reading, I used windows chkdisk and successfully solved this issue. After a couple weeks, I experienced the similar issue when I tried to open some music files on E partition. I then tried to do chkdisk again, but chkdisk stopped in the middle, I powered off the computer and then cannot go to windows again.
I chose to install my windows on another seagate 750GB SATA and my DELL BIOS can successfully identify this 500GB SATA but when I go into windows, this 500GB cannot be recognized. I have no way to use partition magic or some other tools to extract documents inside. Really feel frustrated as there are lots of important documents in my D partition and I have no backup yet.
I now tried Seatools DOS and when I did short test, it only went 10% and freezed there. I tried long test, it reported 3 times 99 error close to 33% location, I then repaired them all and tried the long test again. the long test always failed by the reason, "the drive is not responding to commands , check cables and drive power connection." close to 34% location. I am sure my cable and drive power has no problem.
Any input? thanks
03-06-2009 09:13 AM
I have the same problem on a different drive. Drive works relatively OK with occasional ECC fails. I want to make a image to another drive and replace the old one.
the problem is that when any program tries to read the drive and gets to about 11%, the drive freezes and i get this error msg.
i don't understand why seatools doesn't try to just mark that area as bad and move on, instaed of failing the whole test. i can hear the drive retrying and clicking before it quits.
this is shoddy firmware error handling!
04-12-2009 01:05 PM
If you got any answers or found any way to solve this problem, i'd be interested too, because i seem to have the same problem and would like to make sure there's no solution before sending it to seagate for warranty.
Thanks in advance.
05-15-2009 09:52 PM
If the drive is only locking up on a USB adapter, get an internal card!
As annoying as it sounds, you can just copy of segments of sectors to seperate image files, then recombine them.
1) Make note of exact sector ranges that it fails to read at. Yuck, this will take lots of power cycles on a known bad drive. USB adapters ironically would make this easier but often CAUSE the 'lockup' behaviour on errors. I've had to directly connect several laptop drives to my desktop's IDE controller to get around this issue before I had some magnet donors. Big red X marks the spotty drives.
2) Copy areas outside those ranges to seperate files and make note of which filename went where.
3) Make "dummy" files for the bad areas of the drive. Dummy files are just full of zeros and the same size as if you had been able to copy the sectors.
4) Append all those files in the right order, into a single file. Use the "Copy" command in a command prompt, or even easier: http://www.freebyte.com/hjsplit/ This utlity will 'unsplit' a group of files. Use the 'split' feature on a sample file to get an idea of what filenames it expects. Your source files should alternate between the good data and the gaps. Odd/Even, OK?
5) Copy that image file to the sectors on new drive or use a program like Getdataback on the image file.
R-Drive's image tool can allow you to copy even with errors (it replaces them with zeros) but is useless if the drive itself keeps locking up even when reading areas PAST the errors. So would DriveImage XML. Yes, it's a hardware/firmware issue. :/ How funny that it's trying to protect you from reading with a potentially crashed head. If the data on the drive is financially important, than don't do any of these steps and just take it to DTI.com or such. A local or by-mail data recovery company is much safer.
Keep VERY GOOD notes as otherwise all those files you make are worthless if appended in the wrong order. Using HJ-Split will help people who don't know the command prompt/DOS shell, but you will probably want to name your files like it expects to see them to save time pointing it to the next file in your list. This process is such a pain, that I would highly recommend just paying someone to do it if you had trouble reading any of those steps.
A good (nonfree, but very easy interface) tool for reading raw sectors is Disk Explorer by Runtime software. 010 Editor, TurboHex, XEDIT, or WinHex would all also work. http://www.new-utilities.net/nt_disk_viewer.html has a freeware one that I haven't tried. http://en.wikipedia.org/wiki/Disk_editor has a good selection - I'm going to make it even longer, heh. There's even a free-to-install tool from Microsoft. Just use any that support raw disks and the ability to select a range, to read out the sectors. This is a tedious process, so find one that you like best. Try them until you find one that you can live with. I know that Disk Explorer has a simple interface for selecting sectors, but the others will work. Be aware that some programs let you choose the byte offset in a sector that it ends and starts at and not just the sector. This little gotcha means you have to make sure that Disk Explorer says "0" to start and "1FF/511" to end!
A command line interface tool could make it easy to create a batch file to extract and combine the sector images into one big disk image but I don't know where one is... DD from Linux would work on my Ubuntu desktop. Good luck with data recovery.
06-30-2009 07:33 AM - last edited on 07-14-2009 12:52 PM by AlanM
Having the same darn problem. It just seems like these problems are only surfacing recently???
Looking through the problems of the newer drives, something about the logging system or smething failing on the 7200.11 drives, I took a close look at the HD info in seatools. It noted there 'Logging feature Set it not supported'. I know my drive is kinda old... its a 80Gb ST380011A IDE drive. Could this logging also be causing all these problems?
07-02-2009 12:55 PM
Yes and no... This is an issue only for some drives from specific batches if I understand right. It seems that there was a subtle firmware issue that only happened under very specific conditions. When the log file fell unto certain locations, the drive's logic enters an impossible condition to recover from, no matter how many times you cycle the power. The fix was to replace the firmware with a version that had the software crash fixed. Hard to update firmware though when the drive is unrecognized. Haha that is annoying. That thread you mention seems to cover most of the technical reasons.
Possibly no, because not all drives fail for the same reason. Some drives just prematurely fail randomly no matter how hard Seagate tries to prevent this - it's the nature of magnetic drives. Power surges, bad power supplies, overheating due to poor cooling, dropping drives (especially when spinning!), defective chips/capacitors, HUGE magnetic fields along the lines of junk yard cranes, sitting on top of an industrial electric motor, and so on. There are a lot of issues not nearly so dependant on the design.
It's actually kind of interesting, since firmware is one of my more esoteric interests as a programmer... Most people could care less so long as it doesn't happen to their drive.
If you have a backup (say, a mirrored drive of the same size but different brand) then you can just send in the entire drive and they're cross ship you another drive if I understand right. Might need a credit card unless you want to go without cross shipping. Of course, you have to have an RMA number. Windows has something called VSS (volume shadow copy service) that automatically mirrors changes to another volume. Other OSes have something like that. Another option is RAID where the backup is automatic. The problem with these two is if a fire or something happens... You lost both drives. There are methods to use a network drive to backup the contents... usually when the user is not logged in/screensaver is on/at night. There is a technology called NAS (Network array storage) which is like RAID but over your network. What's sweet is that you can enable encryption (usually Virtual Private Networking aka VPN) and use a business broadband connection to backup across the world.