When I restarted the MHDD in my drive, and then I select the option without SCSI. I have a SATA drive. After loaded. I typed 1 to select my HDD from the list. I typed in erase. I get LBA mode: disk drive not ready. What does this mean? How can I fix it?

What letters do you have lit up in status register once selecting the drive and issuing F2 to ID?

_________________
Hard Disk Drive, SSD, USB Drive and RAID Data Recovery Specialist in Massachusetts

At the drive selection screen, my HDD is first, and the DVD-ROM is second.

What was meant was when you select your drive what status id's show highlighted ie: DRSC, DRDY, BUSY etc.

Loki

It showed busy not ready. That was in a black screen when you hit F2.

Thats your answer the hard drive hasnt initilised, it should say DRSC & DRDY.
Looks like your drive has other issues most likely not a DIY fix.
As your trying to erase the drive their is obviousally no data that is needed.
Time to bin the drive unless its under warranty?

Loki

What if I use another tool to erase such as DBAN, and then come back to MHDD? Or what tool can fix my drive?

The drive needs to initialise ie DRSC & DRDY, if it doesnt you wont be able to use DBAN etc.
It would need a proper diagnosis. If its a firmware issue? tools like PC3000, Atola, SD Doctor Suite but they cost $$$$ ie PC3000 UDMA is about $15,000 + you will need training & lots of experience.
As I stated before not a DIY fix. Data recovery comapanies get a drive in working order to recover data they do not fix drives for you to continue to use.

Loki

It works fine in DBAN, but not in MHDD. I wanted to try MHDD. Why does one tool works, but not the other?

I've got an idea of a possible answer, but without having that drive in front of me so I can run my own tests, I can't be sure. Since you don't need the data from this disk, it isn't worth me spending more time troubleshooting this.

If you want to do more work yourself, you could search for and try other utilities (more than just those 2 tried so far), to see which ones do, and which do not, appear to recognise that drive. You may then find a common factor between the programs which recognise that drive, and that then answers your question.


That's not what you seemed to be saying in this thread:
darik-showing-unrecognized-drives-t20334.html

So in the drive selection list in MHDD, you can see your drive listed with name and LBA?

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

Yes, and I type "1" to select my drive.

I'm not sure if everyone if misunderstanding? I'm looking to use MHDD for erase, and not recover? I know I stated that in my previous thread.

Can you post a screen shot or type out what it lists for your drive?

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

MHDD will not work with this device.

Drive not responding or operation canceled.

Work only in LBA mode.

Try checking your BIOS to see if you can change a setting to LBA mode.

Loki

I meant on the drive selection screen

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

I hope this helps?

PCI controllers

WDC WD1001FALS-00E8B0 05.00K05 WD-WMATV8679648 1,953,525,168

HL-DT-ST DVDRAM GH15F EG00 K5A91B12621 87,722

WARNING: SLAVE DEVICES NOT SUPPORTED

HDD number [3]:

@loki:

FYI that BIOS setting makes no difference to MHDD - it is used only for int 13h access, not for register-level access.

That error from MHDD is typical for when the Identify Device command fails or it returns unexpected data from the drive e.g. Word 49 in the Identify Device response, which indicates whether the drive can be accessed via LBA, or only CHS. All modern drives should respond that they can use LBA access (which is a specific type of register usage), but I have seen times when faulty drives didn't do that...

Edited to add: In this case, the Identify Device command is working, so it must be that it's returning unusual data, e.g. from ROM data, as I mentioned above.

Would there be a solution for fixing this?

To answer that question, a correct diagnosis is needed first, but that needs equipment and experience e.g. at a DR company IMHO.

You don't need the data recovered from the drive, and any repair to the drive would cost more than the price of a new drive (and you couldn't be sure of the length of time that any repair would last), I therefore see no point in continuing the troubleshooting - but if you have enough free time that you find the problem, please do come back and tell us.