All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 14 posts ] 
Author Message
 Post subject: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:05 
Offline

Joined: June 26th, 2011, 19:38
Posts: 52
Location: United States
I have a ShrekLT drive that is behaving very strangely. I can get the drive into safe mode, load mod 11 and mod 1 and read out all firmware, but cannot get the drive to identify correctly in normal mode. i am attaching a picture of the DFL screen once I have booted to safe mode and loaded the modules.

When I try to access the drive normally, the drive does not identify correctly, but I can get access to the ROM.

Anyone have any thoughts as to what is going on with the drive? Is the ROM possibly corrupted? I tried a fix for a similar problem with this drive series but it did not work: http://forum.dolphindatalab.com/thread-1616.html.


Attachments:
SafeModeMod11.PNG
SafeModeMod11.PNG [ 48.52 KiB | Viewed 10005 times ]
Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:28 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
FWIW, I can check the ROM for you.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:43 
Offline

Joined: June 26th, 2011, 19:38
Posts: 52
Location: United States
Here you go.


Attachments:
ROM.zip [238.32 KiB]
Downloaded 322 times
Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:43 
Offline
User avatar

Joined: August 19th, 2007, 17:30
Posts: 1899
Location: In your hard drive.
0A.bin Read error - Heads map
0B.bin Read error - Flash Rom

_________________
Buy your friends Toshiba\Hitachi and your enemies Seagate.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:49 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Spildit wrote:
fzabkar wrote:
FWIW, I can check the ROM for you.


Those Shrek .... Remember the threads with tools having trouble reading ROM MODULES or correctly ID the active ROM module or whatever ?

Maybe it's something related ?

That's what I was thinking, although the error message isn't clear.

    0A.bin read error
    0B.bin read error

If it is reading the wrong copy of 0A, then it would encounter a bad checksum (for the heap map section). If 0B is in error, then why not look for 20B? Does "read error" mean that the module cannot be read at all, or can it mean that there is some problem with its content?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 17:58 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
ROM analysis attached. All seems OK. Module 20B is the active module, not 0B. That's a common bug/limitation in pro tools.


Attachments:
PeskyBit.rar [4.25 KiB]
Downloaded 338 times

_________________
A backup a day keeps DR away.
Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 18:02 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Sorry for the double post. BTW, the double line spacing is annoying, but I don't know how to prevent it.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 18:03 
Offline
User avatar

Joined: August 19th, 2007, 17:30
Posts: 1899
Location: In your hard drive.
0047 FFFF 00000800 01FFFE00 0003F4FE FFFFFE00 BAD

_________________
Buy your friends Toshiba\Hitachi and your enemies Seagate.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 18:25 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Spildit wrote:
thatdellguy wrote:
0047 FFFF 00000800 01FFFE00 0003F4FE FFFFFE00 BAD


It's inactive (0B). Shouldn't be a problem.

Active in 20B is ok :

0047 OK 00000800 OK 0003E4FE 00000000 OK


Yes, that's how I see it. Some tools, including PC3K, incorrectly report that module 47 is bad. That's because they don't understand how to determine which of the two module directories (0B or 20B) is the active one.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 19:22 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Spildit wrote:
Maybe OP should try to play with SED flag changing/unlocking and see what happens ?

Could we see module 02?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 19:35 
Offline

Joined: June 26th, 2011, 19:38
Posts: 52
Location: United States
Here you go.


Attachments:
02.zip [1.22 KiB]
Downloaded 350 times
Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 19:49 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
The SED flag is set.

Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

000007D0                                      00 00 00 00
000007E0  00 00 01

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 21:45 
Offline
User avatar

Joined: August 19th, 2007, 17:30
Posts: 1899
Location: In your hard drive.
So, DFL doesn't tell you the drive is SED before working on it?

_________________
Buy your friends Toshiba\Hitachi and your enemies Seagate.


Top
 Profile  
 
 Post subject: Re: Firmware problem with ShrekLT
PostPosted: March 21st, 2017, 22:48 
Offline
User avatar

Joined: August 15th, 2006, 3:01
Posts: 3464
Location: CDRLabs @ Chandigarh [ India ]
thatdellguy wrote:
So, DFL doesn't tell you the drive is SED before working on it?


Well,
DFL solves the sed issue in a funny way .They call it firmware locked :D

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 62 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