Samsung HD322GJ

[arpii]

Hello Guys,
I need your help. because recently something went wrong with my Samsung HD322GJ HDD. It was in good condition, but after a wake up (from sleep computer) the HDD started the following:
Spinning up, withouth any clicking or any faulty sound then staying ready till 2-3 seconds, then spinning down. The BIOS don't recognize the HDD. I've tried with PCB change, BIOS change without success. I recently got some data through terminal (see it below).
There is a lot of family photos and some documents, what I really want to save... so, I kindly would like to ask your help guys, because I have no more idea Unfortunately the professional data recovery companies is not an option for me, because that is too expensive for my budget

Here is the log:

ActiveFW : 00FWVer : 0001SATA PLL cal doneDDR size detected = 16MB˙˙˙˙˙˙˙˙˙ź VID=0 4 PN=0028 Rev=0003- 885x Found*PA VID=0004 PN=0028 Rev=0003- 885x FoundU
S_0
RV Sensor Circuit Enabled
Shock Sensor Circuit Enabled
SO_1
SpinStartUp: mcSpinRPM = 48
RPM at Handoff: 626
Temp : 24 degC
SpinOk
mS1 00000003
SK C:158305 H:0
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x1B
Selective MARC NX Loaded
Selective MARC NX Loaded
ResoTable Loaded. Rev:0x01
RRO1xTable Loaded. Rev:0x01
Fw Active 0000
Ovly loaded to 0x00014D00
Ovly loaded to 0x1002E300
FdtTable Loaded. Rev:0x02
| 19 | RLIST | 2 | 0 | 256 | 1140 |
Reading Serial Num Pass
Up MC
Diskmode ID Loaded.

PwrOn RRO1x @ H0
Table) cos = 1845760, sin = 1615872
Coeff) cos = 77102, sin = -48056

TgtCyl: 832
Hd: 0 Zn: 0 Avg.:- 416
TgtCyl: 263168
Hd: 0 Zn: 1 Avg.:- 718

SVCAL(0080,0000)-->PASS
RecordValid Fail : 0407647D 0007E41D
EPOK
VOP!
PK_4 C:236953 H:0
VOP!
PK_4 C:236953 H:0
LED 1A04
LED 1A04
LED 1A04
LED 1A04
LED 1A04
LED 1A04

Thanks in advance!!!

PS.
Another info:
I have an exactly same donor, which can be recognized by the BIOS, so the platter part firmware is maybe correct on the donor (thats trashed because bad sectors)

[jono-ats]

Likely a corrupted A-List, which can be cleared with the LE command in terminal.

Jon

[arpii]

Likely a corrupted A-List, which can be cleared with the LE command in terminal.

Jon

Thx for fast response. It keep the filesystem on the disk or I have to use some kind of "raw data" recovery to save my data?

[northwind]

Yep, what he said ^

[fzabkar]

WRONG !!!!

LE command doesn't clear A-list.

LED 1A04 is indeed A-List problem but LE will only allow access to SA, it will NOT clear the A-List.

IIUC, LR is the "View Rlist" command. Does it need to be preceded by an LE? :?

http://www.hddoracle.com/viewtopic.php?f=44&t=682

Would it be possible to try the following test (on a drive with grown defects)?

LR
LE
LR

Does the output of LR change after issuing LE? I'm assuming that the Rlist is the "A-list".

[fzabkar]

As you can see LE doesn't change A-List.

Thanks, that is conclusive enough for me. :-)

[fzabkar]

Clear S.M.A.R.T. VSC for Samsung :

taskfile registers = DE 00 01 4F C2 A0 B0

The SMART feature field value is DEh. The ATA standard specifies this as a "reserved" value which means that it is not to be used by vendors. Instead values E0h - FFh are assigned as "vendor specific". :?

Attachments

[arpii]

Guys, I stucked in a basic point.
The patient connected to SATA3G port 1. I've the system on SSD on SATA6G port 1. When the patient attached, the windows doesn't starts, stucked on starting windows flag. Okay, I checked the hot plug option on, in the BIOS.
I have SHT v4.0.9 Demo and unfortunately I cannot idetify the HDD both with normal and safe mode HDD identification. There are a menu, named "Set IDE port data", I've tried both available option but without success.
Moreover, the donor also started the same symptons like the patient

[fzabkar]

Are you saying that Windows also cannot start when your good donor is attached? Does BIOS see it?

[arpii]

Thx, with this i can check the correct address of the port. I hope thats all why the SHT cannot found the Hdd.
Umfortunatelly it seem a major issue of this type of drive, but you have to know, the donor had some bad and/or weak sectors, but it was able to recognize by the BIOS before...

[arpii]

Here :

The attachment hdd.jpg is no longer available

Your drive is this one !

Okay, finally the SHT recognized that, but I needed to switch to IDE from AHCI and choose the first controller's "slave" option.
It can be recognized after I issued the LE command in terminal.
You sent me a table from another app. which ATA command can be clear the A-List. How can I apply that in SHT? Is it named "Works with ATA registers" ? Its look a little bit different what you sent above.

[arpii]

If you can detect the drive with SHT after the "LE" maybe the drive can be detected by BIOS/USB adaptor as well, the problem would be that if you were to image/copy data as soon as you reach the first bad block you might be in trouble.

I don't know if you can copy data out with LE only without clearing the A-List first.

But if "LE" is allowing to load firmware past the point that it hangs with LED message in a way that SHT can now ID the drive with correct capacity maybe "LE" is all that you need to make the drive detected by BIOS / ATA interface in a way that it can be cloned. The trick is not to power off the drive.

If you fix the A-List/S.M.A.R.T. you can power off the drive and on again. It shouldn't be stuck in BSY and should detect as normal by the SATA interface.

I don't know how to say thank you!!!!!! After I performed the mentioned ATA commands, after a system restart, the HDD has been recognized by the BIOS and the filesystems were browse-able in windows. My data is on the way to the safer new place...

[fzabkar]

As usual, very nice work, Spildit!

[pepe]

As usual, very nice work, Spildit!

I still not understand what's so nice about disclosing other's research...
I am pretty sure Spildit never researched any VSCs on his own, doubt He could do anything like that, but he is an expert in making screenshots of VSC commands in other's programs.
Guess he hears the coins dropping in his bitpocket...

But this matter was already talked through back and forth so i don't expect much change.
Admin, please give us a smilie for throwing up

[fzabkar]

Samsung's VSCs were disclosed publicly around 15 years ago by other researchers.

[pepe]

then i must be 15 years behind....

[fzabkar]

then i must be 15 years behind.... :)

Yes, you must be.

[fzabkar]

Guess he hears the coins dropping in his bitpocket...

But this matter was already talked through back and forth so i don't expect much change.
Admin, please give us a smilie for throwing up :D

We all know that your whinge is about money, but not in the way that you claim. How about a smiley for greed and self-interest?

$$$

[marcuscercal]

then i must be 15 years behind....

Yes, you must be.

Maybe less, or some kind of deficit ...

[fzabkar]

Reverse Engineering HDD Software using IDE Port Sniffer:
http://www.hddoracle.com/viewtopic.php?f=59&t=611

The following "IDE Grabber" logs contain VSCs for various brands:

http://nazyura.hardw.net/Grabb8b.zip
http://nazyura.hardw.net/Grabb16b.zip