My hard disk has many weak sectors, can I modify the $BadClus manually to prevent the system to access these sectors. Cos Chkdsk cannot identify these weak sector. Thanks for your help.

Hello !
You might want to read this :
Hope this tool helps you.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Thanks. Does makebad revertable or permanently bad? Cos the firmware of my hard disk is corrupted. I guess this is the reason for so many weak sectors which occur intervally at first 60% of the disk. I am seeking the way to solve the firmware problem. If makebad is not revertable then I may not try.

MakeBad can be reverted by deleting the partition and making a new one. This will destroy all your data but will revert the effects of MakeBad. Think of MakeBad as a scandisk but wile scandisk can only mark the bad sectors as bad so that those sectors can no longer be used (until you full-format) Makebad do the same but to "weak" sectors (the ones that take more time than normal to read/write to).
If your firmware is damaged you will need the expensive PC3000 or an equivalent expensive tool to fix it, but the best option is to get a new HD.
Good luck.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

How did u check that there is a problem with your firmware ?

When I use HDAT2 to fix the disk weak sector, it said the firmware is corrupted. My other two good hard disks do not have such problem in HDAT2. I think the software can tell the true though I'm not familiar with it.

When I use HDAT2 to fix the disk weak sector, it said the firmware is corrupted. My other two good hard disks do not have such problem in HDAT2. I think the software can tell the true though I'm not familiar with it.

When I use HDAT2 to fix the disk weak sector, it said the firmware is corrupted. My other two good hard disks do not have such problem in HDAT2. I think the software can tell the true though I'm not familiar with it.

I think HDTA2 cannot check the SA of the hdd then how could it tell that there is a problem with the firmware .

While this was directed to Spildit, I'm open to anyone's help



Hi Spildit,
This is my the first time using the makebad utility for mhdd. I am currently on my first run with it now. These huge drives nowadays take long time lol. So I just want to get this right when you say deleting the partition will undo what makebad does? The readme says to run MakeBad first and then create partition and then format.



This confuses me a bit as it looks what you are saying is that this works more like a chkdsk that requires a partition instead of raw drive that marks the sector bad on the G-list or p-list (still working on getting those right lol).

Could you set me straight on this? It be good to hear from someone with some hands on knowledge. Perhaps you could help my curiosity some that if it is run on a sector that contains data, does it just make the sector bad rendering the data in that sector destroyed/unaccessable? I am familiar with how chkdsk works by moving the data from the sector and then marking it bad. I was under the impression that MakeBad simply marks the sector bad and does no moving of any data. So running it on a partition that is formatted with says Windows would basically just destroy it by marking sectors bad that contain data.

Secondly, other then the "automated process", how does this different then using the makebad command from within the normal mhdd?

While I am at it hehe,
If using the makebad command to manually make a sector bad, would it be suggested to "Writing sectors to a file" and then make bad and then "Writing sectors from file to the drive" to a different sector? Is this even capable from the command line? Useful for a working Windows with just a couple weak sectors...

Any help or advice on this is greatly appreciated

Just can't quite figure it out here. I am using the manual makebad and putting in sector 5701545 and it says completed.
But when I reboot the computer and do a scan it not showing as being marked bad and just shows warning again for >500ms.
I've tried raw drive (unpartitioned), partitioned, partition with NTFS).

Smart status never changes:
Reallocated Sectors count remains 100 100 426
Reallocate event count remains 100 100 136

Am I missing something here? Like SMART isn't suppose to show it and a rescan (F4) does not either?

So I've been searching and browsing around the forum and found this...



So what I thought was supposed to be happening was in fact NOT! OK that's cool. At least I have an understanding that the G and P list can't be written to normally and what the differences are between the two.

Now I'm still not quite sure I understand the correct procedure/requirements for using the makebad command from within mhdd..
Since it does not write to the P and G list, I can only assume it requires a NTFS partition in advance to be on the drive? Does it need to be formatted?
Basically I just don't know the proper requirements/procedure for running the makebad command.