ST3000DM001 - Imaging every 20 secs after Power reset then

[BenDataRecovery]

Hey guys,

imaging every 20 secs after Power reset exactly 100 MB! That's better then PIO mode imaging 1 MB/s which is very stable but annoying... the drive would image ages...

is there a way to get it more stable? Already 250 GB imaged - but it is a 3 TB drive...

Thanks in advance
Benjamin

edit: I added a screenshot with changes that were made... Jared edited the SysFile 93 with PC3000 to get the changes persistent.. that was the only way. With Just unchecking the boxes the changes were only temporary... or were not even made.. maybe because of the small timeframe the HDD is going to BSY again.

Attachments

[labtech]

When the slow down occurs, what is the drive doing in the terminal?

[michael chiklis]

Try to clone via UDMA33 instead of UDMA66 or sata high speed.
Also, try to change read timout, sometimes with this drives is better to read with very low timouts (example 150 ms instead 10000 ms).

[laptokowiec]

Has changing from UDMA66 to UDMA33 helped with imaging ?

[day1data]

Try imaging just by head, and in reverse.
Are you able to image the MFT? If so why don't you try selective file imaging.

How much data is on the drive?
I wouldn't bother imaging the whole drive unless there is a lot of data.

[laptokowiec]

Before we imaged the whole area, there were some modyfications in CONGEN. Additionaly we programmed the process to imaging in 200MB parts .
We managed to clone almost 100%

[Nick_CT]

I've found that some really strange DM reading issues can be resolved by just reading in reverse (and sometimes with PIO) without any errors at all, one head at a time.

[Amarbir[CDR-Labs]]

Hi Everyone ,
day1data asked [ why not do selective file cloning ] ,Answer is because MRT Does not have that feature .Also We use PIO all the time ,Sometimes its necessary as all the time you cannot rush .

[Nick_CT]

I've found that some really strange DM reading issues can be resolved by just reading in reverse (and sometimes with PIO) without any errors at all, one head at a time.

The problem with PIO is that it takes lonnngggg time to image.

I've just done a WD 320 GB in PIO (with HRT-DRE cloning tool) and it took 3 days (skipping several areas when 5 bad sectors were found consecutively) + 1 day to check all the bad sectors one by one and image the skipped sections.

There were several power resets as well as the drive wouldn't recover from BSY even with soft resets.

In PIO we can expect something like 100 GB to 120 GB a day assuming no bad sectors are found.

1 TB drive will take 10 days to image in PIO.

If you're just after a user profile then 100GB a day is fine in my opinion. Imaging the whole 3TB drive could be a problem, but if it's docs, pics and a PST then PIO would be alright in a reasonable time frame, especially if it's only 1 head we're talking about.

[Nick_CT]

I have this loader, but I don't think it's going to help you if it needs heads