ST3000DM001...BSY

[Nick Butner]

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

[Tim Homer - Desert Data Recovery]

With this error - RECOV Servo Op=0900 Resp=0005 - pretty much certain its head failure or media damage. Even if you can read the SA, it does not mean you can read the data area.

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To post to this group, send email to datarecovery...@googlegroups.com.
Visit this group at https://groups.google.com/group/datarecoverycertification.
For more options, visit https://groups.google.com/d/optout.

[Tim Homer - Desert Data Recovery]

You may also have luck starting DE with the Seagate utility option and checking the pending bug box. May solve your issues.

 

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Thursday, June 29, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: ST3000DM001...BSY

 

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

--

[PCLAB]

Try to edit sys 93 file and disable all functions.

[Nick Butner]

I thought the Fail servo op was head issue.  Originally, the drive output that error twice and spun down.  Thought it was heads, swapped them and now has the current error. Possibly media like you said.  As for the pending bug in utility, is that an option for F3?  I dont see it. 

On Thursday, June 29, 2017 at 3:42:07 PM UTC-4, Tim wrote:

With this error - RECOV Servo Op=0900 Resp=0005 - pretty much certain its head failure or media damage. Even if you can read the SA, it does not mean you can read the data area.

 

From: datarecovery...@googlegroups.com [mailto:datarecoverycertificati...@googlegroups.com] On Behalf Of Nick Butner
Sent: Thursday, June 29, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: ST3000DM001...BSY

 

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertification+unsub...@googlegroups.com.

[Nick Butner]

Forgot to mention I tried that too. 

[Tim Homer - Desert Data Recovery]

Sorry you are right the pending bug is not available for an F3.

If you changed heads, did you swap head adaptives?

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Friday, June 30, 2017 5:19 AM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Cc: t...@desertdatarecovery.com
Subject: Re: ST3000DM001...BSY

 

I thought the Fail servo op was head issue.  Originally, the drive output that error twice and spun down.  Thought it was heads, swapped them and now has the current error. Possibly media like you said.  As for the pending bug in utility, is that an option for F3?  I dont see it. 

On Thursday, June 29, 2017 at 3:42:07 PM UTC-4, Tim wrote:

With this error - RECOV Servo Op=0900 Resp=0005 - pretty much certain its head failure or media damage. Even if you can read the SA, it does not mean you can read the data area.

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Thursday, June 29, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: ST3000DM001...BSY

 

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To post to this group, send email to datarecovery...@googlegroups.com.
Visit this group at https://groups.google.com/group/datarecoverycertification.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

[Nick Butner]

OK, copied head adaptives from donor ROM image, hit apply, re-powered, still same terminal output.  I do have a second donor I could try as well, from what I read it could take multiple head swaps to get it working with this family.

On Friday, June 30, 2017 at 10:57:32 AM UTC-4, Tim wrote:

Sorry you are right the pending bug is not available for an F3.

If you changed heads, did you swap head adaptives?

 

From: datarecovery...@googlegroups.com [mailto:datarecoverycertificati...@googlegroups.com] On Behalf Of Nick Butner
Sent: Friday, June 30, 2017 5:19 AM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Cc: t...@desertdatarecovery.com
Subject: Re: ST3000DM001...BSY

 

I thought the Fail servo op was head issue.  Originally, the drive output that error twice and spun down.  Thought it was heads, swapped them and now has the current error. Possibly media like you said.  As for the pending bug in utility, is that an option for F3?  I dont see it. 

On Thursday, June 29, 2017 at 3:42:07 PM UTC-4, Tim wrote:

With this error - RECOV Servo Op=0900 Resp=0005 - pretty much certain its head failure or media damage. Even if you can read the SA, it does not mean you can read the data area.

 

From: datarecovery...@googlegroups.com [mailto:datarecoverycertificati...@googlegroups.com] On Behalf Of Nick Butner
Sent: Thursday, June 29, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: ST3000DM001...BSY

 

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertification+unsub...@googlegroups.com.

To post to this group, send email to datarecovery...@googlegroups.com.
Visit this group at https://groups.google.com/group/datarecoverycertification.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertification+unsub...@googlegroups.com.

[Tim Homer - Desert Data Recovery]

After you applied the adaptives to the ROM image, did you upload it back to the drive?

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Friday, June 30, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Cc: t...@desertdatarecovery.com
Subject: Re: ST3000DM001...BSY

 

OK, copied head adaptives from donor ROM image, hit apply, re-powered, still same terminal output.  I do have a second donor I could try as well, from what I read it could take multiple head swaps to get it working with this family.

On Friday, June 30, 2017 at 10:57:32 AM UTC-4, Tim wrote:

Sorry you are right the pending bug is not available for an F3.

If you changed heads, did you swap head adaptives?

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Friday, June 30, 2017 5:19 AM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Cc: t...@desertdatarecovery.com
Subject: Re: ST3000DM001...BSY

 

I thought the Fail servo op was head issue.  Originally, the drive output that error twice and spun down.  Thought it was heads, swapped them and now has the current error. Possibly media like you said.  As for the pending bug in utility, is that an option for F3?  I dont see it. 

On Thursday, June 29, 2017 at 3:42:07 PM UTC-4, Tim wrote:

With this error - RECOV Servo Op=0900 Resp=0005 - pretty much certain its head failure or media damage. Even if you can read the SA, it does not mean you can read the data area.

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Thursday, June 29, 2017 12:23 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: ST3000DM001...BSY

 

World's greatest drive...Have ST3000DM001 stuck in BSY with terminal access on PC3000.  Have backups of important sys files and have tried clearing NRG list, translator regen, checking sys files for damage.  Still stuck in BSY with No Host FIS error.  Drive has donor heads which can read/write successfully and a donor board with the ROM swapped.  Terminal output attached, any ideas would be great.  Ace Tech support hit a wall and needed to remote in which is not an option.

Nick

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To post to this group, send email to datarecovery...@googlegroups.com.
Visit this group at https://groups.google.com/group/datarecoverycertification.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To post to this group, send email to datarecovery...@googlegroups.com.
Visit this group at https://groups.google.com/group/datarecoverycertification.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.

To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

[Nick Butner]

My fault, saved it as a separate rom image and wrote it over terminal. Re-power, still same output.

[Tim Homer - Desert Data Recovery]

Put the donor heads back in the donor and see if the drive initializes. If not then media damage to the patient drive is most likely killing the heads.

-----Original Message-----
From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of Nick Butner
Sent: Friday, June 30, 2017 1:32 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>

[anaesarora Singh]

Did you try changing the PCB,I was always successful after changing the PCB and swapping ROM.

[Tim Homer - Desert Data Recovery]

If you won’t let anyone log in to take a look, there is little anyone can do.

 

From: datarecovery...@googlegroups.com [mailto:datarecovery...@googlegroups.com] On Behalf Of anaesarora Singh

Sent: Wednesday, September 13, 2017 11:00 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>

Subject: Re: ST3000DM001...BSY

--