IMHO more info needed from you, in order for readers to better understand your story. Also, I assume that you do not need the data from these disks, since you tried to do a secure erase. (FYI I cannot view your video at the moment, as for a few days I'm using a 3G modem, with limited bandwidth, at a remote location - so I am using just the information you have written.)
What Kinda info u want? SMART? I´ll post it. In the video u can see what´s happening.
What is common between these 2 drives, in the way you have been using them? Same PC? Same mains power supply? Same building? etc. etc.
No. It´s not from a PC. It´s from Laptops. One is from a Dell Latitude D-520 (shown on video, 640Gb), and another from a Lenovo Y-430.
They have random bad sectors
What do you mean exactly by "random"? Do you mean that sector X is sometimes bad (unreadable), and sometimes sector X is readable (without doing any writes between tests)? Or do you mean that unreadable sectors are distributed (seemingly) randomly across the whole disk? Or something else? Where is your actual evidence?
Let´s see... The bads (nor the delays), appears in different areas of the Hd. Since I´ve LLF the drive, i noticed that some erased, and some appeared in other sectors, this is strange at all.
in SMART, the reallocated sectors are the same number: 16376.
Please supply full SMART data, including raw values, from both drives. Do you have any older SMART data from these drives? If so, then supply that also.
Smart Data from MK755GSXP below (RAW, RAW OFFSET, VALUE, THRESHOLD, STATUS)
Read Error Rate,0,0,100,0,OK
Reallocated Sectors Count,16376,0,1,49,Fail
Seek Error Rate,0,0,100,77,OK
Seek Time Performance,0,0,100,32,OK
Power-On Hours (POH),812,0,98,32,OK
Spin Retry Count,0,0,109,47,OK
Power Cycle Count,489,0,100,0,OK
G-sense error rate,1526,0,100,15,OK
Power-off Retract Count,55,0,100,0,OK
Load/Unload Cycle Count,8020,0,100,0,OK
Reallocation Event Count,1158,0,100,116,Degradation
Current Pending Sector Count,0,0,100,0,OK
Uncorrectable Sector Count,0,0,100,0,OK
UltraDMA CRC Error Count,0,0,200,0,OK
Load/Unload Retry Count,0,0,100,0,OK
Head Flying Hours,0,0,100,0,OK
When I try to erase with secure erase, to delete odd information on the G-List
This statement is ambiguous, but you might misunderstand what a secure erase does. More (unambiguous) explanation is needed from you, about what you think a secure erase should do.
These SATA drives have a feature called Secure Erase, that erase all data in HDD. And these two have the Enhanced Secure Erase, that erase G-List (that contais the Sectors Previously Rellocated)
The program always give me the information that the drive is freeze-locked.
This is not necessarily a fault - this is done by a BIOS deliberately to stop malicious secure erase being done by malware! You need to research the ways to bypass this, if you really want to do a secure erase - several bypass techniques exist (e.g. see the readme for HDDerase for some examples). However IMHO secure erase is unlikely to solve your real (currently undiagnosed) problem.
No, The main problem is: The HDD prevents itself to make changes in it, any changes you want to do. Look, I´ve tried to enable Write Cache Off, HDAT or other does, but, when you INIT the drive, the settings go wrong. Hence the "Complete" or "HDD Reject command", used in DCO restore option.
Personally, I think you are trying too many unrelated commands, for no clear reason (that I can understand) and the results are confusing you - so that you guess there is a firmware fault. Based on your description and limited info, I see no evidence of a firmware fault, and in any case, you will not fix most firmware problems yourself. So please stop guessing at the cause, and do more diagnosis
(if you accept the risks that you may cause more problems).
No, I´m trying commands related to the problem. Not confused. That´s a pertinent problem to 2 different drives, do you unnerstand? Like I said before, it´s like the HDD have activated the read-only feature to the firmware. But I can partition it and copy and erase files to it. That´s it.
Please read this, to explain more about repairing firmware-related problems: diy-what-the-big-deal-t12671.html
Ok. I´ll read. Thanks.