Hi to everyone, this is my first post after 1 month of reading.

I´m not a pro and all my tools are my brayn, free software on the internet and a USB TTL PL2303 cable

I´m here because I would change the model name on a SAS Cheetah and I started to experience with a SATA ST380013AS as there is so much more info for it.

I know now how to change the model name on the SATA model but I destroy info in the process and I would like to restore my disk without loosing data if it´s possible.

Disk is accesible and this is the error report after connect and CTRL + C command;

"Interface task reset
4096k x 16 buffer detected
ALPINE - 1_Disk S-15 02-08-03 14:00

Buzz - Head Mask 000F - Switch to full int.
Spin Ready

8.05 09-10-03 16:23
(P)SATA Reset
Mesa C2 Grand D Legacy mode
AT Er 00 Nwt Er fe RdWr 934d.02.0000
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: a9a80000 ff 00000000.a9a8.000 000a 0000 0009 0001
AutoRd Err fe at 02934d.00.0112

CE Log EC=fe Rtype=25 OV=0 STStatus0
SCAN Error
AT Er 00 Nwt Er fe RdWr 934d.02.0000
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: a9a80000 ff 00000000.a9a8.000 000a 0000 0009 0001
AutoRd Err fe at 02934d.00.0113

CE Log EC=fe Rtype=25 OV=0 STStatus0
SCAN Error

I already tried ASCIFE and I would like to say I have any previous back up of nothing as I was not experienced on what I was doing.

Could the ST380013AS be restored?

Thank you in advance for your answer and knowledge.
nachin11

I forgot to say, HDD attached to the SATA channel block my computer and I can´t enter in Windows, eventhat is recognised by the bios apparently correctly.

Greatings from Spain

Better way is to selfscan it. BUT
Then you have to write all service area back, which I suppose you do not save. And to selfscan it you have to upload APP cert and tables which will be almost impossible without appropriate tools.
Sell it as "donor" probably is the best idea.

_________________
DataRecovery.bg

Not bad idea

In a first try Windows could saw the 2 partitions, C and D (Dell Utilities) so I´m optimist now Windows hangs.

I did not execute "complicated" commands, only Ctrl + "". and ASCIFE

Could I make a "service area" copy now and see if it´s still valid?

P.D.: Disk says Cert 133 is correct.

Safety belts are intended for use BEFORE crashing, not to be fastened AFTER crash....

At present there's very little or nothing to do without resources.

Thank you for your answers

How I have to proceed with my SAS Cheetah to make the appropiate backups?

Taking in mind your previous post the resources in drive are still intact, drive is having problems reading head 0. Even loosing original resources is not so "huge" problem as the way to load then back to the drive.
I have a question about your intention to manipulate SAS cheetah drive passport. Do you know how to connect the terminal, do you know the commands needed to do required action?

_________________
DataRecovery.bg

Resources means tooling.

I know the Sata terminal commands and the proccess to change model name on Sata drives, Is the same for Sas?