ATA enhanced secure erase takes long time to complete

[Krush206]

This is a 160 GB rotational drive. Non-enhanced secure erase took about an hour and a half to complete. Enhanced secure erase is taking hours (more than a day) to complete, even though, the estimated completion time is 54 minutes (for both enhanced and non-enhanced erasure). Is this fine or should I be concerned?

Attachments

[lcoughey]

Enhanced will do a multiple pass erase and will also include remapped bad sectors. If there are a lot of remapped sectors on the drive, it seem plausible that it could take a long time to complete.

[Krush206]

Yeah, it does have a lot of bad sectors, higher than 12000. It's a long story, 3 HDDs of mine suddenly "bricked" while I was using Phoenix OS (one of them apparently survived, an external HDD). It looks like this OS somehow corrupts HDDs' firmware, I say that because CrystalDiskInfo shows this disk's health status as 'Unknown' and I remember it used to show as 'Caution' (the drive had about 56 sectors remapped). The first drive which this OS "bricked" had NONE remapped sectors and suddenly a bunch of sectors got remapped. Some weird thing I noticed aswell is that I have used testdisk app to check for filesystems which was erased, it found a BSD filesystem with 2 TB of storage, the disk's original size is 160 GB

Attachments

This is what GSmartControl shows,
realize there are 'cloned' attributes there. Don't mind the high raw values, GSmartControl doesn't shows them properly; CrystalDiskInfo does

[lcoughey]

The OS is unlikely to have corrupted the drive's firmware. Running a drive that is failing is likely what caused firmware damage. That is, the firmware is stored on the platters and is just as vulnerable to bad sectors as the rest of the drive. When the health status of a drive is showing caution, that is a good time to backup the data and replace the drive and put it to pasture.

[Krush206]

Sorry, I haven't informed properly. The external HDD actually was plugged in a laptop (which has none remapped sectors), it was running Phoenix OS aswell. The illness it got was literally the same from these other 2 HDDs, but somehow it survived and still works flawlessly. I never used this external HDD on my desktop computer. And if I recall correctly, this issue happened on kernel version 4.9, I always used to change to the version 4.4 since it was more stable

[Krush206]

I read somewhere that by running enhanced secure erase, as it overwrites bad sectors it can actually recover them (if it's not badly damaged) and reset the G-List. Hence why I ran it on this drive. Is this true though?

[Krush206]

So, I ended up putting the drive in the freezer four times or so, that didn't solve the issue. But then I thought about using a magnet and it worked! I have no idea why but after magnetizing the drive there are no more read failures. Though, I still think there is something botched in the drive's firmware, S.M.A.R.T. data's attributes got randomized a couple of times after freezing the drive. This is not new though, it used to get randomized very few times even before I froze the drive. But stopped after using a magnet

[HaQue]

and you are going to use this drive? wow.

[pclab]

Great, you got the drive running.
Now, do you want a DR lab to help you get the data soon, right?

[Krush206]

No, that wasn't a joke. And I don't really care about data. I don't think the drive died at all, this issue happened after using that OS called Phoenix OS (version 1.5.0, 32 bits) which somehow botched 2 drives of mine. One of those drives had NONE reallocated sectors, no S.M.A.R.T. attributes showing errors/failures, the drive was alive and kicking. I was using the OS normally, but the 'illness' was injected after rebooting/shutting down the PC. It almost killed my father's external hard drive aswell (which would be the third drive killed). At first, I thought it was my computer but after trying it on a laptop I realized it was the OS. I used the external drive on that laptop, using the same OS version and the same thing happened like as the other 2 drives (except S.M.A.R.T. wasn't botched. Probably because it is a USB device, not an actual SATA). Anyways, I have been using the drive for a month or so and is still working properly

[Krush206]

Why you say it's bullshit? I literally put the magnet (which wasn't powerful at all like those in a microwave) around the drive for 3 or 4 times (I haven't disassembled it), without exceptions. That was the only thing which 'ressurected' the drive. Also, if you don't believe the OS 'bricked' then give I try yourself on Phoenix OS 1.5.0. Use another SATA HDD with it. You don't even need to erase your current OS to use Phoenix. Btw, the drives were bricked with ext4 filesystem. But I think FAT32 would brick it aswell since the external drive was screwed by it with FAT32

[HaQue]

obviously the magnet pulled all the bits that had fallen over upwards. Science.

The Freezer trick doesn't work on Android based OS's, that's just stupidity. Its only Apple gear... once a MAC detects it is not cool, it don't work right. Windows doesn't really care.. about anything. It doesn't need you at all really. Linux? well It isn't the year of Linux on the desktop. Yet.

who would have thought that the people that put up a site such as http://www.phoenixos.com/en_US/ and is still in chinese, would have an OS that isnt 100% stable?

The trouble with idiots is they pull you down to their level then beat you with experience.

I am just verifying if Phoenix OS v1.5.0 (even though it is up to over v3) will brick my drive... no doesnt seem....
Kzshhhh Kzshhhhh Kzshhhh Kzshhhhh

[pcimage]

Why you say it's bullshit? I literally put the magnet (which wasn't powerful at all like those in a microwave) around the drive for 3 or 4 times (I haven't disassembled it), without exceptions. That was the only thing which 'ressurected' the drive. Also, if you don't believe the OS 'bricked' then give I try yourself on Phoenix OS 1.5.0. Use another SATA HDD with it. You don't even need to erase your current OS to use Phoenix. Btw, the drives were bricked with ext4 filesystem. But I think FAT32 would brick it aswell since the external drive was screwed by it with FAT32

100% BS!

[zynx]

hello, im new in this forum and i was curious about this topic… well, i had an old conserved drive here with 80 gb of storage and decided to give a try on this… my drive also bricked after using phoenix. bios takes 10 seconds to recognize drives but ends up not recognizing this one anymore… i also thought the guy was saying bs but i have to confirm it does bricks drives since it bricked mine… i will later try to use a magnet to check if the drives gets alive again…

[Nvidea]

Krush206,

hello Krush,, i no able to download HDTA2 version 2018,, website .com is offline ..
can you do post to me for googledrive?

[Krush206]

Krush206,

hello Krush,, i no able to download HDTA2 version 2018,, website .com is offline ..
can you do post to me for googledrive?

Here

[Nvidea]

Thanks much,,
from Prosoft MediaTools Wipe 1.2 Build 130626 you know where find Keygen?

[HaQue]

Thanks much,,
from Prosoft MediaTools Wipe 1.2 Build 130626 you know where find Keygen?

https://www.prosofteng.com/mediatoolswipe-disk-wipe/

but you knew that already

[Nvidea]

Thanks much,,
from Prosoft MediaTools Wipe 1.2 Build 130626 you know where find Keygen?

https://www.prosofteng.com/mediatoolswipe-disk-wipe/

but you knew that already

hello,, no i no have nothing equipment .. only for DEMOS
At moment i'm on samsung on bug and sectors bad .. i allready run DBAN sucesful but came back bad-sectors on mhdd
HDAT2 no detect nothing and i no i'm able to unlock the password to security erase ...

[Nvidea]

any can help me?

on SRT demo, can i write good modules to other HD on (same model)on bad modules? to superscribe to other HDdriver? hd is freezing when I READ the modules to backup, many are in (X red) ..