using MHDD

[tech_boy]

Can MHDD copy sectors it reads to an external file, while it scans the drive for bad sectors ?

Someone mentioned this on another forum. The reason I ask is because if an HDD is on the "brink", I want to be able to save what data I can, while getting a diagnosis at the same time, because I know I may not be able to scan the disk again.

I hope this makes sense

[Vulcan]

Can MHDD copy sectors it reads to an external file, while it scans the drive for bad sectors ?

Last time I checked, it didn't do this very well, e.g. it doesn't save any "placeholder" on the target, when there is unreadable data on the source - but as far as I can tell, MHDD is not designed for this type of large-scale cloning, so such limitations aren't a surprise.

The reason I ask is because if an HDD is on the "brink", I want to be able to save what data I can, while getting a diagnosis at the same time, because I know I may not be able to scan the disk again.

If you don't have a backup, and want/need to clone a disk which is "on the brink" - then just clone the disk! (You can search the forum for posts recommending various cloning software like ddrescue etc. depending on your level of expertise, cost, and preferred OS). If the disk hasn't failed, and if you still want to do some diagnosis at that point, then you've got as long as you want to do the diagnosis (depending on exactly what you mean by that term), after you've got a clone of the data.

If the disk is so faulty that you are "not be able to scan the disk again", then you don't need to get a diagnosis

It seems to me that the situation you're describing can be avoided by having adequate backups - or if you find you're having problems, and forgot to take backups, then use a cloning program (like ddrescue or similar if you're accepting the risks & limitations of DIY, or by using the services of a pro with hardware assisted cloning like DDI) first, instead of using software which is not primarily designed for cloning (like MHDD).

Hope that helps.

[tech_boy]

Ah thanks, I see your point.

Why would I run a scan on the drive when I could just use a good rescue tool like the one you suggested. Because either way the drive is going to be scanned.. May as well get the data in the most efficient way possible.

Thing is, I'm a new computer repair tech (haven't opened yet) and I'm trying to figure out a scheme for preserving data, in the cases when I have to diagnose an HDD and the customer NEEDS their data.

From what I gather, if a customer doesn't care about their data, you can run any number of "logical" troubleshooting utilities even if the mechanical parts of the drive are dying, and it wouldn't matter if the drive crashed from the scans. But in the case when the customer wants their computer fixed AND needs their data, I don't want to run "logical" scanning utilities for risk of adding more ware to the drive, before getting the data. That's ultimately where I was coming from..

thanks

[networks]

From what I gather, if a customer doesn't care about their data, you can run any number of "logical" troubleshooting utilities even if the mechanical parts of the drive are dying, and it wouldn't matter if the drive crashed from the scans. But in the case when the customer wants their computer fixed AND needs their data, I don't want to run "logical" scanning utilities for risk of adding more ware to the drive, before getting the data. That's ultimately where I was coming from..

thanks

The "best practice" with regards to data recovery is to always make a bit stream clone of the drive either way as Vulcan mentioned in previous post. You do not want to do anything to the "source" customer drive like chkdsk, spinwrite etc. You always want to work off the clone copy of the drive which is a good drive no mechanical issues etc. If the customer "needs" their data you may want to consider partnering with a DR firm and send those to them and possibly earn a small commission. That way you know the customers data recovery potential is the best it can be until you get more time and experience under your belt. If you want to learn then by all means use the drives the customers or whoever doesn't care about or they have a good backup and learn from those cases.

[Vulcan]

I'm a new computer repair tech (haven't opened yet) and I'm trying to figure out a scheme for preserving data, in the cases when I have to diagnose an HDD and the customer NEEDS their data.

This all depends on things like: what you mean by "diagnose"; what your agreement is with your customers about who is responsible for their data; about why they haven't got a backup themselves if, as you claim, they "NEED" their data; about what the reported problem is (i.e. are they asking you for a data recovery service, or for some other hardware fix where you just want to scan the hard disk as a courtesy); etc. etc.

Since I dislike this type of hypothetical question (since, in my years of experience, the question/scenario often changes and the questions go on and on) I'll just give a couple of comments based on my experience, and then I'll step back from the thread:

a) There are many variables (including some I explained above), which you haven't listed, and these typically will influence the decision about a suitable approach in different cases.
b) MHDD is not a suitable tool for large-scale cloning IMHO - which addresses your original question.

[Corsari]

I think the idea of using MHDD to clone the drive is because it maybe not mounted by the OS.

While MHDD gives direct access to the drives, isn't it?

Anyway, which is the best way to use MHDD to clone one hard drive on to a second one (both connected)? Alternatively, is it possible to create one image of the first drive in any directory of a second drive? If yes, I'm wondering which file systems type MHDD is able to work with/on.

Obviously at test level

Thank you for any tip