Using the MHDD tool I found the WD SATA drive I have indeed has a 0220 Lock on it with an ATA password. Though on the google translated site, the directions may be mistranslated or i'm missing a step.

I read through the MHDD at http://hddguru.com/software/2005.10.02- ... al.en.html and even google translated the site here http://translate.google.com/translate?j ... -hard.html

and got stuck here:

-The hard drive is locked by ATA password and the security level is set to HIGH
-
-I run the script with the DUMP command. dump (attention to the point!)


Well I tried the following:
DUMP
dump
command
command.
command.dump
command. dump

and no files were generated or saved.

I tired to F1 in the program and it seems there is no Command or DUMP command to use now, Im using both the Self-extracting boot floppy image: Magic Boot Disk — Floppy Creator v2.0 and the one for the
ISO image to burn a CD: Magic Boot Disk — ISO CD Image v2.0.

I went to the FAQ at hdd-faq-t5.html to see if the dump command changed and didn't see anything.

Can anyone please help me with this?

.dump

_________________
You don't have to backup all of your files, just the ones you want to keep.

I would try every variance but that wouldnt I. Thank you, I'll give it a try tonight.

Also you have to be using the correct version and have copied the dump script into the correct folder. I couldn't see if you mentioned doing that.

_________________
You don't have to backup all of your files, just the ones you want to keep.

While using boot floppy version 4.5 and typing in

.dump

I get this:

MHDD ATA/SATA TERMINAL v2.1
Script: DUMP
---------------------------------------------------------------------------------------------------------
ERROR: file .\scripts\DUMP not found

I used the CD one with all the tools on it and nothing happened.

Doesn't sound like you actually created the script. You need to copy the script you are trying to use into a file called dump in the scripts folder.

_________________
You don't have to backup all of your files, just the ones you want to keep.

Alright, I made two files. dump1 and dump2 Maybe there was a language barrier because when I searched the forum for "create script files, or make script files I found nothing. So how am I to know that I need to make script files? From the instructions, it leads me to think, .dump Makes the files itself.

I did find "hacked your script to use a different input ... directory " and
"MHDD runs the script it will not make a new .bin file it will output to the 22 or 42 bin files so that the script does not have to create the output file"

So Im confused.

Now I have a Surface Scan (LBA28, 128GB Limit)
Enter Start LBA:_


Thats nice, I have a LBA of 488,397,168. From what to where is this password stored? I would presume somewhere between 0 and , I don't know, 500,000 but I dont know.

I did a search for "Enter start LBA" and "LBA password range" and found not a thing.

So whats the range ?

The password is not in range of 0-488,397,168 Lba's...

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Ok Fellas, this forum is becoming like our technical support at work. Obscure and unhelpful. So let me lay this out.

This forum has no one clear instruction guide to give some understanding as to how to run this. Points in-between are being assumed to be known by those who have figured it out and I have followed, what I really thought to be a basic flow of instructions. I am at a point I can go no further I am being misdirected and thrown off course and generally not helped. You have figured it out. Great.

The title of the thread here is “MHDD cannot create 21/21.bin files”

Ive read through the MHDD Documentation.

I get that my final goal is to use the Security commands to unlock the locked drive from some firmware level (NOT ON THE HARDDRIVE) password. I get that. Regardless of that knowledge I have tried to make these “files“ which the instructions state:


I see no where how big these “files“ Im trying to make can be. All I see is 32 lines of code and in that code, from a hex editor, is the password. Great, but people have been making files from 512 bytes to 1gb in size. Again, no where on the instructions does it inform how big this file we are supposed to make.

Why are their two files made? All I see is one file used to gather this information and yet I’m told to make two.

You guys said I need the correct version. That’s great! Could someone toss me a bone as to what that is? A number maybe? How about if its better to use a Floppy disk, which I may be the only one who has a full set of workable 51/4 and 3 ½ disks and drives on the Western Hemisphere, or use a CD to boot from and store the data on a USB, or let the files be written to the ram disk created. But no one is saying how, only that I did it and its done. GREAT! Show me the command line because .dump or .poop or .flush keeps redirecting me to place in an LBA range which, putting aside that LBA points to HARDDRIVE areas and not the firmware, I tried anyway, because hey. That’s why I’m posting here because I cannot create 21/21.bin files


You allude that MHDD does make the script. Ok What “script“ are you talking about? Because, call me crazy, but to this moment a “Script file,“ to me is a program written for a software environment that automate the execution of tasks which could alternatively be executed one-by-one by a human operator. But apparently, Scripts here are something else. Are you talking about .bin file? I was told here “ You need to copy the script you are trying to use into a file called dump in the scripts folder.”

From which folder?
To what folder?
Do I make the file?
Do I give it an extension?
Is there a pre-made .bin file I copy and paste into the script directory?

I’ve already made a dump1 and dump2 file, with no extension, into the \script folder and that LBA crap happens.
Is the command to make these .bin files I need the actual period while the name I give it is the ultimate bin file name?

Many places here just type .dump and poof the magic happens. Well apparently I don’t have the touch and I’m missing some critical step to do this and reading this forum from top to bottom is not helping, nor is reviewing the instructions or the threads made by other people because their own walk throughs are not coherent.

When it comes to helping unlock passwords we're all Obscure and unhelpful...as we don't know if you even are the owner of that harddrive.
I suggest you visit a DR company and ask them to unlock it for you, but you need to prove ownership of that drive.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

We're not psychic. You asked why MHDD wasn't running your dump script and the correct command was provided for you. Is it our responsibility to also verify that you have in fact created the script that you are trying to run? Would this not be obvious?

My recommendation would be to re-examine whatever instructions you are trying to follow, as you have obviously missed one or more steps. No, we are not going to tell you exactly how to remove your password, for reasons mr_spokk explained above.

_________________
You don't have to backup all of your files, just the ones you want to keep.

Also, they get paid to answer your questions and we don't. So maybe you should expect us to be even less helpful than them.

_________________
You don't have to backup all of your files, just the ones you want to keep.

I just want to point out that when feelings are hurt, defensive posts are made with chain gun efficiency. I only wish such precise detail, quick responses and multi input was offered in my question rather than this.

No one pays me for my technical help where I am, but I still managed to uphold a level of professionalism when it comes to troubleshooting and not fall back on the blame game.

I don’t see how asking you to follow my question is asking you to be psychic drc. I thought stating in the title of the thread “MHDD cannot create 21/21.bin files” was a pretty clear quesion.

The Hard Drive condition is not in question. I have already Low level formatted the hard Drive with no errors. You have no Disclosure or FAQ that requires us to prove ownership, though I am aware the impossibility to prove that on the internet. It should not , however be your fall back argument to shutting down helping someone. If you want a 7 hour video of me low level formatting the hard drive and then trying to unlock the drive, by all means ask.

Ive told you the versions I’m using, I told you the exact process I am stuck at. I have asked in my last post exactly what my question is but you rather dodge it. Fine.

This is not an issue about me needing to learn the architecture of ATA technology.

You said I need the correct version. What is the “correct” version to create bin files to import them into a hex editor to allow me to ID the master password?

So I placed the hard drive back into the 3ware controler to attempt to see again, if there was a way to remove the password from there.

I displayed the exact point at which the problem started. Again, I low level formatted the hard drive through the SCSI support built into the computer from the initial startup so there is no data. I cannot prove it by showing you a chkdsk because the HD is locked! I even went into the 3Ware Alt-3 3BM setup to remove the drive from the drive As stated

"Unlock the drives in a unit, so that
they can be removed and used with
a controller other than a 9000-series
controller."

Which I'm presuming is an entirely different lock out than the ata 0220 lock.

There is no instruction that says "make a file in Script directory and Save it there using this command." All I've seen here is the term "Altered Batch file," which has not been explained. The only thing I have seen is a contradiction in running MHDD from a CD and others saying never to do so. I thought the MHDD makes a ram disk so that wouldnt matter, but apparently it does.

I already made a blank dump1 file, with no extension, in the Script directory and it still says nothing is found with that name in that directory.

The instructions say to EID then .dump. I don't see any prep steps in between.

Attacking or criticising people here, will get you nowhere. If you don't like the responses here, then the soution is simple - go elsewhere. The members here can choose when (and if) to reply. Your later comments implying some lack of professionalism, are not worthy of a reply - you have no idea what some of us do for day jobs.

FYI, you obviously think you're being clear, but you're not. I got lost due to a lack of details in your first post, especially since you're following instructions from another website. If you can't follow their instructions, then ask them for help with their instructions!

However, you have now mentioned two pieces of new info that you didn't mention before (so who was being unprofessional in their troubleshooting?), that makes your whole problem easy to solve. Therefore I'll give you the benefit of the doubt, despite your earlier criticism, and I'll reply.

In short - your drive has been locked by your RAID controller. Either use its in-built feature to unlock it, or if you Google for 5 mins, you'll find that the potential passwords are known, as they are not intended for security as such, just to prevent the disks from being accidently reused in another PC, while still part of an array.

Easy

P.S. Don't expect more help from me, after your earlier criticism. I'll "teach you how to fish" by giving the info above, but I'm not going to spoonfeed the actual fish to you.

Thank you. The reason why I never mentioned the raid controler was that I already went through the process to remove the lock to allow cross device transport, but that made no difference and the password is still active. The only reason why I mentioned it this time around was the default WD codes did not work, so again, I fell back on the original setup. I'll in the process of digging more into the RAID card's program.

When I looked at the test script, it was in a .MBA format. When I looked up that format on google it said it was " MBA - Martus Human Rights Bulletin System (Benetech)" which didnt help. When I tried to just edit the script with a text editor to include some of the pre-posted scripts for a WD HD, every time I got an error saying it needs to be v1.1 and there is my new stuck point. I have the HxD editor but I cannot see any way from that to make a script file. Can someone just point me to a program to make such a script?

solar, I can't PM respond bc I'm too new a member, but I can read PM responses. If you PM me some contact info, I can respond to you in that way.

Sam