Heya all. Decided to share experience. Have a ST3000DM001 3TB grenada. Comes ready with RECOV Servo Op=0600 Resp=0005 in terminal. On ID attempt goes BUSY. CTR Z gives nada. I noticed that i get a second of functionality after power-up and then only busy after. Power on and immediately go EDIT HDD ID. Drive IDs before the action times out so it gives access. But changes made will not stick cause of busy issue. Make sure you check power cycle before applying changes option. Disable all but extra diag option did not help me. Was still busy , but with a lot more stuff in terminal . namely this :
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x001ED24FC2-001ED256C5 - 0x00091689-0009168E Count 3000
(DOS) Refresh Start.
(DOS) Marginal Read: 001ED24FC2
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 001ED24FC2!
(DOS) Read Error - 001ED24FC2
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x001ED24FC3-001ED256C5 - 0x00091689-0009168E Count 3000
(DOS) Refresh Start.
(DOS) Marginal Read: 001ED24FC3
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 001ED24FC3!
(DOS) Read Error - 001ED24FC3
Lba accesses FUBAR cause busy issue is still plaguing the drive.
DISABLE IDLE in EDIT HDD ID tab solved that issue. Full LBA access at normal speed.
GL all.
ST3000DM001 3TB BUSY on ID attempt
Moderator: Nick_TS
Re: ST3000DM001 3TB BUSY on ID attempt
unfortunately i have same problem with seagate Granada 500gb, 1TB and 2TB i have similar post in this forum but no one have practical answer.
i think all of this series (Granada) have a same issue.
hope ACE find and submit good solution for this series!
look at this issue:
http://acelaboratory.ru/forum/viewtopic.php?f=38&t=8039
need to short PCB point but i don't know where is the exact point is!
i think all of this series (Granada) have a same issue.
hope ACE find and submit good solution for this series!
look at this issue:
http://acelaboratory.ru/forum/viewtopic.php?f=38&t=8039
need to short PCB point but i don't know where is the exact point is!
Re: ST3000DM001 3TB BUSY on ID attempt
Heya. If you send the picture to http://ts.acelab.eu.com/ guys - they will 100% identify the read / write channels for you. In addition i had limited success in some cases with spamming CTR Z during spin up/calibration. Just spaaaaaaaaam it. I think it acts like introduction of noise that prevents proper / full calibration and SA read. And may give u ready.
As for the link you posted to me , weeeeel , something is very fishy there.
8. i checked the V40 command and NRG list had entries.
9. in PC3K i cleared NRG list.
10. run again m0,2,2,,,,,22 command and than N1 command.
This part makes no sense to me. NRG has to be saved BEFORE translator is recalculated and reintroduced into new one. AFAIK runing m0,2,2,,,,,22 clears it. Thats what causes problems with limited LBA access after trnaslator regen. New regen does not take NRG into account. I would not suggest following that step by step solution.
As for the link you posted to me , weeeeel , something is very fishy there.
8. i checked the V40 command and NRG list had entries.
9. in PC3K i cleared NRG list.
10. run again m0,2,2,,,,,22 command and than N1 command.
This part makes no sense to me. NRG has to be saved BEFORE translator is recalculated and reintroduced into new one. AFAIK runing m0,2,2,,,,,22 clears it. Thats what causes problems with limited LBA access after trnaslator regen. New regen does not take NRG into account. I would not suggest following that step by step solution.
Re: ST3000DM001 3TB BUSY on ID attempt
Practical suggestion for ur issue is as follows:
1) Achieve ready status. Send picture to http://ts.acelab.eu.com/ so the can ID read write channels for you to short , or try spamming ctrl z.
2) Backup all system data and modules to be safe.
3) Run V40 ( checks NRG )
4a) V40 gave no entries - run regeneration of the translator and copy ur data out.
4b) V40 gave entries. This part is fuzzy for me. The idea is copy the NRG , recalculate translator and somehow reintroduce original NRG. Someone on the forum said "Hide original NRG to slip list and thats it. But i never personaly did it.
1) Achieve ready status. Send picture to http://ts.acelab.eu.com/ so the can ID read write channels for you to short , or try spamming ctrl z.
2) Backup all system data and modules to be safe.
3) Run V40 ( checks NRG )
4a) V40 gave no entries - run regeneration of the translator and copy ur data out.
4b) V40 gave entries. This part is fuzzy for me. The idea is copy the NRG , recalculate translator and somehow reintroduce original NRG. Someone on the forum said "Hide original NRG to slip list and thats it. But i never personaly did it.
Re: ST3000DM001 3TB BUSY on ID attempt
Alexii wrote:Practical suggestion for ur issue is as follows:
1) Achieve ready status. Send picture to http://ts.acelab.eu.com/ so the can ID read write channels for you to short , or try spamming ctrl z.
2) Backup all system data and modules to be safe.
3) Run V40 ( checks NRG )
4a) V40 gave no entries - run regeneration of the translator and copy ur data out.
4b) V40 gave entries. This part is fuzzy for me. The idea is copy the NRG , recalculate translator and somehow reintroduce original NRG. Someone on the forum said "Hide original NRG to slip list and thats it. But i never personaly did it.
for ST5000DM002 i sent the PCB pic to acelab yesterday and they answer me very fast. they marked me 2 pair of the points in the picture so i shorted the first pair points but the result wasn't good and then shorting the second points also the action wasn't successful!
i think this kind of hdd series has some problem in firmware or sys file.like freeplay 2.5" series that should load 17A.bin file i think this Granada series may need to use some similar method.
Re: ST3000DM001 3TB BUSY on ID attempt
Alexii wrote:4b) V40 gave entries. This part is fuzzy for me. The idea is copy the NRG , recalculate translator and somehow reintroduce original NRG. Someone on the forum said "Hide original NRG to slip list and thats it. But i never personaly did it.
You can select Defect List and create a new list, at this point it will ask type of defect list, one option is NRG, you can re-create NRG with this option. Other option is to select other option and after adding defects you can select option to hide to slip list (sorry that answer may be vague, I am writing this through memory and dont have access to PC3K right now to clarify exact options)
Re: ST3000DM001 3TB BUSY on ID attempt
Grenada are not great drives. In my experience the worst (so far) of F3 series.
Shorting of these can be tricky but I also find that adjusting of head map in ROM can help in some cases, strange thing is in some cases after restoration of native map drive operated well...
I see some cases where drive seems fine and DRDY is reached but status register displays DWF on any ATA access, but serial access over terminal is fine. For this, I have not solved - is this the symptoms you have?
Shorting of these can be tricky but I also find that adjusting of head map in ROM can help in some cases, strange thing is in some cases after restoration of native map drive operated well...
I see some cases where drive seems fine and DRDY is reached but status register displays DWF on any ATA access, but serial access over terminal is fine. For this, I have not solved - is this the symptoms you have?
Re: ST3000DM001 3TB BUSY on ID attempt
AJ2008 wrote:Grenada are not great drives. In my experience the worst (so far) of F3 series.
I see some cases where drive seems fine and DRDY is reached but status register displays DWF on any ATA access, but serial access over terminal is fine. For this, I have not solved - is this the symptoms you have?
i agree with you Granada is not good HDD.i couldn't extract or repair any kind of this hdd's till now. all of them goes busy and for me no method is worked!
in this recent case when i power up the HDD in pc3k it is busy but after a while all other status register's goes blinking not green but red color.
i can access to ROM buy shorting target pins.
i will appreciate if you have any experience in how to work in ROM to change any element that help me to detect this HDD.
thank you
Re: ST3000DM001 3TB BUSY on ID attempt
AJ2008 wrote:Alexii wrote:4b) V40 gave entries. This part is fuzzy for me. The idea is copy the NRG , recalculate translator and somehow reintroduce original NRG. Someone on the forum said "Hide original NRG to slip list and thats it. But i never personaly did it.
You can select Defect List and create a new list, at this point it will ask type of defect list, one option is NRG, you can re-create NRG with this option. Other option is to select other option and after adding defects you can select option to hide to slip list (sorry that answer may be vague, I am writing this through memory and dont have access to PC3K right now to clarify exact options)
Bah =) Thank you =) Its funny how sometimes the simplest of things can escape one... NRG is usually small. Nothing really prevents me from manually opening new empty non res defect list and manually adding the sectors i previously saved =)
As for fuzzy I dag throug the PC3K UI in regard to NRG editing on a look out for the "hide to slip list" option and i never found it. But maybe i wasnt looking close enough.
Cheers AJ.
Re: ST3000DM001 3TB BUSY on ID attempt
Quick addition. I am playing with a 7200.6 drive as a test subject. A list of funky observations:
1) V40 gave 12 entries , but if you count em they are actually 18. Browsing defect tab of PC3K UI i found editing option for non res g list. The values there are same as V40 report.
2) Recalculated translator 1 time and checked V40 after regeneration. It had 4 defects there. Recalculated again and it showed 0.
3) With new translator and zeroed non res g list , i copied the old non res in. Ran V40 to make sure it stuck and yes indeed here are the 12 entries that are actually 18.
4) LBA access was only partial. The end of the drive that i could read before was unreadable now , even though V40 shows proper entries. So i guess i am missing something.
At the end of it all , i copied all the modules and sys files from database backup i made and now drive is at square one in terms of functionality. All the sectors i could read i still can and those i could not read i still cant.
Question. What did i do wrong ? Why new translator with reintroduced original non res G list gave me no funktionality?
Ty for ur time potential helper =))
1) V40 gave 12 entries , but if you count em they are actually 18. Browsing defect tab of PC3K UI i found editing option for non res g list. The values there are same as V40 report.
2) Recalculated translator 1 time and checked V40 after regeneration. It had 4 defects there. Recalculated again and it showed 0.
3) With new translator and zeroed non res g list , i copied the old non res in. Ran V40 to make sure it stuck and yes indeed here are the 12 entries that are actually 18.
4) LBA access was only partial. The end of the drive that i could read before was unreadable now , even though V40 shows proper entries. So i guess i am missing something.
At the end of it all , i copied all the modules and sys files from database backup i made and now drive is at square one in terms of functionality. All the sectors i could read i still can and those i could not read i still cant.
Question. What did i do wrong ? Why new translator with reintroduced original non res G list gave me no funktionality?
Ty for ur time potential helper =))
Re: ST3000DM001 3TB BUSY on ID attempt
Bump for assistance .
Who is online
Users browsing this forum: No registered users and 20 guests
