Problem HD Samsung HM250HI 2AC101C4 later Disk Cleaner (PM)

[edtambasco]

Hello first sorry for my English.
Use Google Translate.. Sorry
My name is Ed, I need your help.
I have a HP Mini with HD HM250HI 2AC101C4 it was working normally.
But I format the hard drive.
I used the program Parted Magic (Linux - HirensBoot), and instead of using the Partitioner, I used the option Disk cleanner (icon: white and red), so I chose the option erase internal zero fill.
I canceled the operation. But it was too late.

After that the nightmare began.

The HardDisk detects in the BIOS, but when I ask to install Windows to partition (disk totally free), appears the error: 0x8007045D.

I have been searching in google.
Some people asked to pass the chkdsk. It does not work.
I tried to make partition with Parted Magic again, but he did not detect the HDD unit.
I tried to use Ranish Partition, says that the disk was not found.

The only tool that detects HD after CMOS is ESTOOL.
The Smart is OK
But the examination of surface or low level formatting features BadBlock consecutive successively. And there is no repair.
Accuses the error AJ36.


The HD had no badblock.
It was after this that I used the Disk Cleaner tool Parted Magic.

I believe I damaged the firmware, found a file. RAR and PCR, but do not know which one need not download and which tool should I use to update the firmware.

I need to make this attempt, everything is perfect before my error.
Never use this Disk cleanner, he destroyed my firmware (sure).
Ask please help to update the firmware to see if you can use the disc again.

Thank you.

Ed Tambasco.

[BlackST]

If you re-run that 'disk cleaner' and LET IT COMPLETE data will be erased and the disk should work again. BUT YOU LOOSE EVERYTHING ON DISK. NOTE : THE DISK IS PROBABLY ALREADY PARTIALLY ERASED (HOW MUCH is unknown).
Unless you need data, then the problem is more complicated so don't do anything.

Last edited by BlackST on July 2nd, 2013, 0:56, edited 1 time in total.

[edtambasco]

I do not need data.
But any tool I step detects as badblock.

I can not run:
- Active Kill Disk
- HDD Low Level
- ESTOOL

All claim that the disk with this badblock, programs ask if I want to ignore or not.

I ignore but there are only errors, and nothing is repaired.

Did corrupted firmware?

Last edited by edtambasco on July 2nd, 2013, 1:04, edited 1 time in total.

[edtambasco]

Please .. sorry.. name tool program Parted Magic is Disk Erase, not Disk Cleaner.

Disk Erase (Tool Parted Magic - Linux - HirensBoot), deleted modules, tracks importants, please update firmware HD.

[BlackST]

Connect to another pc and check with MHDD.

[edtambasco]

Connect to another pc and check with MHDD.

Smart Disk OK.
HDD is Mini Notebook HP...Its possible boot cd?

I've tried several tools but they all accuse all sectors as badblock. There is a possibility of this program Disk Erase company PartedMagic have damaged my firmware? For before my HD was Normally

[edtambasco]

MHDD message - Disk not read!

[BlackST]

Select it with PORT. If no joy, then the disk has problems.

[Vulcan]

@edtambasco,

MHDD message - Disk not read!

More detail needed about exactly what appeared on the screen when you ran MHDD and what options you selected. Even with a working disk drive, MHDD might fail due to BIOS SATA controller setting.

From your story, I think that you have started the drive's internal Secure Erase, and have not allowed it to complete (I guess that you switched-off the laptop while the Secure Erase was in progress). In this case, the drive will appear to be full of "bad blocks" to some utilities (and this will prevent you from starting the Disk Cleaner again), because the drive will not allow any reads until it has finished the Secure Erase. If my guess is correct about the situation, then this is normal drive behaviour.

I doubt that the drive firmware is damaged. In any case, you cannot fix the drive firmware even if there is a problem, so don't worry about that.

Here is my suggestion, based on my interpretation of your story (which might be wrong, of course): Switch on the laptop, go into the BIOS setup (so that the laptop does not try to boot anything) and leave the laptop powered-on, showing any BIOS setup screen, for 3 hours. Do not touch it during that time - that should be enough time for the Secure Erase to finish. Then switch-off the laptop, wait 15s and switch it back on again. Then go into the BIOS setup again, select the disk setup screen and your drive should be reported as normal (of course it will be blank / erased). Reply with an update after you have done these steps.

[edtambasco]

@edtambasco,

MHDD message - Disk not read!

More detail needed about exactly what appeared on the screen when you ran MHDD and what options you selected. Even with a working disk drive, MHDD might fail due to BIOS SATA controller setting.

From your story, I think that you have started the drive's internal Secure Erase, and have not allowed it to complete (I guess that you switched-off the laptop while the Secure Erase was in progress). In this case, the drive will appear to be full of "bad blocks" to some utilities (and this will prevent you from starting the Disk Cleaner again), because the drive will not allow any reads until it has finished the Secure Erase. If my guess is correct about the situation, then this is normal drive behaviour.

I doubt that the drive firmware is damaged. In any case, you cannot fix the drive firmware even if there is a problem, so don't worry about that.

Here is my suggestion, based on my interpretation of your story (which might be wrong, of course): Switch on the laptop, go into the BIOS setup (so that the laptop does not try to boot anything) and leave the laptop powered-on, showing any BIOS setup screen, for 3 hours. Do not touch it during that time - that should be enough time for the Secure Erase to finish. Then switch-off the laptop, wait 15s and switch it back on again. Then go into the BIOS setup again, select the disk setup screen and your drive should be reported as normal (of course it will be blank / erased). Reply with an update after you have done these steps.

Vulcan you are correct.

I ran the Secure Erase (Linux - PartedMagic - Hirens) chose option Internal Zero. I canceled the operation, and the nightmare began.

I'll enter the BIOS and leave standing. But I do not see the HD light flashing

You're correct, any utility that step only indicates badblock.
Parted Magic, no longer detects the HDD

I ask you, why leave it on the screen stopped CMOS?
Thank you.

[edtambasco]

Whey you ran MHDD does it say the drive is password protected ? It should find the drive and report the ATA status.
You can try @Vulcan suggestion too and see if you have luck.
If not the drive might be damaged and you will not be able to fix it without expensive tools and knowledge. As the data is not important get another drive.

Não contem password amigo.
Tudo começou quando eu passei o Secure Erase e cancelei o procedimento.
Agora nenhum programa encontra a unidade. E quando encontra só da BadBlock
Na BIOS detecta normal. O disco não contem erros, eu que errei ao passar este programa.
Abraços aos amigos de Portugal.

===========

Contains no password friend.
It all started when I passed the Secure Erase and canceled the procedure.
Now no program is unity. And when he finds only the BadBlock
In the BIOS detects standard. The disc does not contain errors, that I was wrong to pass this program.
Hugs friends from Portugal.

[edtambasco]

Select it with PORT. If no joy, then the disk has problems.

Lapton only port (one port). The port is OK (controller), my error pass program Secure Erase (PartedMagic).

[Vulcan]

I do not see the HD light flashing

That is normal when a drive is doing an internal Secure Erase, but might also mean that your drive needs the Secure Erase command to be repeated (see below).

I am guessing that your drive just needs time to complete the Secure Erase. If my guess is wrong, and if your drive requires the Secure Erase command to be repeated, then the challenge will be to find the exact details of the command which was sent originally by PartedMagic (which actually uses hdparm to send the Secure Erase command to the drive, IIRC), if you are unable to just re-run the same program, as already suggested by BlackST.

Just to be clear: Have you already tried to repeat the exact procedure which you did before, to start the Secure Erase originally? Please answer clearly what happened when you tried, or state clearly if you do not understand the question.

I don't have the spare time to setup a test system and use PartedMagic to repeat your situation, to - obviously that would allow more complete diagnosis.

Unfortunately I did not see a clear reply from you, giving the details of exactly how you were using MHDD and exactly how MHDD recognised the drive, so I am not confident of the real status. I think you misunderstood the question from BlackST and perhaps the communication / translation situation is a problem here. Good luck!

[edtambasco]

I do not see the HD light flashing

That is normal when a drive is doing an internal Secure Erase, but might also mean that your drive needs the Secure Erase command to be repeated (see below).

I am guessing that your drive just needs time to complete the Secure Erase. If my guess is wrong, and if your drive requires the Secure Erase command to be repeated, then the challenge will be to find the exact details of the command which was sent originally by PartedMagic (which actually uses hdparm to send the Secure Erase command to the drive, IIRC), if you are unable to just re-run the same program, as already suggested by BlackST.

Just to be clear: Have you already tried to repeat the exact procedure which you did before, to start the Secure Erase originally? Please answer clearly what happened when you tried, or state clearly if you do not understand the question.

I don't have the spare time to setup a test system and use PartedMagic to repeat your situation, to - obviously that would allow more complete diagnosis.

Unfortunately I did not see a clear reply from you, giving the details of exactly how you were using MHDD and exactly how MHDD recognised the drive, so I am not confident of the real status. I think you misunderstood the question from BlackST and perhaps the communication / translation situation is a problem here. Good luck!

Yes I tried to redo the procedure.
But the HDD is no longer recognized in PartedMagic

MHDD did not recognize the drive.
Parted Magic not longer recognizes the drive
Only CMOS and ESTOLL recognize HDD
But does the low level formatting

I canceled the Secure Erase, and now I can not run again because it does not detect
Get it?

Problem appeared after I ran Disk Eraser.
I'll leave the BIOS screen for 3 hours, and say what happened

[Vulcan]

Get it?

Perhaps yes, perhaps no. Because now you say:

MHDD did not recognize the drive.

But earlier you said:

Whey you ran MHDD does it say the drive is password protected ?

Contains no password friend.

That suggested that you had run MHDD, in order to answer Spildit. You also said:

MHDD message - Disk not read!

That is not the same as disk is not detected by MHDD. So earlier it seemed that you were saying that MHDD detected the drive, but could not read it successfully. That is why I asked you clearly exactly which MHDD option you had tried (I guessed Scan - F4).

Now I think everything where you seemed to be using MHDD was a misunderstanding, and you are now saying that MHDD does not detect your drive - which might be due to SATA controller settings in the BIOS (MHDD typically does not work with the modern default SATA controller AHCI setting).

Anyway, thanks for confirming that you have tried to repeat the original procedure. There is very likely to be a workaround, but I do not expect that I can explain it clearly enough, due to the communication problems.

[edtambasco]

I could not run the Disk Erase again.
But I took some pictures for you to see what options I used.

Picture 1 - Shortcut
upamais.com/images/66137556537824618661.jpg

Picture 2 - Option I chose (before the problem)
upamais.com/images/78772865107026469609.jpg

Picture 3 - Error can not find the disk.
upamais.com/images/85860108949701943741.jpg

Picture 4 - HD detected in CMOS
upamais.com/images/26584796346631645198.jpg

Picture 5 - Test HD Checked
http://upamais.com/images/59485123436635256684.jpg

Picture 6 - Print Progress reached 100% successfully.
upamais.com/images/91350844335036262661.jpg

I tried to give a command at the prompt:

hdparm-I / dev / hda

Error list driver

Other prints:

Other 1 - upamais.com/images/54665830428864404586.jpg
Other 2 - upamais.com/images/92666783481860566711.jpg
Other 3 - upamais.com/images/69977925071657808112.jpg
Other 4 - upamais.com/images/96071346588295240686.jpg

Note: sdb believe it is the stick I gave the boot.

I'm waiting now give three hours in CMOS.

[edtambasco]

Não contem password amigo.
Tudo começou quando eu passei o Secure Erase e cancelei o procedimento.
Agora nenhum programa encontra a unidade. E quando encontra só da BadBlock
Na BIOS detecta normal. O disco não contem erros, eu que errei ao passar este programa.
Abraços aos amigos de Portugal.

Check PM

Parted Magic? No detect drive.

[edtambasco]

@Vulcan

Left for more than three hours in the CMOS screen but not resolved.
Any idea what can be done? You saw the prints JPG´s??

[Vulcan]

Any idea what can be done? You saw the prints JPG´s??

It seems that your drive's behaviour is that it does not automatically restart an interrupted Secure Erase, and needs the command to be restarted, and then allowed to run to completion.

From the screenshots, I see that the drive is still recognised correctly by the BIOS and a SMART extended self test (I guess that is what the BIOS test is doing?) is successful, so the drive does not seem to be obviously faulty (although this does not prove that the drive is definitely OK). Therefore it is a surprise that the Parted Magic live CD does not correctly recognise the "problem" drive.

It may also be useful for you to explain why you were trying to format the drive originally, before you chose to run the Secure Erase. Did you suspect that the drive is faulty, or was everything working OK and you just wanted to erase all the data on the drive, or something else?

If it was my drive, I would:

a) analyse the Parted Magic Linux boot messages, to see what problem(s) it shows, related to why the drive is not being allocated a /dev node; and
b) use MHDD to diagnose the current state of the drive and, if appropriate, re-issue the original interrupted Secure Erase command.

Unfortunately I don't expect that you have the experience to do option (a) and you probably cannot do option (b) on that laptop / netbook, unless you can find a BIOS option to change the SATA controller into IDE / Legacy / Compatibility mode. Some laptops / netbooks don't include a BIOS option for changing the SATA controller mode, and I am guessing that the current SATA controller mode (typically AHCI) is why MHDD does not recognise that drive on that laptop / netbook (if I understand your previous comments correctly - there is no screenshot to confirm this).

Therefore, as BlackST suggested earlier, you would probably need to use a different laptop or PC which does have that BIOS option for the SATA controller, just to be able to run MHDD. Then you have to find someone who will help you diagnose the situation remotely using MHDD (or a similar utility like Victoria etc.), even with the translation / communication problems...

[Vulcan]

Therefore it is a surprise that the Parted Magic live CD does not correctly recognise the "problem" drive.

Correction: I should not say that the live CD does not correctly recognise your "problem" drive. Your screenshots show an I/O error reported from "hdparm -i /dev/sda" but that suggests a /dev/sda device node has been created (i.e. the drive has been recognised during boot) so the problem does not seem to be with recognition.

I remember seeing similar problems sometimes when using hdparm on older Linux distros, but it was so long ago that I cannot remember the cause at the moment. A different distro may behave differently (i.e. better). The Linux boot messages may also still be useful when analysed by someone with the necessary skill / experience. (I doubt this is related to the known premature timeout issue on older hdparm versions.) The other parts of my previous comment are unchanged.