MultiDrive – free backup, clone & wipe disk utility from Atola Technology

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  Page 1 of 1
  [ 5 posts ] 
  Previous topic | Next topic 
Author Message
beefstrudel
 Post subject: Palmer doesnt ID after SED unlock
PostPosted: July 10th, 2025, 12:04 
Offline

Joined: September 14th, 2023, 8:43
Posts: 59
Location: Kentucky USA
I have a palmer with a failing head I need to unlock for heads map and lock UA. When using PC3000 to unlock the ROM the drive no longer IDs. It readys in kernel mode with no errors in the utility, sounds like the heads click twice and then park. Uploading the powerup log after the ROM is unlocked, original and unlocked ROM.
ACE Lab TS provided me another ROM to try but it gave the same results. This is with a donor board and the original, drive behaves the same.

With the original locked ROM, drive IDs and has sector access. I just need heads map to disable bad head.


Attachments:
Palmer.zip [1.9 MiB]
Downloaded 15 times
Top
 Profile  
 
fzabkar
 Post subject: Re: Palmer doesnt ID after SED unlock
PostPosted: July 10th, 2025, 14:29 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia
Unless my software has a bug, the boot block in your digitally signed, unlocked ROM has a bad checksum.

Code:
Analysing 00599-352370735-unlock.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
-----  -- --   --   -----   -----   --------   ------ -----  ---------
    0  5A 54   04   80000 - 80157      4FF60      154   154  EEEEEEEE 0000F16C BAD (not digitally signed)
                                                             000005F0 0000062F BAD (digitally signed)
2000  01 FD   04    21A0 -  498C      49688     26EC  26EC    3B   3B   OK
2020  02 EB   11    498D -  8899   30080000 c   542C  3F0C    02   02   OK
2040  03 F7   0C    889A -  8C8E   24000000      3F4   3F4    D8   D8   OK
2060  04 D0   40    8C8F -  DEAB   FFE00200     521C  521C    98   98   OK
2080  05 A9   01    DEAC -  E9B8   38248600 c    D48   B0C    EF   EF   OK
20A0  06 AA   04    E9B9 -  EE59   3824A600      4A0   4A0    79   79   OK
20C0  07 DB   01    EE5A - 14E02          0 c   7950  5FA8    9B   9B   OK
20E0  08 31   01   14E03 - 151BF       DC44 c    480   3BC    DF   DF   OK
2100  09 5F   03   151C0 - 17780      40340 c   304C  25C0    AB   AB   OK
2120  0A 3F   03   17781 - 17B59   60249600 c    9AC   3D8    26   26   OK
2140  0B F8   01   17B5A - 2F53E   3832CC00 c  1FB74 179E4    A1   A1   OK
2160  0C 06   01   2F53F - 5350B   38008230 c  310F8 23FCC    9F   9F   OK
2180  0D BE   00   5350C - 5435D   FFF60000      E51   E51    59   59   OK
82000  01 DD   04   82180 - 8496C      49688     26EC  26EC    64   64   OK
82020  02 CB   11   8496D - 88879   30080000 c   542C  3F0C    02   02   OK
82040  03 D7   0C   8887A - 88C6E   24000000      3F4   3F4    D8   D8   OK
82060  04 B0   40   88C6F - 8DE8B   FFE00200     521C  521C    98   98   OK
82080  05 89   01   8DE8C - 8E998   38248600 c    D48   B0C    EF   EF   OK
820A0  06 8A   04   8E999 - 8EE39   3824A600      4A0   4A0    79   79   OK
820C0  07 BB   01   8EE3A - 94DE2          0 c   7950  5FA8    9B   9B   OK
820E0  08 10   01   94DE3 - 9519F       DC44 c    480   3BC    DF   DF   OK
82100  09 3F   03   951A0 - 97760      40340 c   304C  25C0    AB   AB   OK
82120  0A 1F   03   97761 - 97B39   60249600 c    9AC   3D8    26   26   OK
82140  0B D8   01   97B3A - AF51E   3832CC00 c  1FB74 179E4    93   93   OK
82160  0C EA   01   AF51F - D34EB   38008230 c  310F8 23FCC    9F   9F   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes

00599-352370735-unlock_ACELAB.bin (good checksum)

Code:
Offset(h) 00       04       08       0C

00080000  00000000 DC0BFFFF 00000000 20000000
00080010  00100000 68190000 00000000 00000000
00080020  00000000 6823FFFF 00000000 00000000
00080030  00000000 00000000 00000000 00000000
00080040  00000000 00000000 00000000 00100000
00080050  00000000 2F060000
                   ^^^^

00599-352370735-unlock.bin (bad checksum)

Code:
Offset(h) 00       04       08       0C

00080000  00000000 DC0BFFFF 00000000 20000000
00080010  00100000 68190000 00000000 00000000
00080020  00000000 6823FFFF 00000000 00000000
00080030  00000000 00000000 00000000 00000000
00080040  00000000 00000000 00000000 00100000
00080050  00000000 F0050000
                   ^^^^

_________________
A backup a day keeps DR away.
Top
 Profile  
 
beefstrudel
 Post subject: Re: Palmer doesnt ID after SED unlock
PostPosted: July 10th, 2025, 15:18 
Offline

Joined: September 14th, 2023, 8:43
Posts: 59
Location: Kentucky USA
I noticed the one ACE provided was digitally signed and the one I made was not, however both ROMs give the same behavior. Heads just click twice and park, drive stays spinning and ready in kernel mode.

Any ideas how to fix it? I have the drive imaging now with the original ROM but without being able to get a heads map its just going to take forever.
Top
 Profile  
 
fzabkar
 Post subject: Re: Palmer doesnt ID after SED unlock
PostPosted: July 10th, 2025, 16:49 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 16960
Location: Australia
It appears that the checksum is ignored, in which case my observation is a red herring. Sorry.

Would manually editing the head map in ROM module 0x0A achieve the same end? Is UA locking normally achieved via edits to the ROM?

_________________
A backup a day keeps DR away.
Top
 Profile  
 
beefstrudel
 Post subject: Re: Palmer doesnt ID after SED unlock
PostPosted: July 11th, 2025, 12:37 
Offline

Joined: September 14th, 2023, 8:43
Posts: 59
Location: Kentucky USA
Locking UA makes a change in service area, not sure which module.
Yesterday I just started imaging it with the original ROM, it picked up speed overnight. It was looking at about 50 days to image 460 GB, now its at 48% and down to 2 days remaining. At this point I'm just going to let it run the way it is. ACE doesn't seem to be able to figure it out either.
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 5 posts ] 

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: Google [Bot] and 39 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:  
Switch to mobile style
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group