We have already found the problem. The solution shouldn't be too far away.

_________________
A backup a day keeps DR away.

Assuming the drive will like it later

Yup, thats the next battle

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Hello all,

latest news: rom compiled by Spildit was accepted, disk fired up and data could be rescued with Clonezilla!

Thanks to everybody trying to help, especially to Spildit and fzabkar who managed to bring the drive back to live.



Urmel

Hi, good morning.
I have a question: I exchanged Mainboards between two disks HD103SJ:

Disk 1 - New disk - No spinning.
Disk 2 - SMART activated, old disk - Spin ok.

So I assemble the good disk with the electronics of the SMART disk, also replaced the memory chip.
The disk is working perfect, no bad sectors, speed is OK, everything fine BUT....the smart diagnostics triggered is driving me crazy, windows and BIOS remember me it all the time.

I wish to clear these SMART.
Do you have a disk pinout? is RS232 TTL or C? Speed?
Which command should I use?

Thank you very much
Santiago

I'm confused. Are you saying that you replaced a faulty PCB on Disk 1 with the PCB of Disk 2, transferred the "ROM", and now Disk 1 is reporting a SMART error?

Is the "good disk" the one that fails to spin???

_________________
A backup a day keeps DR away.

Hi, thanks for the reply.

Yes, I have two discs.
Disk One: Good disk, but no spinning (I checked internal power supply and driver IC and appears OK)
Disk Two: Bad Disk, with good electronics.

So I exchanged PCBs, results: the good physical disk with the good electronics.
But the BIOS didn't recognize the HDD after a long time.
So Finally: Good Physical disk (disk one), good electronics disk (disk two), and ROM IC of disk one (good physical disk)

It´s the smart data:


Model .................................. : HD103SJ
F/W Version ............................ : 1AJ10001
Serial Number .......................... : S246J9AZC03031
Logical: CHS ........................... : 16383/16/63
Cache Size ............................. : 32767 Kb
Sectors available with LBA cmd ......... : 268.435.455 (128,0GB)
Sectors available with LBA48 cmd ....... : 1.953.525.168 (931,5GB)
Real MAX LBA ........................... : 1.953.525.168 (931,5GB)

Technological passport
Flash Version .......................... : 1AJc3suM.d26
Head Number ............................ : 4
Zone Number ............................ : 24
SA Cyl ................................. : 64
SA SPT ................................. : 1584

Table modules is loaded ................ : from SA

Zones distribution table ............... : loaded


SMART \ SAMSUNG HD103SJ
------------------------------------------------------------------
ID Attribute Name Val Worst RAW |
------------------------------------------------------------------
1 Raw Read Error Rate 1 1 87162
2 Throughput Performance 252 252 0
3 Spin Up Time 70 68 9173
4 Start/Stop Count 98 98 2159
5 Reallocated Sector Count 252 252 0
7 Seek Error Rate 252 252 0
8 Seek Time Performance 252 252 0
9 Power-On Hours Count 100 100 3034
10 Spin Retry Count 252 252 0
11 Recalibration Retries 252 252 0
12 Device Power Cycle Count 98 98 2200
191 G-Sense Error Rate 100 100 7
192 Power-Off Retract Count 252 252 0
194 HDA Temperature °C 64 57 34°C
195 ECC On The Fly Count 100 100 0
196 Reallocation Event Count 252 252 0
197 Current Pending Sector Count 252 31 0
198 Uncorrectable Sector Count 252 252 0
199 UltraDMA CRC Error Count 200 200 0
200 Write Error Rate 100 100 641
223 Load/Unload Retry Count 252 252 0
225 Load/Unload Cycle Count 100 100 2207
------------------------------------------------------------------

This is the problem now:



AIUI, you appear to be suggesting that this SMART attribute was OK before you swapped the PCB. If so, then I can't see how it could be possible. SMART data are stored on the platters, not on the PCB.

If you wish to examine the terminal log ...

How to connect a terminal cable on a Samsung drive ?
http://www.hddoracle.com/viewtopic.php? ... =189&p=432

Try cleaning the HDA contacts. Different brand but same principle ...

Oxidisation on Western Digital PCBs:
http://www.hddoracle.com/viewtopic.php? ... 649&p=1789

_________________
A backup a day keeps DR away.

Hi Fzabkar, I'm beginner, but you are right, the HDA contacts was oxidized, I cleaned and painted with silver paint.
The disk works fine, no bad sectors.
I tried to clean the SMART data with the SHT demo software, but in the demo version doesn't allow it.
I must prepare a TTL RS232 interface, to connect a terminal.
Do you know another way to clean the SMART data? Low level format? Firmware upgrade?
Many thanks for helping me

I have the same problem with my HD103SJ as Urmel_31:

• drive does not spin
• all voltages are present
• serial printout is
  
  Code:
  *PA VID=0000 PN=0004 Rev=0002- 785x Found*PA VID=0000 PN=0004 Rev=0002- 785x FoundChipRev = 63B0U
  S_0
  [DEBUG HALT @MDL_RSRC_BufferAlloc():10034A95 L0 1003A451]
  
  RV En Sensor Circuit
  En Shock Sensor Circuit

@Spildit: where can I find the description of your fix - your link is broken. Thank you for sharing!

See http://www.hddoracle.com/viewtopic.php?f=19&t=643

Give me a little time and I'll see if I can help you repair the FIPS via terminal.

_________________
A backup a day keeps DR away.

If it's a real FIPS problem, command EI should fix it.

I posted this potential solution at the HDD Oracle, but received no feedback. Have you verified that it works?

_________________
A backup a day keeps DR away.

How do I use 'EI' correctly - just enter it without arguments? Should I give it a try?

BTW: I sent commands SU and SD to start and stop the motor and they worked. Got them from here: https://forum.hddguru.com/viewtopic.php?t=26366

No. I don't have such a drive.

"DI" = Dump Image
"MI" = Modify Image
"EI" = Erase Image

"DI 64" = show Heads Map
"MI 64 FF" = unlock all heads
"DI 0 4" should return ASCII of IF SP (FIPS header)
Commands are valid for some (Trinity) models....

@eNDi, try the "DI 0 4" command.

Then try "DI 0 400"

_________________
A backup a day keeps DR away.

"DI 0 4" returns only zeros:


"DI 0 400" returns for addresses 0x0000 to 0x03ff always 0x0000, and for addresses 0x0400 to 0x07ff the 32bit address itself following a 0x4eed 0000:

Did you use the EI command? That would explain why the data are all zeros. Am I correct in assuming that the drive is still not working?

_________________
A backup a day keeps DR away.

I didn't use EI - I didn't want to erase it before you said "go"
And yes, the drive is still not working.
At least I got it to spin up with 'SU'.

I would try resoldering of the FLASH chip. It's easy and safe.