Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Merc2 firmware needed

October 24th, 2014, 13:43

I have a sata Merc2, not detected in BIOS, giving a terminal output of EC=43 error and also complaining of cert code on Ctrl+R.
Could you help me with Cert 3.14? I want to SS the drive. Thanks.

Eng Rev = .501
MERC2 - 1_Disk 3.14 01-20-06 15:55 14 ,MERC2,14
CERT Rev = .029
NONE
Mask Rom Rev = 0.05
Unique Descriptor = .1A0

Code:
Interface task reset4096k x 16 buffer detected
MERC2 - 1_Disk    0.05   01
Buzz  - -20-06 15:53
Head Mask 03,01 - Switch to full int.
              Spin Ready
Dwell Cyl - 0DAC/07CD/0000
(P)(H)DiskAccess ReadSector EC=43 at ffffffff.00.003f
DiskAccess ReadSector EC=43 at ffffffff.00.004b
INVALID Cert Disk Code - ROM Resident Revision Required: 3.14

Re: Merc2 firmware needed

October 24th, 2014, 14:02

Try this one
Attachments
SgLDR.zip
(420.04 KiB) Downloaded 273 times

Re: Merc2 firmware needed

October 24th, 2014, 14:11

Thank you, unfortunately I use free tools, and they don't handle loaders. :(

Re: Merc2 firmware needed

October 24th, 2014, 14:21

Are you use SDLD for upload? So, here is arch with Cert code and Cert tbl.
Attachments
Cert 3.14.zip
(225.7 KiB) Downloaded 272 times

Re: Merc2 firmware needed

October 27th, 2014, 6:54

Thanks. Is it taken from a SATA drive with 3.14 firmware? I compared it with a Cert from a PATA drive having firmware 3.06 and here's the only difference (found at offset 10000):
Code:
.´bĽ3.06
@iaÄ3.14
Is it possible that 2 different Cert revisions differ only in the revision number? And sata and pata certs can also be the same? Asking it, because I have little knowledge of certs not to question your goodwill.
The second part of my original cert seems not damaged (saved it twice and both copies were the same) and is quite different from the one you uploaded.
Started SS with your cert and after Ctrl+T nothing happened (whereas with my damaged one at least it starts (see log).
Can it have other problems?
Attachments
ss.fail.txt
(14.39 KiB) Downloaded 519 times
Post a reply