Hi guys,
I'm handling this Rosewood and after power up it calibrates fine, no mechanical noise, get RDY DSC in status register.
In terminal I get the long message in attached. So far I had not seen a similar message.
Do you have any idea what it could be?
Thanks so much
Jojo
ST1000lm035-long message in terminal
Moderator: Nick_TS
ST1000lm035-long message in terminal
- Attachments
-
- Terminal.txt
- (16.03 KiB) Downloaded 512 times
Re: ST1000lm035-long message in terminal
Can you read modules and Sys files?
Re: ST1000lm035-long message in terminal
No I have not yet started to read the modules and Sys files.
I wanted to send a preliminary quotation based on the output of the terminal. Tomorrow I will start testing.
Thanks for the reply Pclab...I'll let you know.
Jojo
I wanted to send a preliminary quotation based on the output of the terminal. Tomorrow I will start testing.
Thanks for the reply Pclab...I'll let you know.
Jojo
Re: ST1000lm035-long message in terminal
Maybe It's something I do wrong, but I usually "almost" or even repair the drive before making a quote (or if it's something a little harder to do, like a headswap).
Only then I know what's wrong and give the proper quote.
Like this I know the problem is solvable and if it will take 1 day or 2 days or 2 weeks.
Only then I know what's wrong and give the proper quote.
Like this I know the problem is solvable and if it will take 1 day or 2 days or 2 weeks.
Re: ST1000lm035-long message in terminal
Are 348 and 28 system files readable using COM-port?
With best regards
ACELab technical support
ts.acelaboratory.com
blog.acelab.eu.com
ACELab technical support
ts.acelaboratory.com
blog.acelab.eu.com
Re: ST1000lm035-long message in terminal
Sorry Guys for the delay of the reply but I wanted to do some tests and I got 99.20% of the data.
Yes I was able to read the most important Sys files and modules. Then after translator regeneration and edit 93 Sys file I managed to get the complete ID.
Only I did not have full access to the sectors.
So I loaded the Sys file 35 (previously saved) written to the drive and run translator regeneration. I managed to read 1856515558 sectors.
Unfortunately, the drive had reading problems, by an amazing coincidence on the MFT.
But I think the structure of the main folders managed to get it, together with “Lost & Found”.
Unfortunately I tried the various methods of restoring the translator but without success.
In attached the log and terminal.
Anyway thanks for the reply.
Jojo
Yes I was able to read the most important Sys files and modules. Then after translator regeneration and edit 93 Sys file I managed to get the complete ID.
Only I did not have full access to the sectors.
So I loaded the Sys file 35 (previously saved) written to the drive and run translator regeneration. I managed to read 1856515558 sectors.
Unfortunately, the drive had reading problems, by an amazing coincidence on the MFT.
But I think the structure of the main folders managed to get it, together with “Lost & Found”.
Unfortunately I tried the various methods of restoring the translator but without success.
In attached the log and terminal.
Anyway thanks for the reply.
Jojo
- Attachments
-
- Terminal-Translator-Recovery.log
- (32.05 KiB) Downloaded 450 times
-
- Log-Translator-Recovery.log
- (26.68 KiB) Downloaded 411 times
Re: ST1000lm035-long message in terminal
pclab wrote:Source of the post Maybe It's something I do wrong, but I usually "almost" or even repair the drive before making a quote (or if it's something a little harder to do, like a headswap).
Only then I know what's wrong and give the proper quote.
Like this I know the problem is solvable and if it will take 1 day or 2 days or 2 weeks.
PcLab I know that doing most of the work you can be more precise about the quotation, but I do not really like repairing the drive and doing most of job, and then maybe, get a refusal of the estimate.
Who is online
Users browsing this forum: No registered users and 12 guests
