All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 11 posts ] 
Author Message
 Post subject: ST500DM002 stays busy
PostPosted: February 24th, 2016, 17:13 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
Hello,

i'm not able to get this ready
Sounds good. - looks good
but never gets ready:
Can not Ctrl+Z - no terminal command accepted.
Tried shortening - nope - tried another pcb - nope

Boot 0x10M
Spin Up[0x00000000][0x0000B67C][0x0000BA10]
Trans.

Rst 0x10M
MC Internal LPC Process
Spin Up
(P) SATA Reset

Any Ideas`?


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 17:16 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
ohh.. i'm so bad - found another Post with same problem, maybe i had wrong shorting channels or something like that, i'll try


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 17:56 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Usually you have to time the shorting of the read channel just right on these. You can't do it before or right at power on, but rather a few seconds after. Then as soon as you've got terminal access, get in and disable everything in System file 93.

Have fun! :D

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 18:08 
Offline

Joined: March 19th, 2015, 15:01
Posts: 1387
Location: isreal
like "data-medicsĀ®" said there is an exact timing needed to short the read channels
see here Where and how to short Seagate F3 drives


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 18:11 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
yes thx, i got this - just had wrong channels, no i've done the "No HOST IS-Ready Status Flags" procedure. drive spins up "normally" - having Initiatemarkpendingreallocaterequest for disc_lba now

reading ID and SA is OK, saved everything so far i can.

but on all sectors he means "UNC" and black block...

what i've forgotten?


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 18:21 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Did you disable everything in system file 93 like I mentioned?

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 18:29 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
i disabled everything yes, but if i turn off an on again it's here again, but pressed write.


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 18:34 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
ok now no more of this warnings after saving second sys 93..., but still can not clone data with DE


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 24th, 2016, 20:57 
Offline

Joined: July 23rd, 2015, 6:40
Posts: 107
Location: Austria
Thx to jermy ;) - after rewriting sysfile 28 - everything OK again...


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: February 25th, 2016, 15:13 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Good to hear that it's working now. Often with these you only get to do one operation per power cycle and only within a few seconds of it coming ready. Sometimes you'll need to read/modifly the file, power cycle, possibly short read channel again, and then write the file. You'd be surprised how often they go unresponsive between reading system file 93, and trying to write it back.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: ST500DM002 stays busy
PostPosted: July 22nd, 2016, 23:48 
Offline

Joined: May 3rd, 2015, 18:16
Posts: 72
Location: Detroit
Im having this exact problem data-medics describes. I too discovered that the only way to read/write sys files is to turn of/on the drive with a small 1-2 second windows after initialization. I've already unchecked all items in sys93 and that only solved it for a few minutes but now it back to staying BSY again. What can I try? I also noticed there are many sys93 files listed.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 11 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 12 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group