Another MRT bug - ST340015A - No SA access

[michael chiklis]

This is another good drive, it hasn't any problem and i can read and write on user area.
MRT detects it with correct ID and register status DRD - DSC are correcty on.

Now i want to backup mods, but MRT is not able to access correctly into SA

As you can see it fails, probably because it search SPT of U Series X drive.
Drive ST340015A is not U Series X family but it's B540 family as written on this SalvationData post:
http://www.scribd.com/doc/10963736/How- ... del#scribd

[michael chiklis]

I tried it but unsuccessfully, any mod was backed up with this tool.

[Amarbir[CDR-Labs]]

Lol ,
On MRT Forum He Was Told To Try And Check With F3 Tool Haah aa haaa

[Amarbir[CDR-Labs]]

Lol ,
On MRT Forum He Was Told To Try And Check With F3 Tool Haah aa haaa

lol

Yes ,
I was Shocked Too

[digisupport]

I gave MRT a try for 3 month - tested and compared with PC3K.

My conclusion: With MRT you will spend more time dealing with errors and unreliable results then recovering client data.
For now its to low quality even compared the very low price they are asking - will never use it on a client disk.
So MRT is back in the box it came in.

[Amarbir[CDR-Labs]]

I gave MRT a try for 3 month - tested and compared with PC3K.

My conclusion: With MRT you will spend more time dealing with errors and unreliable results then recovering client data.
For now its to low quality even compared the very low price they are asking - will never use it on a client disk.
So MRT is back in the box it came in.

Well,
This is Debatable .With Access To ISA + PCI + UDMA Manuals [ Its Not Bad Working With MRT Pro ] . But The Tool Has To Improve My Suggestion Is That Instead Of Adding Stuff They Rectify Issue And Make Proper Manuals .If They Can Copy PC 3000 They Can Ammend The Bloody Manuals Also [ As Simple As it Gets ]

[michael chiklis]

Lol ,
On MRT Forum He Was Told To Try And Check With F3 Tool Haah aa haaa

You're right.
Amazing!

[michael chiklis]

I gave MRT a try for 3 month - tested and compared with PC3K.

My conclusion: With MRT you will spend more time dealing with errors and unreliable results then recovering client data.
For now its to low quality even compared the very low price they are asking - will never use it on a client disk.
So MRT is back in the box it came in.

The good part of MRT is the Data Explorer (or if you prefer you can call it Data Extractor as for pc3k).
About FW working, they have still to do a lot of improvements...

[digisupport]

@michael - I also found that Data Explorer was not to trust, its better than ddrescue but light-years behind Deepspar and Ace.
This is just my opinion, maybe my MRT had a defect. But now many users starts reporting the same errors I had before I gave up.

[michael chiklis]

What defect have you found witk MRT DE ?

[digisupport]

ST DM001 with a few bad sectors and some slow areas, only 2 files where needed and they where complete recovered with DE. The same files imaged in MRT, one is ok (pst) the other one is corrupt (db). MRT did not report any trouble at all, not a single skipped or reading error sector.
Made the same test in DE again, both files where ok and worked. Compared files, and they where not identical.
On a WD FB lite converted to data I saw the same. Only pictures where needed and all (9 GB ) where successfully recovered in DE first. With MRT 5% of the jpegs where saved with errors and could not be opened. I also ran that job again in DE, and the files where ok.
Maybe its be course my MRT is 4 month old and not the latest hw version, but I don't trust it for client work.

[michael chiklis]

I bought my MRT on August 2014.
I don't have pc3000 so i can't compare with MRT, sorry.

Are you sure that you haven't clone the drive with MRT 'serial utility' on ?
If MRT finds bad sectors and you keep serial utility on, then it would clone not properly those sectors and it will show good green square on sector map (it should mark those sectors with dark green square).
Probably pc3000 has better way to read bad sectors via serial mode ?

After you clone sectors with MRT, you should use R-Studio to extract data on a third drive.
Don't use MRT to extract files because is not good (if this was your case then i understand clearely what you mean)

[Amarbir[CDR-Labs]]

I bought my MRT on August 2014.
I don't have pc3000 so i can't compare with MRT, sorry.

Are you sure that you haven't clone the drive with MRT 'serial utility' on ?
If MRT finds bad sectors and you keep serial utility on, then it would clone not properly those sectors and it will show good green square on sector map (it should mark those sectors with dark green square).
Probably pc3000 has better way to read bad sectors via serial mode ?

After you clone sectors with MRT, you should use R-Studio to extract data on a third drive.
Don't use MRT to extract files because is not good (if this was your case then i understand clearely what you mean)

Well,
What Do You Mean By serial Utility ? .

[michael chiklis]

For those who use MRT to recover just few data, i suggest them to use 'image marked item' or 'image current item' instead of 'save marked item' or 'save current item' in FILE EXPLORER.
After that needed files were imaged, extract them on a third drive via R-Studio.

If you used save function instead of image function, that would explain why a lot of files where corrupt (or not recovered at all).

[digisupport]

So you also have the "old" MRT version I guess.

For my test in MRT I used "image marked item" tried both in high speed and pio mode with the same result.
I did not use "active utility" no utility open in MRT, and no serial connection. I used FE to save files after imaging.

Maybe to save the files with R-Studio would work, if this is so, I made the right decision to put MRT back in the box It came from
I need to trust imaging, can not live with FE saving files that are not ok without logging the result as bad. Sorting good and bad files for client approval would be a task taking many hours.
And this was the result from drives with no bad sectors in the needed files, can not imagine what a mess it would produce on a bad drive.

[michael chiklis]

I used FE to save files after imaging

Don't save files with FE, just image them in MRT FE then save files with R-Studio.

[Amarbir[CDR-Labs]]

Well Boys ,
I Disagree With Both Of You .In My Case I Do Not Have Any Issue .I Use Only Top 4 As Michael Has Marked .You Do Not Call " Use From Active MRT Utility " Serial Utility .In My Case That Option Always Crashes .

[shaikhmaula]

michael chiklis, Dear i need your help for my MRT LAB HDD is detecting by cant find modules.

Thanks
Shaikh Maula