Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
August 1st, 2012, 9:55
OK. Download this Windows program (sorry), it works on Windows XP:
http://files.hddguru.com/download/Software/Seagate/ST_MEM_FREE_28_12_06.ZIPIt works like terminal, plus can run scripts.
Copy attached .CMD script, use txt file for comparison (it is my working script, but base is deferent). Check for my mistakes calculating offset!
I don't know if your adapter works at higher speeds, it is why I set default speed 9600bps, but downloading takes couple hours. I use 115200 (inside script) and download twice!
Report any errors, save log file.
Don't forget to press 'Connect' button and test communication first.
- Attachments
-
- ReadSA.ZIP
- (679 Bytes) Downloaded 885 times
August 1st, 2012, 14:04
Hi SAJunky. Many thanks for the program. Will have to setup a XP box first.
Just to know: this program will copy SA (Sytem area) into a file?
I guess that you took start adress from:
Sys= 0F68E-0F70D 0280 SPTK on sys trks
What are the other parameters for?
R_SECTORS/F6A3/0/200/0/280/APP_0_F6A3.trc/1/1
August 1st, 2012, 14:29
SAJunky: SPEED/115200 works; copying in progress.
Why to read twice?
August 1st, 2012, 15:25
I have executed the alpine_rd.cmd Skript. Results attached.
- Attachments
-
- ST380011A-SA-Download.zip
- Download of SA area of ALPINE ST380011A using alpine_rd.cmd
- (391.68 KiB) Downloaded 683 times
August 1st, 2012, 19:24
I see that two copies of APP are identical. Also I don't see visually problems with CERT code. On the same track there are two copies of CERT Table, there are identical. No error during reading. Could you please re-run script, but comment out reading APP tracks (it was verified with copy). Then compare files if any difference, just to make sure. And I will analize CERT track in meantime.
Some sectors of Vendor data has been replaced with some defaults and these system mesages bugger me, but BlackST suggests that we shouldn't worry about Vendor track, it is not importand for data copying.
Wy reading twice? As serial interface has no error checking and it could be un-reported surface reading errors (we don't know).
August 2nd, 2012, 2:25
SAjunky wrote:but BlackST suggests that we shouldn't worry about Vendor track, it is not importand for data copying.
NO !! I said some
stuff is not necessary for the drive to start, not some
STUFF.
I care about what
I say not about people
understand or
want to understand , then it's not my problem / my drive anymore.
August 2nd, 2012, 5:06
BlackST wrote:NO !! I said some stuff is not necessary for the drive to start, not some STUFF.
My bad, sorry.
It was my initial thinking about errors on system track as indicated by:
- Code:
Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.009d
It points to the Vendor track. And now I am back on the right track, thanks.
Waiting for verification of reading, in meantime will try to find out which sectors generate errors.
August 2nd, 2012, 12:47
Your vendor track is stuffed, but not with a garbage, but some intentional action. Here what I found.
In the image of my drive I see three copies of STUFF sector. The first one, I call it STUFF1, is placed on sector 4 (file offset 0x800). Second one, STUFF2 is at sector 9 (0x1200). STUFF3 is at sector 0xB (0x1600).
My copy 1 and 3 are identical, but differs to STUFF2 only in two places:
0x6C/D FF FF against 00 00
0x1C4 02 00 against 00 00
Your STUFF1 and 3 are also identical, but it contains rather odd disk name
ST1Disk2H instead usual
ST380011A as found in STUFF2
What is more interesting that STUFF2 is identical in my drive and yours. It make me thinks it is possible to restore your STUFF1.
Not sure if my STUFF1 is correct, will check with other firmware and keep you updated.
August 2nd, 2012, 16:03
Your suggestion to repeat the downloads was correct. It shows that vendor track is different each time read due to read errors.
This time I was around and recognized that the drive stuck many times. Read Results attached.
Since read of the other tracks lead to identical results without sticking my conclusion (ok could be dynamically modified too) is that media is damaged in the area of the vendor track. So a rewriting of it will probably not work.
If we need this dammed track what are the options now?
- try to overwrite it anyhow
- is it possible to relocate the vendor track
- extract the raw sector data via the terminal mode and put data it into a "drive emulator"
(B.t.w. it seems that adjacent bytes of some strings are swapped)
- Attachments
-
- ST380011A-3-Downloads.zip
- 3 Downloads of SA
- (805.66 KiB) Downloaded 724 times
August 2nd, 2012, 19:09
Actually you need to overwrite track in an attempt to repair it. You can't relocate Vendor track, it has a fixed offset. But you can move base in the process called selfscan, assuming your data has been moved out already and safe, as it will destroy user data space.
Problem is now which sectors to write over and what data. I am working on it. And we need a script to write it back of course. After that (or before - not sure yet) you will have to regenerate SMART (1>N1) and clear G-List (T>i4,1,22).
I am unable to download the file, my Internet feed is eratic. Will come back tomorrow.
August 2nd, 2012, 23:40
Are you REALLY SURE about what you are saying?
August 3rd, 2012, 14:35
I see your STUFF is always the same. Writing occurs in sector 3 (0x400) and more writing outside Vendor (0x12 sectors) area. Vendor area except sector 3 is exactly the same, so reading in this area is stable..
I managed to download firmware for similiar drives. I found is that on healthly firmware STUFF1 equals to STUFF2 and STUFF3 is empty. So my STUFF1 also shows deterioration, It is why is called 'current' STUFF.
Now it a time for experiments. My drive had been backup and taken out of service about 2 years ago, I don't afraid losing data. I will try with SMART, empty G-List, then see when my data is unrecoverable and what happen if I replace STUFF with copy.
On your side I would suggest to start copying. Read a qoute below. Overheard from some other forum, Pro's are talking...
If you are ready and have started to clone and it is slow you have to leave it and let it go I just finished to clone 1TB Hitachi HDD that was terrible and it took me 19 days to do this one. I had a Toshiba that took me 45 days to do but in all I got all data off the drives and back to the clients.
There is no way to speed up cloning. You repair the problem then you have to allow the drive to clone and read the data off of it you can not force a read from data and regen a translator if you expect to get your data back on this drive. You have to leave to not force DR and allow the broken drive to clone. I know it is not fun to sit around and wait for a drive to clone but on some drive you can not even clone 1 million sectors in 24 hours. It depends on the heads and the degration on the platters and how many sectors are totally bad and have to be read more than once. You have to leave to be patient when it comes to this.
You can try and clone backwards on this one and see if you can read better the end of the drive and work forward. At times I had to clone backwards, then make a major jump in sectors, then clone from middle to certain point then clone from middle to back point. It all depends on the drive and how you can work around these problems. That is what you need to look at when cloning on how you can do this one. Sometime one area is so slow you think it will never finish. At times I try and skip these areas to work around them later on so that I can get the most data off the HDD as possible and go back to the problem area and only work in them. Try this one
August 3rd, 2012, 15:04
If you are ready and have started to clone and it is slow you have to leave it and let it go I just finished to clone 1TB Hitachi HDD that was terrible and it took me 19 days to do this one. I had a Toshiba that took me 45 days to do but in all I got all data off the drives and back to the clients.
There is no way to speed up cloning. You repair the problem then you have to allow the drive to clone and read the data off of it you can not force a read from data and regen a translator if you expect to get your data back on this drive. You have to leave to not force DR and allow the broken drive to clone. I know it is not fun to sit around and wait for a drive to clone but on some drive you can not even clone 1 million sectors in 24 hours. It depends on the heads and the degration on the platters and how many sectors are totally bad and have to be read more than once. You have to leave to be patient when it comes to this.
You can try and clone backwards on this one and see if you can read better the end of the drive and work forward. At times I had to clone backwards, then make a major jump in sectors, then clone from middle to certain point then clone from middle to back point. It all depends on the drive and how you can work around these problems. That is what you need to look at when cloning on how you can do this one. Sometime one area is so slow you think it will never finish. At times I try and skip these areas to work around them later on so that I can get the most data off the HDD as possible and go back to the problem area and only work in them. Try this one
[/quote]
Let me guess... The author of this text is "poehere"???
August 4th, 2012, 8:06
In other case of Momentus 5400.3 with EC=43 errors and STUFF problem:
http://forum.hddguru.com/seagate-momentus-5400-problem-t11419.htmlBlackST wrote:
1) fix STUFF 2) check and eventually fix firmware-must at least start decently 3) selfscan. In this order.
Selfscan is definitely not an option, other has to be tested if data remains intact in result of fixing. At least we know that in this order.
1. To fix STUFF:
T>F
SetStuff->ASCIFE
a) Result: Unknown type 03
Answer: Get an identical model and copy vendor track, first 4 blocks are sufficient.
b) Result: STUFF does change, but " Not configured-0 "
Answer: Change type using T>Y
Is not better to get identical model and copy of Vendor track, the first 5 sectors (including STUFF) instead of generating default STUFF?
I found such firmware where STUFF sector is identical with our copy which survived in sector 9. 'Our' means mine and OP, both identical.
August 4th, 2012, 8:16
labtech wrote:Let me guess... The author of this text is "poehere"???
Can you sleep without it?
I have bad Internet connection, lot of lost packets, Googled to some forum, site didn't respond, so readed from cache. It turned to be closed user group, not accessible to the public. I am not going to hack into the forum just to satisfy your curiosity. Sorry pal...
August 4th, 2012, 9:19
SAjunky wrote:labtech wrote:Let me guess... The author of this text is "poehere"???
Can you sleep without it?
I have bad Internet connection, lot of lost packets, Googled to some forum, site didn't respond, so readed from cache. It turned to be closed user group, not accessible to the public. I am not going to hack into the forum just to satisfy your curiosity. Sorry pal...
Okay...
Don't see anywhere where you were asked to do anything.
My statement was intended as a joke and to somewhat give a hint of reinforcement in what you are explaining in your post by using somebody else's explanations, which I believe were written by poehere. Poehere is a reputable experienced member, which is a positive thing.
So be easy with the smart comments, pal.
August 4th, 2012, 10:57
labtech wrote:My statement was intended as a joke and to somewhat give a hint of reinforcement in what you are explaining in your post by using somebody else's explanations
You are welcome, any hint is appreciated. Actually more by OP than myself, as I don't need to preserve data. I can go with selfscan if I wish...
However perhaps you should know that I understood your post completely in reverse, I saw on many occasion on this forum that there are real Pro's and not so real. Therefore your reinforcement was received in reverse. Now it gets clear, thanks pal. English is not my home language, take adjustment to this fact, please.
August 4th, 2012, 11:11
English is not my native language, either

. Salut!
August 4th, 2012, 11:59
labtech wrote:Let me guess... The author of this text is "poehere"???
Yes
August 4th, 2012, 16:17
Hello SAJunky: Thank you for your research. Before I gonna fix Stuff I would like to comment some observations. In my Vendor track there are 5 occurances
of similar sections that start with a S/N and a disk name. The S/N in Stuff 2 have different leading characters.
Copying Stuff 2 into the other positions will at least lead to overwrite the correct S/Ns with a wrong one -maybe not a problem but who knows.
0x0800 (Stuff 1)
0x0814 S/N
0x0836 "ST1Disk2Head"
0x0E00
0x0E14 S/N but first 2 bytes replaced with 01 00
0x0E36 "ST1Disk2Head"
0x1200 (Stuff 2)
0x1214 S/N but first 2 bytes replaced with <whitespace>
0x1236 "ST380011 A"
0x1800 (Stuff 3)
0x1814 S/N
0x1836 "ST1Disk2Head"
0x1A00
0x1A14 S/N
0x1A36 "ST1Disk2Head"
I really do not know if the STUFF sections are mere redundancies. Maybe I should check my other ST30011A drive. The vendor track of this drive will probably not work in OP (was that the term?) since drive has different firmware (8.01). But maybe I should have a look into that.
Powered by phpBB © phpBB Group.