Seagate is now the largest manufacturer of hard disk drives. So there are many families associated with Seagate.
Some users select falimy randomly and get following output in the terminal:
We will explain how to overcome this problem using PC-3000.
Sometimes data recovery engineer need to prepare a report for customer. We are going to overview what kind of reports can be provided by PC-3000.
Hello dear friends,
Very often we get a question about “Using donor stored resources” feature for Hitachi IBM-ARM drives. How it can be used?
Let’s take a look one real case with real issue which we’ve faced several times for the recent past.
First off all we have Toshiba DT01ACA050 drive in this case. Not all our customers know that in fact DT01ACA model (and some other Toshiba drives too) are related to Hitachi! And it can be easily determined:
On the label we see HDS721050DLE630 (Also original model you can find in IDNT module). Therefore we should choose 7210DLE6 family to operate with this drive properly. Continue reading
Before we will start, a small description:
This article was planned as a short guide for monolith pinout research. The main idea of this article is not to study step-by-step how to search pinout in all possible cases, but to understand the main principle and main idea of this process which is rather complicated and required a lot of experience. In other words – this article is posted “as it is”. We don’t want to say that current example is the best one, and all tools and hints that we are describing would be the best choiсe in the world. Exist a lot of methodics, and we are going to share only one of them.
PC-3000 products are produced for data recovery, but monolith pinout research is additional branch (rather large by the way) which is not contact with our technology directly. It’s the additional market, with it’s own “underwater rocks”, problems and profits. That’s why we provide only overview information, for better understanding and realizing “Do I really want to spend my life for dealing with this pinout research or not?”
From time to time we get the questions from our customers, especially from the beginners: how to fix the bad modules in Service Area?
Some modules can be fixed using the PC-3000 commands like translator regeneration, for example. But what to do if the drive has the bad sectors in SA, and some important module can not read good? Let’s discuss it in this article.
There are a lot of cases which alow to read a user data but it’s to slow or drive has a damaged surface at the start of users area, as result impossible to expand a user partition or it takes a lot of time.
But how to deal with such cases if customer needs his data right here right now or we have a time restriction by drive operation because it proceed to damage the heads/surface…
In this article we will talk about this problem and possible solutions for it.
Some family of Seagate F3 drives has specific issue which you wil not see on other families. One of these issues we would like to show today.
Some customers are asking us is it possible to run PC-3000 under Linux. We decided to make some testing and answer on this question.
For the lazy and busy: yes, it’s possible. But performance will be 4-5 times less. If you’d like to know why – you are welcome to read further.
Hello Friends! Recently we’ve got a case where we saw the next message in utility terminal tab after drive’s power on:
MCMTFileHandler: EXCEPTION: Failed MCMT read request
We see such cases pretty often here in support, so let’s see what can be done to bypass this error and get the full drive’s ID and user data access.
This article is not about a cooperative platformer, even not about popular racing video game. It’s about shifted data and method for fixing it in PC-3000 Data Extractor utility.